reiser4 snapshot for August 26th.
Hello!
I have just released another reiser4 snapshot that I hope all interested parties will try. It is released against 2.6.0-test4.
You can find it at http://namesys.com/snapshots/2003.08.26
I include release notes below.
Reiser4 snapshot for 2003.08.26
WARNING!!! This code is experimental! WE ARE NOT KIDDING! DO NOT PUT ANY VALUABLE DATA ON REISER4 YET!
Fixed some bugs. And finally reiser4 should compile on 64bit boxes (hm. somebody try it, as I am unable to build any 2.6 kernel for ia64). Also reiser4 should now build without debug enabled.
Important SMP bug was fixed (only was in effect for SMP kernels on boxes with less than 3 CPUs). There are still some OOM problems sometimes that we are working on, but generally I hope problems reported by various people about compile failures should be fixed now. Readonly mounts (and hence - reiser4 as rootfs) are not supported too.
reiser4progs update includes some 64 bit fixes too along with other stuff. fsck still does not work, so don't even try to run it.
Snapshot is released as a patch against linux-2.6.0-test4REISER4_NOOPT config option (Disable compiler optimizations for reiser4 code.)
is known to not compile on x86.
Enable CONFIG_REISER4_LARGE_KEY, as reiser4progs are creating filesystems with
large keys by default.
The reiser4-kernelonly.diff file represents only required kernel modifications if you plan to use our reiser4 bk repository.
It does not contains any reiser4 code
The reiser4.diff is full patch with everything included.
Changelog (extracted by "bk changes"):
[email protected], 2003-08-26 12:53:59+04:00, [email protected]
remove assertion (contradicts recent changes in prepare_twig_cut())
[email protected], 2003-08-26 12:53:28+04:00, [email protected]
remove superfluous check
[email protected], 2003-08-26 11:19:03+04:00, [email protected]
search_one_bitmap_backward() endless loop fix.
[email protected], 2003-08-25 22:01:52+04:00, [email protected]
backward search bitmap code fixes
[email protected], 2003-08-25 21:26:46+04:00, [email protected]
ctail.c:
Fixed bug
file.c:
shared reserve_cut_iteration
cryptcompress.c:
Added cut_items_cryptcompress(),
fixed bugs
[email protected], 2003-08-25 21:06:06+04:00, [email protected]
sync with recent change in prepare_twig_cut()
[email protected], 2003-08-25 21:00:04+04:00, [email protected]
when removing eottl, clear connected bits on formatted neighbors
[email protected], 2003-08-25 20:59:26+04:00, [email protected]
restore old check.
[email protected], 2003-08-25 20:59:13+04:00, [email protected]
fix race in check_jload()
[email protected], 2003-08-25 20:58:52+04:00, [email protected]
add separate inode to keep bitmaps.
cleanup
[email protected], 2003-08-25 20:45:18+04:00, [email protected]
fix fence error in wake_up_requestor()
[email protected], 2003-08-25 18:05:17+04:00, [email protected]
bitmap.c:
Remove erroneous ON_DEBUG()
[email protected], 2003-08-25 13:58:15+04:00, [email protected]
use vmalloc instead of kmalloc
[email protected], 2003-08-25 08:49:07+04:00, [email protected]
bitmap code reorganization
[email protected], 2003-08-24 15:56:24+04:00, [email protected]
inode.h:
64bit compile fix
[email protected], 2003-08-22 21:05:40+04:00, [email protected]
fix compilation errors
[email protected], 2003-08-22 21:00:56+04:00, [email protected]
restore compilability.
[email protected], 2003-08-22 20:56:38+04:00, [email protected]
fix problems with BK's handling of symlinks
[email protected], 2003-08-22 20:55:24+04:00, [email protected]
Merge laputa.namesys.com:/home/god/projects/2.5/fs/reiser4 into laputa.namesys.com:/home/god/projects/i386/fs/reiser4
[email protected], 2003-08-22 20:45:52+04:00, [email protected]
cleanup
[email protected], 2003-08-22 20:45:32+04:00, [email protected]
add scripts to perform mongo automatically.
[email protected], 2003-08-22 20:44:24+04:00, [email protected]
fix race in sibling list code.
[email protected], 2003-08-22 20:43:54+04:00, [email protected]
fix debugging checks.
[email protected], 2003-08-22 20:43:15+04:00, [email protected]
don't do read-ahead if low on memory.
[email protected], 2003-08-22 20:42:55+04:00, [email protected]
add assertion.
[email protected], 2003-08-22 20:42:39+04:00, [email protected]
fix assertion: atom lock should be held to avoid races with fusion.
[email protected], 2003-08-22 20:42:13+04:00, [email protected]
use jnode attached to page to avoid hash table lookup when possible
[email protected], 2003-08-22 20:41:38+04:00, [email protected]
add sysfs file with a list of all active atoms.
[email protected], 2003-08-22 20:40:59+04:00, [email protected]
don't set JNODE_DKSET in add_empty_leaf() to avoid races
[email protected], 2003-08-22 20:40:23+04:00, [email protected]
move check.
[email protected], 2003-08-22 20:40:08+04:00, [email protected]
fix race in eflush_del().
fix hash function.
make hash table dynamically sized.
[email protected], 2003-08-22 20:39:29+04:00, [email protected]
mark get_current_context() as const.
[email protected], 2003-08-22 20:39:06+04:00, [email protected]
remove noisy compiler options
Quoted 9 lines · Oleg Drokin
Hello!
I have just released another reiser4 snapshot that I hope all interested parties will try. It is released against 2.6.0-test4.
You can find it at http://namesys.com/snapshots/2003.08.26
I include release notes below.Reiser4 snapshot for 2003.08.26
I got this error while attempting to compile with reiser4. Snippet from .config follows.
Steven
CC fs/reiser4/plugin/file/tail_conversion.o
CC fs/reiser4/sys_reiser4.ofs/reiser4/sys_reiser4.c:54:32: parser/parser.code.c: No such file or directory fs/reiser4/sys_reiser4.c: In function `sys_reiser4':fs/reiser4/sys_reiser4.c:75: warning: implicit declaration of function `reiser4_pars_init' fs/reiser4/sys_reiser4.c:75: warning: assignment makes pointer from integer without a cast fs/reiser4/sys_reiser4.c:80: error: dereferencing pointer to incomplete type fs/reiser4/sys_reiser4.c:82: warning: implicit declaration of function yyparse' fs/reiser4/sys_reiser4.c:83: warning: implicit declaration of function reiser4_pars_free' fs/reiser4/sys_reiser4.c:66: warning: unused variable `Gencode' fs/reiser4/sys_reiser4.c: At top level:fs/reiser4/parser/parser.h:333: warning: Fistmsg' defined but not used fs/reiser4/parser/parser.h:342: warning: typesOfCommand' defined but not used fs/reiser4/parser/parser.h:354: warning: `Code' defined but not used make[2]: *** [fs/reiser4/sys_reiser4.o] Error 1
make[1]: *** [fs/reiser4] Error 2
make: *** [fs] Error 2
[steven@spc1 linux-2.6.0-test4-r4]$ grep REISER4 .config CONFIG_REISER4_FS=yCONFIG_REISER4_FS_SYSCALL=yCONFIG_REISER4_LARGE_KEY=y
# CONFIG_REISER4_CHECK is not setCONFIG_REISER4_USE_EFLUSH=y
# CONFIG_REISER4_BADBLOCKS is not set
Quoted 8 lines · Steven Cole
Quoted 7 lines · Oleg Drokin
Hello!
I have just released another reiser4 snapshot that I hope all interested parties will try. It is released against 2.6.0-test4.
You can find it at http://namesys.com/snapshots/2003.08.26
I include release notes below.
Quoted 5 lines
Quoted 2 lines
Reiser4 snapshot for 2003.08.26
I got this error while attempting to compile with reiser4. Snippet from .config follows.
Disable "reiser4 system call" (CONFIG_REISER4_FS_SYSCALL) support, it is not ready.
Quoted 29 lines
Steven
CC
fs/reiser4/plugin/file/tail_conversion.o
CCfs/reiser4/sys_reiser4.ofs/reiser4/sys_reiser4.c:54:32:parser/parser.code.c: No such file or directoryfs/reiser4/sys_reiser4.c: In function `sys_reiser4':fs/reiser4/sys_reiser4.c:75: warning: implicit declaration of function `reiser4_pars_init'fs/reiser4/sys_reiser4.c:75: warning: assignment makes pointer from integer without a castfs/reiser4/sys_reiser4.c:80: error: dereferencing pointer to incomplete typefs/reiser4/sys_reiser4.c:82: warning: implicit declaration of functionyyparse' fs/reiser4/sys_reiser4.c:83: warning: implicit declaration of functionreiser4_pars_free'fs/reiser4/sys_reiser4.c:66: warning: unused variable `Gencode'fs/reiser4/sys_reiser4.c: At top level:fs/reiser4/parser/parser.h:333: warning:Fistmsg' defined but not used fs/reiser4/parser/parser.h:342: warning:typesOfCommand' defined but not usedfs/reiser4/parser/parser.h:354: warning: `Code' defined but not used make[2]: *** [fs/reiser4/sys_reiser4.o] Error 1
make[1]: *** [fs/reiser4] Error 2
make: *** [fs] Error 2
[steven@spc1 linux-2.6.0-test4-r4]$ grep REISER4 .configCONFIG_REISER4_FS=yCONFIG_REISER4_FS_SYSCALL=yCONFIG_REISER4_LARGE_KEY=y
#CONFIG_REISER4_CHECKis not setCONFIG_REISER4_USE_EFLUSH=y
#CONFIG_REISER4_BADBLOCKSis not set
Signature · 1 line
Alex.
Quoted 2 lines · Alex Zarochentsev
Disable "reiser4 system call" (
CONFIG_REISER4_FS_SYSCALL) support, it is not ready.
[...]
CC lib/string.olib/string.c:435: warning: conflicting types for built-in function `bcopy'
CC lib/vsprintf.o AR lib/lib.a LD arch/i386/lib/built-in.o AS arch/i386/lib/checksum.o CC arch/i386/lib/dec_and_lock.o CC arch/i386/lib/delay.o AS arch/i386/lib/getuser.o CC arch/i386/lib/memcpy.o CC arch/i386/lib/strstr.o CC arch/i386/lib/usercopy.o AR arch/i386/lib/lib.a GEN .version CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o LD init/built-in.o LD .tmp_vmlinux1
arch/i386/kernel/built-in.o(.data+0x7c4): In function `sys_call_table':
: undefined reference to `sys_reiser4'
make[2]: *** [.tmp_vmlinux1] Error 1
make[1]: *** [vmlinux] Error 2
[...]CONFIG_REISER4_FS=m
# CONFIG_REISER4_FS_SYSCALL is not set
# CONFIG_REISER4_LARGE_KEY is not set
# CONFIG_REISER4_CHECK is not set
# CONFIG_REISER4_USE_EFLUSH is not set
# CONFIG_REISER4_BADBLOCKS is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
[...]
Hello!
Quoted 9 lines · Felipe Alfaro Solana
Quoted 2 lines
Disable "reiser4 system call" (
CONFIG_REISER4_FS_SYSCALL) support, it is not ready.[...]
arch/i386/kernel/built-in.o(.data+0x7c4): In function `sys_call_table':
: undefined reference to `sys_reiser4'
make[2]: *** [.tmp_vmlinux1] Error 1
make[1]: *** [vmlinux] Error 2
[...]CONFIG_REISER4_FS=m
Building as module is also not yet supported.
Bye,
Oleg
Quoted 13 lines · Oleg Drokin
Hello!
Quoted 9 lines · Felipe Alfaro Solana
Quoted 2 lines
Disable "reiser4 system call" (
CONFIG_REISER4_FS_SYSCALL) support, it is not ready.[...]
arch/i386/kernel/built-in.o(.data+0x7c4): In function `sys_call_table':
: undefined reference to `sys_reiser4'
make[2]: *** [.tmp_vmlinux1] Error 1
make[1]: *** [vmlinux] Error 2
[...]CONFIG_REISER4_FS=m
Quoted 2 lines
Building as module is also not yet supported.
Fine, then here's a patch:
fs/Kconfig renamed from fs/Kconfig.orig +3 -0
@@ -203,6 +203,9 @@ tristate "Reiser4 (EXPERIMENTAL very fast general purpose filesystem)" depends on EXPERIMENTAL ---help--- + Building as a module is not yet supported, so don't say 'M' + unless you're a developer. + Reiser4 is more than twice as fast for both reads and writes as ReiserFS. That means it is four times as fast as NTFS by Microsoft. (Proper benchmarks will appear in a few months at
Meanwhile, reiser4 seems to be working fine and is nice and fast.
I did a "time bk -r co" for the current 2.6 tree, and here are the results for reiser4 and ext3 on 2.6.0-test4:
Reiser4:
real 1m55.077s user 0m30.740s sys 0m36.558s
Ext3:
real 3m48.438s user 0m26.400s sys 0m13.205s
Steven
Quoted 4 lines · Steven Cole
I did a "time bk -r co" for the current 2.6 tree, and here are the results for reiser4 and ext3 on 2.6.0-test4:
Reiser4:
Quoted 9 lines
real 1m55.077s user 0m30.740s sys 0m36.558sExt3:
real 3m48.438s user 0m26.400s sys 0m13.205s
Can you try ext3 with -o data=writeback, as well as xfs & reiser3?
Thanks
Quoted 9 lines · Mike Fedyk
Quoted 8 lines · Steven Cole
I did a "time bk -r co" for the current 2.6 tree, and here are the results for reiser4 and ext3 on 2.6.0-test4:
Reiser4:
real 1m55.077s user 0m30.740s sys 0m36.558s
Quoted 7 lines
Quoted 5 lines
Ext3:
real 3m48.438s user 0m26.400s sys 0m13.205sCan you try ext3 with -o data=writeback, as well as xfs & reiser3?
[root@spc1 /]# umount /dev/hda9
[root@spc1 /]# mount -t ext3 -o data=writeback /dev/hda9 /home [root@spc1 /]# mount -t reiserfs /dev/hda10 /share_r [root@spc1 /]# mount -t xfs /dev/hda12 /share_x
[root@spc1 /]# df -T
Filesystem Type 1K-blocks Used Available Use% Mounted on
/dev/hda1 ext3 241116 89449 139219 40% /
none tmpfs 126784 0 126784 0% /dev/shm
/dev/hda8 ext3 241116 4711 223957 3% /tmp
/dev/hda6 ext3 3012204 2507596 351592 88% /usr
/dev/hda7 ext3 489992 70724 393968 16% /var
df: `/share_r4': Value too large for defined data type
/dev/hda9 ext3 20556656 16526268 4030388 81% /home
/dev/hda10
reiserfs 4112476 1911220 2201256 47% /share_r
/dev/hda12 xfs 4991380 990884 4000496 20% /share_xYes, I can do that. Results in a little while.
BTW, this is RedHat Severn, so df --version gives
[steven@spc1 /]$ df --version
df (coreutils) 5.0
Steven
Quoted 8 lines · Steven Cole
Quoted 1 line · Mike Fedyk
Can you try ext3 with -o data=writeback, as well as xfs & reiser3?
[root@spc1 /]# umount
/dev/hda9
[root@spc1 /]# mount -t ext3 -o data=writeback/dev/hda9/home [root@spc1 /]# mount -t reiserfs/dev/hda10/share_r [root@spc1 /]# mount -t xfs/dev/hda12/share_x
Please use the same partition for all filesystem tests, otherwise you will be showing results that need to be adjusted for inner-spindle disk speed.
Quoted 4 lines · Mike Fedyk
Quoted 3 lines · Steven Cole
Quoted 1 line · Mike Fedyk
Can you try ext3 with -o data=writeback, as well as xfs & reiser3?
Quoted 8 lines
Quoted 5 lines
[root@spc1 /]# umount
/dev/hda9
[root@spc1 /]# mount -t ext3 -o data=writeback/dev/hda9/home [root@spc1 /]# mount -t reiserfs/dev/hda10/share_r [root@spc1 /]# mount -t xfs/dev/hda12/share_xPlease use the same partition for all filesystem tests, otherwise you will be showing results that need to be adjusted for inner-spindle disk speed.
Good point. That will take a little more time, but at least the results will be more meaningful. Thanks.
Steven
Quoted 17 lines · Mike Fedyk
Quoted 13 lines · Steven Cole
Quoted 3 lines · Mike Fedyk
Can you try ext3 with -o data=writeback, as well as xfs & reiser3?
[root@spc1 /]# umount
/dev/hda9
[root@spc1 /]# mount -t ext3 -o data=writeback/dev/hda9/home [root@spc1 /]# mount -t reiserfs/dev/hda10/share_r [root@spc1 /]# mount -t xfs/dev/hda12/share_x
Quoted 6 lines
Please use the same partition for all filesystem tests, otherwise you will be showing results that need to be adjusted for inner-spindle disk speed.
Oh yes, Mike is right.
Signature · 1 line
Hans
Quoted 54 lines · Steven Cole
Quoted 17 lines · Oleg Drokin
Hello!
Quoted 12 lines · Felipe Alfaro Solana
Quoted 3 lines
Disable "reiser4 system call" (
CONFIG_REISER4_FS_SYSCALL) support, it is not ready.[...]
arch/i386/kernel/built-in.o(.data+0x7c4): In function `sys_call_table':
: undefined reference to `sys_reiser4'
make[2]: *** [.tmp_vmlinux1] Error 1
make[1]: *** [vmlinux] Error 2
[...]CONFIG_REISER4_FS=mQuoted 4 lines
Building as module is also not yet supported.
Fine, then here's a patch:
fs/Kconfig renamed from fs/Kconfig.orig +3
-0@@ -203,6 +203,9 @@ tristate "Reiser4 (EXPERIMENTAL very fast general purpose filesystem)" depends on EXPERIMENTAL ---help--- + Building as a module is not yet supported, so don't say 'M' + unless you're a developer. + Reiser4 is more than twice as fast for both reads and writes as ReiserFS. That means it is four times as fast as NTFS by Microsoft. (Proper benchmarks will appear in a few months atMeanwhile, reiser4 seems to be working fine and is nice and fast.
I did a "time bk -r co" for the current 2.6 tree, and here are the results for reiser4 and ext3 on 2.6.0-test4:
Reiser4:
real 1m55.077s user 0m30.740s sys 0m36.558sExt3:
real 3m48.438s user 0m26.400s sys 0m13.205s
Quoted 12 lines
Steven
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Better to disable it entirely. Features too broken to compile should not be warned of, they should be invisible and not selectable in the menu. Thanks Steven and Mike.
Signature · 1 line
Hans
Quoted 13 lines · Oleg Drokin
Hello!
Quoted 9 lines · Felipe Alfaro Solana
Quoted 2 lines
Disable "reiser4 system call" (
CONFIG_REISER4_FS_SYSCALL) support, it is not ready.[...]
arch/i386/kernel/built-in.o(.data+0x7c4): In function `sys_call_table':
: undefined reference to `sys_reiser4'
make[2]: *** [.tmp_vmlinux1] Error 1
make[1]: *** [vmlinux] Error 2
[...]CONFIG_REISER4_FS=m
Quoted 2 lines
Building as module is also not yet supported.
To do:
remove all options in build system that don't compile.
o module
o syscall
o etc...
how to log reiser and raid0 crash? 2.6.0-t4
In reply to Felipe Alfaro Solana2.6.0-test4 amd xp 3000+ msi mbo nforce2 four Maxtor 60G 8mbcache raid0
I cause a lock up by doing a cp -aR /usr/src /mnt/usr which moves data larger than total hard buffer cache, to raid0 reiserfs or ext2 ( NOT reiser4!) Copy ops smaller than buffer cache(8mb x 4 = 32mb) don't fail. Nothing fails on a single drive, compiles or copies, just copy to a mounted raid0 device. What should I try, test, or dump?
No irq error storm. No cd drives installed. Smaller copy ops work. Turning swap off first slows things down enough to work, but swap itself is probably OK. I have bios turn apic off, then linux turns it on, which is good until the turn apic off before turn apic on patch gets into test5 or whatever.
hdparm sets all four drives the same, udma6 but have tried down to udma4 and pio4 and dma turned off, unmask on or off.
If two drives are on the mboard controller and two on a promise pci card, does /proc/ide/amd74xx refer to the two drives on the motherboard only? It seems to mention four drives but the two slow ones might just be a ref to unoccupied slave drive positions.
I'm wondering what to send in. Maybe I could send a log from successful copy with swap off, showing reiser logging, and config, in case a stress condition or misconfig shows up even when catastrophic failure doesn't occur. With swap on the fail is sudden and no error logging is coming through.
I could incrementally copy /usr/src to one raid, then do a copy from that raid to another raid. All that would do is test copying from one balanced set of four drives/partitions to another balanced set, versus copying from one drive's /usr/src to that and three other drives' raid set, which is unbalanced, dragging on one drive.
-Bob
Re: how to log reiser and raid0 crash? 2.6.0-t4
I had syslog send just *.info to vc/5 and though the *.info messages never make it into syslog file, I started cp -aR /usr/src/kernel-source-2.6.0 /tmp with md/2 mounted to /tmp and saw this *.info on vc/5 and then it locked up. How about those zeros, skip, assign id anyway?
journal_1037: journal_read_transaction, offset 3623, len 0 mount_id 0journal_1039: journal_read_trans skipping because 3623 is too oldjournal_1299: Setting newest_mount_id to 12
Anything?
-Bob D
Quoted 42 lines · Resident Boxholder
2.6.0-test4 amd xp 3000+ msi mbo nforce2 four Maxtor 60G 8mbcache raid0
I cause a lock up by doing a cp -aR
/usr/src/mnt/usrwhich moves data larger than total hard buffer cache, to raid0 reiserfs or ext2 ( NOT reiser4!) Copy ops smaller than buffer cache(8mb x 4 = 32mb) don't fail. Nothing fails on a single drive, compiles or copies, just copy to a mounted raid0 device. What should I try, test, or dump?No irq error storm. No cd drives installed. Smaller copy ops work. Turning swap off first slows things down enough to work, but swap itself is probably OK. I have bios turn apic off, then linux turns it on, which is good until the turn apic off before turn apic on patch gets into test5 or whatever.
hdparm sets all four drives the same, udma6 but have tried down to udma4 and pio4 and dma turned off, unmask on or off.
If two drives are on the mboard controller and two on a promise pci card, does
/proc/ide/amd74xxrefer to the two drives on the motherboard only? It seems to mention four drives but the two slow ones might just be a ref to unoccupied slave drive positions.I'm wondering what to send in. Maybe I could send a log from successful copy with swap off, showing reiser logging, and config, in case a stress condition or misconfig shows up even when catastrophic failure doesn't occur. With swap on the fail is sudden and no error logging is coming through.
I could incrementally copy
/usr/srcto one raid, then do a copy from that raid to another raid. All that would do is test copying from one balanced set of four drives/partitions to another balanced set, versus copying from one drive's/usr/srcto that and three other drives' raid set, which is unbalanced, dragging on one drive.(quoted diff) +0
-2-Bob -To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: how to log reiser and raid0 crash? 2.6.0-t4
In reply to Resident BoxholderHello!
Quoted 8 lines · Resident Boxholder
I cause a lock up by doing a cp -aR
/usr/src/mnt/usrwhich moves data larger
than total hard buffer cache, to raid0 reiserfs or ext2 ( NOT reiser4!) I'm wondering what to send in. Maybe I could send a log from successful copy with swap off, showing reiser logging, and config, in case a stress condition or misconfig shows up even when catastrophic failure doesn't occur. With swap on the fail is sudden and no error logging is coming through.
Is there any chance of using sirial console to see if you can capture something on that?
Bye,
Oleg
Re: how to log reiser and raid0 crash? 2.6.0-t4
2.6.0-t4 amd 3000+ 1G four maxtor 60G drives on two controllers(mb's and promise)
problem isolated to promise card(have to verify the other is error-free longer though)
Quoted 6 lines · Oleg Drokin
Hello!
On Tue, Aug 26, 2003 at 03:57:39PM -0400, Resident Boxholder wrote:
Quoted 9 lines
Quoted 3 lines
I cause a lock up by doing a cp -aR
/usr/src/mnt/usr...Is there any chance of using sirial console to see if you can capture something on that?
Bye,
Oleg
I have a second linux pc and I can google whether to use null or regular serial cable, howto put a console on serial, then log to that, I guess that's all. As a bonus I won't need a kvm switch anymore.
Here's some repeatable "high-level(monkey-level)" info.
I have four drives, two on mboard controller and two on a 133 Promise card. If I make a four-drive four-partition raid zero md device, I get enough lockups to draw my attention, so then I make two-drive md devices to see which controller works, if any. Without really flogging it I got ext2 and reiserfs on the mboard's two drives to work for mkfs, fsck, and copy /usr/src/ /tmp so maybe this is a Promise problem. The mboard controller handles udma6 no problem for that two-drive md.
With only two drives on the promise card forming a raid zero md device, crashes happen on mkfs and fscks and even though no md's are mounted on boot, the boot won't happen sometimes after a crash.
I have no errors logging anymore. The only one I got was by switching to vc/5 and seeing reiserfs info but I don't see that anymore since fixing one thing, it was because of mdadm and debian config conflict, forget that. The irq error storm was a false lead as well, no more such errors, no errors at all logged, since removing cd's and second promise card and turning usb off and turning apic off in bios and letting linux turn apic on. ACPI is smooth, no errors, just sudden death.
Things I've tried are no fastrak in promise kernel config, hdparm no dma, hdparm udma4 instead of udma6. I'll try pio4 pio3 on the promise md and really flog the mboard-controlled md to verify that there is no problem except on the promise card. I'm reading what Alan Cox is saying about "LBA48 pio and udma" so I will try turning dma off and going down in pio modes.
Swap is working with four drives, so two on the promise card, but with 1G of ram swap on the promise card may never be used.
-Bob D
Quoted 19 lines · Steven Cole
Quoted 9 lines · Oleg Drokin
Hello!
I have just released another reiser4 snapshot that I hope all interested parties will try. It is released against 2.6.0-test4.
You can find it at http://namesys.com/snapshots/2003.08.26
I include release notes below.Reiser4 snapshot for 2003.08.26
I got this error while attempting to compile with reiser4. Snippet from .config follows.
Steven
CC
fs/reiser4/plugin/file/tail_conversion.o
CCfs/reiser4/sys_reiser4.ofs/reiser4/sys_reiser4.c:54:32:parser/parser.code.c: No such file or directory
[snipped]
Quoted 3 lines
[steven@spc1 linux-2.6.0-test4-r4]$ grep REISER4 .config
CONFIG_REISER4_FS=yCONFIG_REISER4_FS_SYSCALL=y
I should have read this more carefully :(
config REISER4_FS_SYSCALL
bool "Enable reiser4 system call"
depends on REISER4_FS
default n
---help---
Adds sys_reiser4() syscall.
This code is not in good shape yet and may not compile and stuff like that.
Without REISER4_FS_SYSCALL, -test4 with reiser4 compiles fine. Sorry about the noise.
Steven
Quoted 46 lines · Steven Cole
Quoted 24 lines · Steven Cole
Quoted 11 lines · Oleg Drokin
Hello!
I have just released another reiser4 snapshot that I hope all interested parties will try. It is released against 2.6.0-test4.
You can find it at http://namesys.com/snapshots/2003.08.26
I include release notes below.Reiser4 snapshot for 2003.08.26
I got this error while attempting to compile with reiser4. Snippet from .config follows.
Steven
CC
fs/reiser4/plugin/file/tail_conversion.o
CCfs/reiser4/sys_reiser4.ofs/reiser4/sys_reiser4.c:54:32:parser/parser.code.c: No such file or directory[snipped]
Quoted 5 lines
[steven@spc1 linux-2.6.0-test4-r4]$ grep REISER4 .config
CONFIG_REISER4_FS=yCONFIG_REISER4_FS_SYSCALL=yI should have read this more carefully :(
config
REISER4_FS_SYSCALL
bool "Enable reiser4 system call"
depends onREISER4_FS
default n
---help---
Addssys_reiser4()syscall.
This code is not in good shape yet and may not compile and stuff like that.
Quoted 9 lines
Without
REISER4_FS_SYSCALL, -test4 with reiser4 compiles fine. Sorry about the noise.Steven
Users should not be expected to read help text in a case like this.If it does not compile, it should not be visible.
Signature · 1 line
Hans
Hello!
Quoted 10 lines · Steven Cole
Quoted 5 lines
I have just released another reiser4 snapshot that I hope all interested parties will try. It is released against 2.6.0-test4.
You can find it at http://namesys.com/snapshots/2003.08.26
I include release notes below.
Reiser4 snapshot for 2003.08.26I got this error while attempting to compile with reiser4. Snippet from .config follows.
[steven@spc1 linux-2.6.0-test4-r4]$ grep REISER4 .configCONFIG_REISER4_FS=yCONFIG_REISER4_FS_SYSCALL=y
Do not compile sys reiser4 support. It is not yet ready. (hm, probably I need to hide that option for next snapshot)
Bye,
Oleg
Mr. Demidov, if you put code that does not compile into our tree you need to make the config option for it be invisible.
Yes?
Steven, try turning off the sys_reiser4 related code.
Nikita, if Demidov is not workingtoday (I notice the lack of timesheet commits recently), take care of this for him.
Hans
Quoted 50 lines · Steven Cole
Quoted 11 lines · Oleg Drokin
Hello!
I have just released another reiser4 snapshot that I hope all interested parties will try. It is released against 2.6.0-test4.
You can find it at http://namesys.com/snapshots/2003.08.26
I include release notes below.Reiser4 snapshot for 2003.08.26
I got this error while attempting to compile with reiser4. Snippet from .config follows.
Steven
CC
fs/reiser4/plugin/file/tail_conversion.o
CCfs/reiser4/sys_reiser4.ofs/reiser4/sys_reiser4.c:54:32:parser/parser.code.c: No such file or directoryfs/reiser4/sys_reiser4.c: In function `sys_reiser4':fs/reiser4/sys_reiser4.c:75: warning: implicit declaration of function `reiser4_pars_init'fs/reiser4/sys_reiser4.c:75: warning: assignment makes pointer from integer without a castfs/reiser4/sys_reiser4.c:80: error: dereferencing pointer to incomplete typefs/reiser4/sys_reiser4.c:82: warning: implicit declaration of functionyyparse' fs/reiser4/sys_reiser4.c:83: warning: implicit declaration of functionreiser4_pars_free'fs/reiser4/sys_reiser4.c:66: warning: unused variable `Gencode'fs/reiser4/sys_reiser4.c: At top level:fs/reiser4/parser/parser.h:333: warning:Fistmsg' defined but not used fs/reiser4/parser/parser.h:342: warning:typesOfCommand' defined but not usedfs/reiser4/parser/parser.h:354: warning: `Code' defined but not used make[2]: *** [fs/reiser4/sys_reiser4.o] Error 1
make[1]: *** [fs/reiser4] Error 2
make: *** [fs] Error 2
[steven@spc1 linux-2.6.0-test4-r4]$ grep REISER4 .configCONFIG_REISER4_FS=yCONFIG_REISER4_FS_SYSCALL=yCONFIG_REISER4_LARGE_KEY=y
#CONFIG_REISER4_CHECKis not setCONFIG_REISER4_USE_EFLUSH=y
#CONFIG_REISER4_BADBLOCKSis not set
Signature · 1 line
Hans
Quoted 2 lines · Hans Reiser
Mr. Demidov, if you put code that does not compile into our tree you need to make the config option for it be invisible.
There is such an option already, CONFIG_REISER4_FS_SYSCALL, seems it is off by default.
Quoted 75 lines
Yes?
Steven, try turning off the
sys_reiser4related code.Nikita, if Demidov is not workingtoday (I notice the lack of timesheet commits recently), take care of this for him.
Hans
Quoted 57 lines · Steven Cole
Quoted 11 lines · Oleg Drokin
Hello!
I have just released another reiser4 snapshot that I hope all interested parties will try. It is released against 2.6.0-test4.
You can find it at http://namesys.com/snapshots/2003.08.26
I include release notes below.Reiser4 snapshot for 2003.08.26
I got this error while attempting to compile with reiser4. Snippet from .config follows.
Steven
CC
fs/reiser4/plugin/file/tail_conversion.o
CCfs/reiser4/sys_reiser4.ofs/reiser4/sys_reiser4.c:54:32:parser/parser.code.c: No such file or directoryfs/reiser4/sys_reiser4.c: In function `sys_reiser4':fs/reiser4/sys_reiser4.c:75: warning: implicit declaration of function `reiser4_pars_init'fs/reiser4/sys_reiser4.c:75: warning: assignment makes pointer from integer without a castfs/reiser4/sys_reiser4.c:80: error: dereferencing pointer to incomplete typefs/reiser4/sys_reiser4.c:82: warning: implicit declaration of function `yyparse'fs/reiser4/sys_reiser4.c:83: warning: implicit declaration of function `reiser4_pars_free'fs/reiser4/sys_reiser4.c:66: warning: unused variable `Gencode'fs/reiser4/sys_reiser4.c: At top level:fs/reiser4/parser/parser.h:333: warning:Fistmsg' defined but not used fs/reiser4/parser/parser.h:342: warning:typesOfCommand' defined but not usedfs/reiser4/parser/parser.h:354: warning: `Code' defined but not used make[2]: *** [fs/reiser4/sys_reiser4.o] Error 1
make[1]: *** [fs/reiser4] Error 2
make: *** [fs] Error 2
[steven@spc1 linux-2.6.0-test4-r4]$ grep REISER4 .configCONFIG_REISER4_FS=yCONFIG_REISER4_FS_SYSCALL=yCONFIG_REISER4_LARGE_KEY=y
#CONFIG_REISER4_CHECKis not setCONFIG_REISER4_USE_EFLUSH=y
#CONFIG_REISER4_BADBLOCKSis not setSignature · 1 line
Hans
Signature · 1 line
Alex.
Quoted 6 lines · Alex Zarochentsev
Quoted 2 lines · Hans Reiser
Mr. Demidov, if you put code that does not compile into our tree you need to make the config option for it be invisible.
There is such an option already,
CONFIG_REISER4_FS_SYSCALL, seems it is off by default.
Yes, but I the simple minded user that I am turned it on without reading the Kconfig help carefully. Now, it's off, and it compiles.
But, now for more interesting stuff:
[root@spc1 steven]# cd /
[root@spc1 /]# mkdir share_r4
[root@spc1 /]# mount -t reiser4 /dev/hda11 /share_r4 [root@spc1 /]# df -T
Filesystem Type 1K-blocks Used Available Use% Mounted on /dev/hda1 ext3 241116 89449 139219 40% / /dev/hda9 ext3 20556656 16526188 4030468 81% /home none tmpfs 126784 0 126784 0% /dev/shm /dev/hda8 ext3 241116 4711 223957 3% /tmp /dev/hda6 ext3 3012204 2507596 351592 88% /usr /dev/hda7 ext3 489992 70721 393971 16% /var
df: `/share_r4': Value too large for defined data type
I have recently run mkfs.reiser4 on /dev/hda11 with no options. The reiser4progs version is 0.4.12.
I made a local clone of the 2.6-test bk tree on the new reiser4 file system and that worked OK.
I then did a "time bk -r check -acv", twice for both reiser4 and ext3. Here are the results for the second run for each (I neglected to preserve the results for the initial bk -r check -acv):
Reiser4:
real 1m27.774s user 0m33.685s sys 0m16.059s
Ext3:
real 2m55.179s user 0m32.752s sys 0m5.835s
Nice work. I'll try to break Reiser4 now.
Steven
Quoted 17 lines · Steven Cole
Quoted 6 lines · Alex Zarochentsev
Quoted 2 lines · Hans Reiser
Mr. Demidov, if you put code that does not compile into our tree you need to make the config option for it be invisible.
There is such an option already,
CONFIG_REISER4_FS_SYSCALL, seems it is off by default.Yes, but I the simple minded user that I am turned it on without reading the
Kconfighelp carefully. Now, it's off, and it compiles.But, now for more interesting stuff:
[root@spc1 steven]# cd /
[root@spc1 /]# mkdirshare_r4
[root@spc1 /]# mount -t reiser4/dev/hda11/share_r4 [root@spc1 /]# df -T
Quoted 8 lines
Filesystem Type 1K-blocks Used Available Use% Mounted on /dev/hda1 ext3 241116 89449 139219 40% / /dev/hda9 ext3 20556656 16526188 4030468 81% /home none tmpfs 126784 0 126784 0% /dev/shm /dev/hda8 ext3 241116 4711 223957 3% /tmp /dev/hda6 ext3 3012204 2507596 351592 88% /usr /dev/hda7 ext3 489992 70721 393971 16% /vardf: `/share_r4': Value too large for defined data type
I can't reproduce that. Do you see df errors each time you mount just created reiser4 fs? Can you provide additional information about your system:
distro, libc which you used?
My hypothesysis is that libc statfs or df itself want to convert "free inodes" result parameter which is __u64 to shorter data type. reiser4_statfs() sets kstatfs->f_ffree to a large value which is close to 2^64.
Quoted 28 lines
I have recently run mkfs.reiser4 on
/dev/hda11with no options. The reiser4progs version is 0.4.12.I made a local clone of the 2.6-test bk tree on the new reiser4 file system and that worked OK.
I then did a "time bk -r check -acv", twice for both reiser4 and ext3. Here are the results for the second run for each (I neglected to preserve the results for the initial bk -r check -acv):
Reiser4:
real 1m27.774s user 0m33.685s sys 0m16.059sExt3:
real 2m55.179s user 0m32.752s sys 0m5.835sNice work. I'll try to break Reiser4 now.
Steven
Signature · 1 line
Alex.
On Thu, 2003-08-28 at 05:46, Alex Zarochentsev wrote:
[snipped]
Quoted 11 lines
Quoted 10 lines
[root@spc1 /]# mount -t reiser4
/dev/hda11/share_r4 [root@spc1 /]# df -TFilesystem Type 1K-blocks Used Available Use% Mounted on /dev/hda1 ext3 241116 89449 139219 40% / /dev/hda9 ext3 20556656 16526188 4030468 81% /home none tmpfs 126784 0 126784 0% /dev/shm /dev/hda8 ext3 241116 4711 223957 3% /tmp /dev/hda6 ext3 3012204 2507596 351592 88% /usr /dev/hda7 ext3 489992 70721 393971 16% /vardf: `/share_r4': Value too large for defined data type
Quoted 4 lines
I can't reproduce that. Do you see df errors each time you mount just created reiser4 fs? Can you provide additional information about your system:
distro, libc which you used?
Yes, each time that /dev/hda11 is reiser4 and mounted, I get that error. Other fs report OK, tested were ext2, ext3, reiserfs, jfs, xfs. Size is about 4G. At some point in the past, around 2.5.60, I tested the reiser4 snapshot, and this problem did not exist. Unfortunately, I don't remember what the base distro was for those tests.
Distro is Red Hat Severn (the latest RH beta).
df --version reports df (coreutils) 5.0/lib/libc.so.6 reports 2.3.2
gcc is 3.3
kernel is 2.6.0-test4 of course.
reiser4progs is 0.4.12
Quoted 3 lines
My hypothesysis is that libc statfs or df itself want to convert "free inodes" result parameter which is
__u64to shorter data type.reiser4_statfs()setskstatfs->f_ffreeto a large value which is close to 2^64.
I also tried a copy of df version 4.5.7 from a Mandrake 9.1 system, with exactly the same results as above.
Let me know if you have further questions.
Steven
Quoted 7 lines · Alex Zarochentsev
Quoted 3 lines · Steven Cole
df: `/share_r4': Value too large for defined data type
Quoted 9 lines
I can't reproduce that. Do you see df errors each time you mount just created reiser4 fs? Can you provide additional information about your system:
distro, libc which you used?My hypothesysis is that libc statfs or df itself want to convert "free inodes" result parameter which is
__u64to shorter data type.reiser4_statfs()setskstatfs->f_ffreeto a large value which is close to 2^64.
This problem is 100% reproducible for me.
mkfs.reiser4
mount
df
immediately shows the problem.
Running Debian Sid, stock kernel 2.6.0-test4 + Aug 26 reiser4 snapshot, Athlon XP CPU, glibc-2.3.1.
-Tupshin
Quoted 11 lines · Alex Zarochentsev
Quoted 3 lines · Hans Reiser
Mr. Demidov, if you put code that does not compile into our tree you need to make the config option for it be invisible.
There is such an option already,
CONFIG_REISER4_FS_SYSCALL, seems it is off by default.
Off != invisible
Signature · 1 line
Hans
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Steven Cole wrote:
|On Tue, 2003-08-26 at 04:22, Oleg Drokin wrote: | |>Hello! |> |> I have just released another reiser4 snapshot that I hope all interested |> parties will try. It is released against 2.6.0-test4. |> You can find it at http://namesys.com/snapshots/2003.08.26 |> I include release notes below. |> |>Reiser4 snapshot for 2003.08.26 |> | |I got this error while attempting to compile with reiser4. |Snippet from .config follows. | |Steven | | CC fs/reiser4/plugin/file/tail_conversion.o
befor compile "fs/reiser4/sys_reiser4.o" yacc mast be create "fs/reiser4/parser/parser.code.c:" why it not created?
Is yacc installed on your computer and patched?
| | CC fs/reiser4/sys_reiser4.o |fs/reiser4/sys_reiser4.c:54:32: parser/parser.code.c: No such file or directory |fs/reiser4/sys_reiser4.c: In function `sys_reiser4': |fs/reiser4/sys_reiser4.c:75: warning: implicit declaration of function `reiser4_pars_init' |fs/reiser4/sys_reiser4.c:75: warning: assignment makes pointer from integer without a cast |fs/reiser4/sys_reiser4.c:80: error: dereferencing pointer to incomplete type |fs/reiser4/sys_reiser4.c:82: warning: implicit declaration of function `yyparse' |fs/reiser4/sys_reiser4.c:83: warning: implicit declaration of function `reiser4_pars_free' |fs/reiser4/sys_reiser4.c:66: warning: unused variable `Gencode' |fs/reiser4/sys_reiser4.c: At top level: |fs/reiser4/parser/parser.h:333: warning: `Fistmsg' defined but not used |fs/reiser4/parser/parser.h:342: warning: `typesOfCommand' defined but not used |fs/reiser4/parser/parser.h:354: warning: `Code' defined but not used |make[2]: *** [fs/reiser4/sys_reiser4.o] Error 1 |make[1]: *** [fs/reiser4] Error 2 |make: *** [fs] Error 2 |[steven@spc1 linux-2.6.0-test4-r4]$ grep REISER4 .config |CONFIG_REISER4_FS=y |CONFIG_REISER4_FS_SYSCALL=y |CONFIG_REISER4_LARGE_KEY=y |# CONFIG_REISER4_CHECK is not set |CONFIG_REISER4_USE_EFLUSH=y |# CONFIG_REISER4_BADBLOCKS is not set | | | |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE/Tkp21LHFcKwUya8RAkPqAKCYI9+/8nAlz/4fOrcTCdz1FfKDpwCeIP3q aOfMgqqX7Jgo1hM5kVdTcbc=
=rzM5
-----END PGP SIGNATURE-----
Quoted 1 line · El Tue, 26 Aug 2003 14:22:33 +0400 Oleg Drokin <[email protected]> escribió:
Reiser4 snapshot for 2003.08.26
I got some errors running tiobench (see end of the message) They say something about ext3 but reiser4 is on the backtrace.
setup: root fs on /; reiser4 on /mnt; running tiobench on /mnt machine is dual p3 (800 mhz) on ide disk. Config attached
(Also, i wasn't able to run reiser4 as root fs...i got "flushing like mad blah nikita-something" messages in 3-5s periods.)
btw, I suppose this feature will be removed if/when reiser4 is merged?:
config REISER4_FS_SYSCALL
bool "Enable reiser4 system call"
dmesg errors:
(fs/ext3/inode.c, 2728): ext3_write_inode: called recursively, non-PF_MEMALLOC!
Call Trace: [<c018c715>] write_inode+0x45/0x50 [<c018c9af>] __sync_single_inode+0x28f/0x310 [<c018cd00>] generic_sync_sb_inodes+0x1c0/0x2e0 [<c018cf0c>] writeback_inodes+0xac/0x1d0 [<c014962c>] balance_dirty_pages+0xbc/0x180 [<c01cf421>] reiser4_exit_context+0x51/0x60 [<c01ea9e9>] reiser4_write+0x79/0xb0 [<c0165e7a>] vfs_write+0xaa/0x130 [<c0165f9f>] sys_write+0x3f/0x60 [<c0109b2f>] syscall_call+0x7/0xb
(fs/ext3/inode.c, 2728): ext3_write_inode: called recursively, non-PF_MEMALLOC!
Call Trace: [<c018c715>] write_inode+0x45/0x50 [<c018c9af>] __sync_single_inode+0x28f/0x310 [<c018cd00>] generic_sync_sb_inodes+0x1c0/0x2e0 [<c018cf0c>] writeback_inodes+0xac/0x1d0 [<c014962c>] balance_dirty_pages+0xbc/0x180 [<c01cf421>] reiser4_exit_context+0x51/0x60 [<c01ea9e9>] reiser4_write+0x79/0xb0
(fs/ext3/inode.c, 2728): ext3_write_inode: called recursively, non-PF_MEMALLOC!
Call Trace: [<c018c715>] write_inode+0x45/0x50 [<c018c9af>] __sync_single_inode+0x28f/0x310 [<c018cd00>] generic_sync_sb_inodes+0x1c0/0x2e0 [<c018cf0c>] writeback_inodes+0xac/0x1d0 [<c014962c>] balance_dirty_pages+0xbc/0x180 [<c01cf421>] reiser4_exit_context+0x51/0x60 [<c01ea9e9>] reiser4_write+0x79/0xb0 [<c0165e7a>] vfs_write+0xaa/0x130 [<c0165f9f>] sys_write+0x3f/0x60 [<c0109b2f>] syscall_call+0x7/0xb
(fs/ext3/inode.c, 2728): ext3_write_inode: called recursively, non-PF_MEMALLOC!
Call Trace: [<c018c715>] write_inode+0x45/0x50 [<c018c9af>] __sync_single_inode+0x28f/0x310 [<c018cd00>] generic_sync_sb_inodes+0x1c0/0x2e0 [<c018cf0c>] writeback_inodes+0xac/0x1d0 [<c014962c>] balance_dirty_pages+0xbc/0x180 [<c01cf421>] reiser4_exit_context+0x51/0x60 [<c01ea9e9>] reiser4_write+0x79/0xb0 [<c0165e7a>] vfs_write+0xaa/0x130 [<c0165f9f>] sys_write+0x3f/0x60 [<c0109b2f>] syscall_call+0x7/0xb
(and so on)
Hello!
Quoted 3 lines · Diego Calleja Garc?a
btw, I suppose this feature will be removed if/when reiser4 is merged?:
configREISER4_FS_SYSCALL
bool "Enable reiser4 system call"
No. It will be fixed.
Quoted 6 lines
dmesg errors:
(fs/ext3/inode.c, 2728):ext3_write_inode: called recursively, non-PF_MEMALLOC!Call Trace: [<c018c715>] write_inode+0x45/0x50 [<c018c9af>] __sync_single_inode+0x28f/0x310 [<c018cd00>] generic_sync_sb_inodes+0x1c0/0x2e0
Hm. Interesting Thank you for the report. We will fix it.
Bye,
Oleg
Quoted 3 lines · Oleg Drokin
Fixed some bugs. And finally reiser4 should compile on 64bit boxes (hm. somebody try it, as I am unable to build any 2.6 kernel for ia64).
I built this with IA64 2.6.0-test4, it works but there were lots of warnings (I can put up a log if you want it). This was on a dual processor Itanium 2 box.
First up, I tried a little test to make a few files, but once I had unmounted the disk I couldn't re-mount it.
--- example testing below ---
bash-2.05b# mkfs.reiser4 /dev/sda5
mkfs.reiser4 0.4.12
Copyright (C) 2001, 2002, 2003 by Hans Reiser, licensing governed by reiser4progs/COPYING.
Information: Reiser4 is going to be created on /dev/sda5.
(Yes/No): Yes
Creating reiser4 on /dev/sda5...mkfs.reiser4(5676): unaligned access to 0x60000000000242f2, ip=0x20000000000f7661 mkfs.reiser4(5676): unaligned access to 0x60000000000242fa, ip=0x20000000000f77a1 mkfs.reiser4(5676): unaligned access to 0x6000000000024302, ip=0x20000000000f78e1 mkfs.reiser4(5676): unaligned access to 0x60000000000242f2, ip=0x20000000000f2671 done
Synchronizing /dev/sda5...done
bash-2.05b# mount -t reiser4 /dev/sda5 /mnt
bash-2.05b# cd /mnt
bash-2.05b# time for i in seq 1 10000 ; do touch $i ; done
real 0m18.577s user 0m5.910s sys 0m12.657s
[do ls, all looks ok]
bash-2.05b# umount /mnt
bash-2.05b# mount -t reiser4 /dev/sda5 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/sda5,
or too many mounted file systems
--- end example testing ---
The console popped up with :
reiser4[mount(15688)]: reiser4_fill_super (fs/reiser4/vfs_ops.c:1229)[nikita-2608]:
WARNING: Wrong magic: 10000 != 62533452
when I tried to mount it.
I repeated this, but this time thought I'd try 'sync' before unmounting the disk; the sync command just hung and from that point nothing could seem to access disk, even on different partitions (so each program became unresponsive as soon as it tried to open a file).
Then I tried the mongo.pl script just for something else, I used the parameters given in the sample config, i.e.
FSTYPE=reiser4
BYTES=250000000
FILE_SIZE=4096
It just seemed to hang in "PHASE Create" and after, say a minute or two, made the machine unresponsive in the same way as 'sync' above -- as soon as anything tried to access disk it just hung.
So I retried this, and did a ls in the mounted directory just after I started mongo to try and poke at what it was up to; ls hung in the same way but this time I got messages :
reiser4[ls(30795)]: traverse_tree (fs/reiser4/search.c:488)[nikita-1481]:
WARNING: Too many iterations: 128
reiser4[ls(30795)]: traverse_tree (fs/reiser4/search.c:488)[nikita-1481]:
WARNING: Too many iterations: 256
reiser4[ls(30795)]: traverse_tree (fs/reiser4/search.c:488)[nikita-1481]:
WARNING: Too many iterations: 512
reiser4[ls(30795)]: traverse_tree (fs/reiser4/search.c:488)[nikita-1481]:
WARNING: Too many iterations: 1024
reiser4[ls(30795)]: traverse_tree (fs/reiser4/search.c:488)[nikita-1481]:
WARNING: Too many iterations: 2048
that just kept climbing ...
I'm happy to help more, but I think a little more targetting debugging is required. Could you suggest what would be helpful for me to try?
Quoted 18 lines · Ian Wienand
Quoted 3 lines · Oleg Drokin
Fixed some bugs. And finally reiser4 should compile on 64bit boxes (hm. somebody try it, as I am unable to build any 2.6 kernel for ia64).
I built this with IA64 2.6.0-test4, it works but there were lots of warnings (I can put up a log if you want it). This was on a dual processor Itanium 2 box.
First up, I tried a little test to make a few files, but once I had unmounted the disk I couldn't re-mount it.
--- example testing below ---
bash-2.05b# mkfs.reiser4
/dev/sda5
mkfs.reiser4 0.4.12
Copyright (C) 2001, 2002, 2003 by Hans Reiser, licensing governed by reiser4progs/COPYING.
Quoted 9 lines
Information: Reiser4 is going to be created on
/dev/sda5.
(Yes/No): Yes
Creating reiser4 on/dev/sda5...mkfs.reiser4(5676): unaligned access to0x60000000000242f2, ip=0x20000000000f7661mkfs.reiser4(5676): unaligned access to0x60000000000242fa, ip=0x20000000000f77a1mkfs.reiser4(5676): unaligned access to0x6000000000024302, ip=0x20000000000f78e1mkfs.reiser4(5676): unaligned access to0x60000000000242f2, ip=0x20000000000f2671 done
Synchronizing/dev/sda5...done
I will fix it soon.
Thanks for report.
Regards.
Quoted 11 lines · Yury Umanets
Quoted 10 lines
Information: Reiser4 is going to be created on
/dev/sda5.
(Yes/No): Yes
Creating reiser4 on/dev/sda5...mkfs.reiser4(5676): unaligned access to0x60000000000242f2, ip=0x20000000000f7661mkfs.reiser4(5676): unaligned access to0x60000000000242fa, ip=0x20000000000f77a1mkfs.reiser4(5676): unaligned access to0x6000000000024302, ip=0x20000000000f78e1mkfs.reiser4(5676): unaligned access to0x60000000000242f2, ip=0x20000000000f2671 done
Synchronizing/dev/sda5...done
Quoted 1 line
I will fix it soon.
Will Reiser4 be integrated into 2.6.0-test kernels anytime soon? This would reduce time between releases and would open up it to a wider audience for testing
Quoted 15 lines · Felipe Alfaro Solana
Quoted 12 lines · Yury Umanets
Quoted 12 lines
Information: Reiser4 is going to be created on
/dev/sda5.
(Yes/No): Yes
Creating reiser4 on/dev/sda5...mkfs.reiser4(5676): unaligned access to0x60000000000242f2, ip=0x20000000000f7661mkfs.reiser4(5676): unaligned access to0x60000000000242fa, ip=0x20000000000f77a1mkfs.reiser4(5676): unaligned access to0x6000000000024302, ip=0x20000000000f78e1mkfs.reiser4(5676): unaligned access to0x60000000000242f2, ip=0x20000000000f2671 done
Synchronizing/dev/sda5...done
Quoted 12 lines
Quoted 3 lines
I will fix it soon.
Will Reiser4 be integrated into 2.6.0-test kernels anytime soon? This would reduce time between releases and would open up it to a wider audience for testing
This is not a Namesys decision, I encourage you to ask Linus and Andrew about it though. I would like to see it go in as an experimental marked filesystem....
Signature · 1 line
Hans
Re: reiser4 snapshot 20030905 [OOPS]
In reply to Oleg DrokinHi,
I compiled the kernel (2.6.0-test5) without key_large support I attached a disk /dev/hda (I'm booting off /dev/hdb)
# mkfs.reiser4 /dev/hda1 Went ok
# mount -t reiser4 /dev/hda1 /1 And here's the output. It seems unsupported keys cause null pointer dereference.
reiser4[mount(1504)]: get_ready_format40 (fs/reiser4/plugin/disk_format/disk_format40.c:229)[nikita-3228]:
WARNING: Key format mismatch. Only small keys are supported.
Unable to handle kernel NULL pointer dereference at virtual address 00000000 printing eip: c01d859e *pde = 00000000 Oops: 0000 [#1] CPU: 0 EIP: 0060:[<c01d859e>] Tainted: P EFLAGS: 00010246
EIP is at unhash_unformatted_node_nolock+0x1d/0x6e
eax: 00000000 ebx: c262f800 ecx: c1060018 edx: 00000000
esi: c2684000 edi: 00000000 ebp: c1060018 esp: c2685c34
ds: 007b es: 007b ss: 0068
Process mount (pid: 1504, threadinfo=c2684000 task=c5f36710)
Stack: c2684000 c2684000 c01d860d c262f800 c262f800 c01f8345 c262f800 c262f800
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Call Trace:
[<c01d860d>] unhash_unformatted_jnode+0x1e/0x3e
[<c01f8345>] reiser4_invalidatepage+0xe0/0x165
[<c013c7c3>] do_invalidatepage+0x27/0x2b
[<c013c894>] truncate_complete_page+0xcd/0xd2
[<c013ca80>] truncate_inode_pages+0xcd/0x306
[<c0168bf4>] wake_up_inode+0xf/0x26
[<c016eca3>] write_inode_now+0x6a/0xa4
[<c0168753>] generic_forget_inode+0x12e/0x141
[<c01687e1>] iput+0x62/0x7c
[<c01eef6c>] done_formatted_fake+0x3b/0x5b
[<c01f6840>] reiser4_fill_super+0x343/0x606
[<c0156154>] get_sb_bdev+0x127/0x159
[<c016a11b>] alloc_vfsmnt+0x87/0xb6
[<c01f6cf7>] reiser4_get_sb+0x2f/0x33
[<c01f64fd>] reiser4_fill_super+0x0/0x606
[<c0156386>] do_kern_mount+0x5f/0xd1
[<c016b386>] do_add_mount+0x95/0x176
[<c016b6b4>] do_mount+0x155/0x1a1
[<c016b55b>] copy_mount_options+0xf4/0xf8
[<c016baaa>] sys_mount+0xd7/0x135
[<c0109089>] sysenter_past_esp+0x52/0x71
Code: 8b 02 85 c0 74 1c 0f b6 0d 01 06 43 c0 80 f9 02 74 04 0f 18
<6>note: mount[1504] exited with preempt_count 2
bad: scheduling while atomic!
Call Trace:
[<c0118d8b>] schedule+0x3ed/0x3f2
[<c013fc5b>] unmap_page_range+0x49/0x87
[<c013fe5c>] unmap_vmas+0x1c3/0x231
[<c0143fa0>] exit_mmap+0x7c/0x191
[<c011a64d>] mmput+0x67/0xb6
[<c011e366>] do_exit+0x12e/0x3d4
[<c010a121>] do_divide_error+0x0/0xfb
[<c0116b62>] do_page_fault+0x14a/0x44b
[<c013ac01>] cache_alloc_refill+0xd0/0x209
[<c01e46fd>] atom_init+0xc9/0xd7
[<c01e4a05>] atom_begin_andlock+0xd7/0x15e
[<c01e5aee>] try_capture_block+0x147/0x18f
[<c0116a18>] do_page_fault+0x0/0x44b
[<c0109ae5>] error_code+0x2d/0x38
[<c01d859e>] unhash_unformatted_node_nolock+0x1d/0x6e
[<c01d860d>] unhash_unformatted_jnode+0x1e/0x3e
[<c01f8345>] reiser4_invalidatepage+0xe0/0x165
[<c013c7c3>] do_invalidatepage+0x27/0x2b
[<c013c894>] truncate_complete_page+0xcd/0xd2
[<c013ca80>] truncate_inode_pages+0xcd/0x306
[<c0168bf4>] wake_up_inode+0xf/0x26
[<c016eca3>] write_inode_now+0x6a/0xa4
[<c0168753>] generic_forget_inode+0x12e/0x141
[<c01687e1>] iput+0x62/0x7c
[<c01eef6c>] done_formatted_fake+0x3b/0x5b
[<c01f6840>] reiser4_fill_super+0x343/0x606
[<c0156154>] get_sb_bdev+0x127/0x159
[<c016a11b>] alloc_vfsmnt+0x87/0xb6
[<c01f6cf7>] reiser4_get_sb+0x2f/0x33
[<c01f64fd>] reiser4_fill_super+0x0/0x606
[<c0156386>] do_kern_mount+0x5f/0xd1
[<c016b386>] do_add_mount+0x95/0x176
[<c016b6b4>] do_mount+0x155/0x1a1
[<c016b55b>] copy_mount_options+0xf4/0xf8
[<c016baaa>] sys_mount+0xd7/0x135
[<c0109089>] sysenter_past_esp+0x52/0x71bad: scheduling while atomic!
Call Trace: [<c0118d8b>] schedule+0x3ed/0x3f2 [<c013fc5b>] unmap_page_range+0x49/0x87 [<c013fe5c>] unmap_vmas+0x1c3/0x231 [<c0143fa0>] exit_mmap+0x7c/0x191 [<c011a64d>] mmput+0x67/0xb6 [<c011e366>] do_exit+0x12e/0x3d4 [<c010a121>] do_divide_error+0x0/0xfb [<c0116b62>] do_page_fault+0x14a/0x44b [<c013ac01>] cache_alloc_refill+0xd0/0x209 [<c01e46fd>] atom_init+0xc9/0xd7 [<c01e4a05>] atom_begin_andlock+0xd7/0x15e [<c01e5aee>] try_capture_block+0x147/0x18f [<c0116a18>] do_page_fault+0x0/0x44b [<c0109ae5>] error_code+0x2d/0x38 [<c01d859e>] unhash_unformatted_node_nolock+0x1d/0x6e [<c01d860d>] unhash_unformatted_jnode+0x1e/0x3e [<c01f8345>] reiser4_invalidatepage+0xe0/0x165 [<c013c7c3>] do_invalidatepage+0x27/0x2b [<c013c894>] truncate_complete_page+0xcd/0xd2 [<c013ca80>] truncate_inode_pages+0xcd/0x306 [<c0168bf4>] wake_up_inode+0xf/0x26 [<c016eca3>] write_inode_now+0x6a/0xa4 [<c0168753>] generic_forget_inode+0x12e/0x141 [<c01687e1>] iput+0x62/0x7c [<c01eef6c>] done_formatted_fake+0x3b/0x5b [<c01f6840>] reiser4_fill_super+0x343/0x606 [<c0156154>] get_sb_bdev+0x127/0x159 [<c016a11b>] alloc_vfsmnt+0x87/0xb6 [<c01f6cf7>] reiser4_get_sb+0x2f/0x33 [<c01f64fd>] reiser4_fill_super+0x0/0x606 [<c0156386>] do_kern_mount+0x5f/0xd1 [<c016b386>] do_add_mount+0x95/0x176 [<c016b6b4>] do_mount+0x155/0x1a1 [<c016b55b>] copy_mount_options+0xf4/0xf8 [<c016baaa>] sys_mount+0xd7/0x135 [<c0109089>] sysenter_past_esp+0x52/0x71
Re: reiser4 snapshot 20030905 [OOPS]
Quoted 11 lines · Maciej Soltysiak
Hi,
I compiled the kernel (2.6.0-test5) without
key_largesupport I attached a disk/dev/hda(I'm booting off/dev/hdb)# mkfs.reiser4 /dev/hda1 Went ok# mount -t reiser4 /dev/hda1 /1 And here's the output. It seems unsupported keys cause null pointer dereference.
This is known problem. Actually, reiser4 mount function cannot handle errors very well at the moment.
Quoted 5 lines
reiser4[mount(1504)]:
get_ready_format40(fs/reiser4/plugin/disk_format/disk_format40.c:229)[nikita-3228]:
WARNING: Key format mismatch. Only small keys are supported.Unable to handle kernel NULL pointer dereference at virtual address 00000000 printing eip:
[...]
Quoted 2 lines
[<
c0109089>]sysenter_past_esp+0x52/0x71
Nikita.