Re: reiser4 problems
Vitaly Fertman wrote: Hello, On Tuesday 21 March 2006 21:07, Sergey Ivanov wrote: Hi, wrong bytes is not a big problem, reiser4 indeed counted them wrongly some time ago, although it seems to be fixed already. the only serious problem here is at the beginning of the 'CHECKING STORAGE TREE' pass -- there must not be a key [0:0(NAME):0:0:0]. After second fsck, I have unmounted and mounted it read only to save data on ext3 partition and to wait answers and suggestions before using reiser4 once more. which reiser4progs version do you use? 1.0.5 it is already difficult to say why this strange key appeared -- you have already run several build-fs runs -- although it may be related to remount (I remember we used to have some problems before) or to fsck --build-fs. But I was not able to use filesystem after first fsck --build-fs. Even ls mountpoint was failing with io error message. unmount you fs please and run 'fsck --check' on the unmounted fs -- check that all is right there now. FS is consistent which kernel version do you use? It's 2.4.16, ALTLinux vserver's kernel (see http://www.sisyphus.ru/srpm/kernel-image-vs26-smp) with applied patch based on namesys' for 2.6.14, you can see it's spec, changelog and download it from http://www.sisyphus.ru/srpm/kernel-feat-fs-reiser4. As I can see now, all data were intact, everything restored O.K after these 2 fsck --build-fs. -- With best regards, Sergey Ivanov
Re: reiser4 problems
On Wed, 2006-03-22 at 10:33 +0300, Vitaly Fertman wrote: Hello, On Tuesday 21 March 2006 21:07, Sergey Ivanov wrote: Hi, I am sorry to report problems I had this night at my e-mail server. Grepped reiser4 messages from /var/log/messages are at http://parkheights.dyndns.org/r4log.bz2 I have 2 processor system (athlon) with raid5 software array with 5x62.1 GB, giving me 248.4GB for use. I have created lvm2 volumes for imap folders there, and also have /usr, /var, /home and other resides on the same raid5, everything formatted reiser4. Yesterday the server stops working, but answer pings. I've rebooted it with magic SysRQ key combinations after forced unmounting and syncing all partitions. But in the night the problems reappear on some of virtual volumes. In the morning I did remount -o ro and fsck.reiser4, all but one volume was O.K, but one required rebuild-fs. Excuse me, I have not saved the first fsck.reiser4 output. After rebuilding fs and then rebooting the system, I've got immediately problems, the filesystem was not accessible, all attempts to get ls of it finished with i/o error messagees. (I have errors in /etc/fstab, the reiser4 volumes has lines ending with 1 1, not 1 2 as it should be. I'm not sure it attributed to the these problems). The second fsck.reiser4 once more founded some problems, it's the log: --- [EMAIL PROTECTED] ~]# fsck.reiser4 -y --build-fs /dev/evms/imap-seriv *** This is an EXPERIMENTAL version of fsck.reiser4. Read README first. *** Fscking the /dev/evms/imap-seriv block device. Will check the consistency of the Reiser4 SuperBlock. Will build the Reiser4 FileSystem. * fsck.reiser4 started at Tue Mar 21 08:34:40 2006 Reiser4 fs was detected on /dev/evms/imap-seriv. CHECKING STORAGE TREE FSCK: Node (740803): The left delimiting key [29:1(SD):0:2a:0] in the parent node (740782), pos (0/4294967295) does not match the first key [0:0(NAME):0:0: 0] in the node. Fixed. FSCK: The tree height 4 found in the format is wrong. Fixed to 5. Read nodes 440830 Nodes left in the tree 440830 Leaves of them 435415, Twigs of them 5323 Time interval: Tue Mar 21 08:34:41 2006 - Tue Mar 21 08:44:54 2006 CHECKING EXTENT REGIONS. Read twigs 5323 Time interval: Tue Mar 21 08:44:54 2006 - Tue Mar 21 08:46:14 2006 LOOKING FOR UNCONNECTED NODES Read nodes 0 Good nodes 0 Leaves of them 0, Twigs of them 0 Time interval: Tue Mar 21 08:46:14 2006 - Tue Mar 21 08:46:14 2006 CHECKING EXTENT REGIONS. Read twigs 0 Time interval: Tue Mar 21 08:46:14 2006 - Tue Mar 21 08:46:14 2006 INSERTING UNCONNECTED NODES 1. Twigs: done 2. Twigs by item: done 3. Leaves: done 4. Leaves by item: done Twigs: read 0, inserted 0, by item 0, empty 0 Leaves: read 0, inserted 0, by item 0 Time interval: Tue Mar 21 08:46:14 2006 - Tue Mar 21 08:46:14 2006 CHECKING SEMANTIC TREE FSCK: Node (762207), item (5), [6f6e9:6e6577:6f6eb] (stat40): wrong size (20), Fixed to (21). FSCK: Node (762207), item (5), [6f6e9:6e6577:6f6eb] (stat40): wrong bytes (2473), Fixed to (2605). FSCK: Node (773635), item (5), [6f62a:6e6577:6f62c] (stat40): wrong size (6), Fixed to (7). FSCK: Node (773635), item (5), [6f62a:6e6577:6f62c] (stat40): wrong bytes (628), Fixed to (760). FSCK: Node (773635), item (6), [6f62a:746d70:6f62b] (stat40): wrong size (4), Fixed to (3). FSCK: Node (773635), item (6), [6f62a:746d70:6f62b] (stat40): wrong bytes (312), Fixed to (206). Found 395956 objects. Time interval: Tue Mar 21 08:46:14 2006 - Tue Mar 21 09:28:41 2006 CLEANUPING STORAGE TREE ... --- (once more, excuse me, I have copied it from xterm while it was 'cleanuping storage tree', so it's not the full log). wrong bytes is not a big problem, reiser4 indeed counted them wrongly some time ago, although it seems to be fixed already. I recently encountered a wrong bytes issue on 2.6.15.1 with the 2.6.15-1 patch. After a lot of compiling (emerge -eD world in Gentoo), I ended up with a directory that I couldn't delete. fsck.reiser4 --check log: FSCK: Node (21121314), item (10), [10467f6:6c6f63616c6500:10467f7] (stat40): wrong size (3), Should be (2). FSCK: Node (21121314), item (10), [10467f6:6c6f63616c6500:10467f7] (stat40): wrong bytes (182), Should be (100). fsck.reiser4 --fix log: FSCK: Node (19374202), item (0): 1 mergable units were found in the extent40 unit. Merged. FSCK: Node (21121314), item (10), [10467f6:6c6f63616c6500:10467f7] (stat40): wrong size (3), Fixed to (2). FSCK: Node (21121314), item (10), [10467f6:6c6f63616c6500:10467f7] (stat40): wrong bytes (182),
Re: reiser4 problems
Hello On Wed, 2006-03-22 at 16:36 -0600, Jake Maciejewski wrote: On Wed, 2006-03-22 at 10:33 +0300, Vitaly Fertman wrote: Hello, On Tuesday 21 March 2006 21:07, Sergey Ivanov wrote: Hi, I am sorry to report problems I had this night at my e-mail server. Grepped reiser4 messages from /var/log/messages are at http://parkheights.dyndns.org/r4log.bz2 I have 2 processor system (athlon) with raid5 software array with 5x62.1 GB, giving me 248.4GB for use. I have created lvm2 volumes for imap folders there, and also have /usr, /var, /home and other resides on the same raid5, everything formatted reiser4. Yesterday the server stops working, but answer pings. I've rebooted it with magic SysRQ key combinations after forced unmounting and syncing all partitions. But in the night the problems reappear on some of virtual volumes. In the morning I did remount -o ro and fsck.reiser4, all but one volume was O.K, but one required rebuild-fs. Excuse me, I have not saved the first fsck.reiser4 output. After rebuilding fs and then rebooting the system, I've got immediately problems, the filesystem was not accessible, all attempts to get ls of it finished with i/o error messagees. (I have errors in /etc/fstab, the reiser4 volumes has lines ending with 1 1, not 1 2 as it should be. I'm not sure it attributed to the these problems). The second fsck.reiser4 once more founded some problems, it's the log: --- [EMAIL PROTECTED] ~]# fsck.reiser4 -y --build-fs /dev/evms/imap-seriv *** This is an EXPERIMENTAL version of fsck.reiser4. Read README first. *** Fscking the /dev/evms/imap-seriv block device. Will check the consistency of the Reiser4 SuperBlock. Will build the Reiser4 FileSystem. * fsck.reiser4 started at Tue Mar 21 08:34:40 2006 Reiser4 fs was detected on /dev/evms/imap-seriv. CHECKING STORAGE TREE FSCK: Node (740803): The left delimiting key [29:1(SD):0:2a:0] in the parent node (740782), pos (0/4294967295) does not match the first key [0:0(NAME):0:0: 0] in the node. Fixed. FSCK: The tree height 4 found in the format is wrong. Fixed to 5. Read nodes 440830 Nodes left in the tree 440830 Leaves of them 435415, Twigs of them 5323 Time interval: Tue Mar 21 08:34:41 2006 - Tue Mar 21 08:44:54 2006 CHECKING EXTENT REGIONS. Read twigs 5323 Time interval: Tue Mar 21 08:44:54 2006 - Tue Mar 21 08:46:14 2006 LOOKING FOR UNCONNECTED NODES Read nodes 0 Good nodes 0 Leaves of them 0, Twigs of them 0 Time interval: Tue Mar 21 08:46:14 2006 - Tue Mar 21 08:46:14 2006 CHECKING EXTENT REGIONS. Read twigs 0 Time interval: Tue Mar 21 08:46:14 2006 - Tue Mar 21 08:46:14 2006 INSERTING UNCONNECTED NODES 1. Twigs: done 2. Twigs by item: done 3. Leaves: done 4. Leaves by item: done Twigs: read 0, inserted 0, by item 0, empty 0 Leaves: read 0, inserted 0, by item 0 Time interval: Tue Mar 21 08:46:14 2006 - Tue Mar 21 08:46:14 2006 CHECKING SEMANTIC TREE FSCK: Node (762207), item (5), [6f6e9:6e6577:6f6eb] (stat40): wrong size (20), Fixed to (21). FSCK: Node (762207), item (5), [6f6e9:6e6577:6f6eb] (stat40): wrong bytes (2473), Fixed to (2605). FSCK: Node (773635), item (5), [6f62a:6e6577:6f62c] (stat40): wrong size (6), Fixed to (7). FSCK: Node (773635), item (5), [6f62a:6e6577:6f62c] (stat40): wrong bytes (628), Fixed to (760). FSCK: Node (773635), item (6), [6f62a:746d70:6f62b] (stat40): wrong size (4), Fixed to (3). FSCK: Node (773635), item (6), [6f62a:746d70:6f62b] (stat40): wrong bytes (312), Fixed to (206). Found 395956 objects. Time interval: Tue Mar 21 08:46:14 2006 - Tue Mar 21 09:28:41 2006 CLEANUPING STORAGE TREE ... --- (once more, excuse me, I have copied it from xterm while it was 'cleanuping storage tree', so it's not the full log). wrong bytes is not a big problem, reiser4 indeed counted them wrongly some time ago, although it seems to be fixed already. I recently encountered a wrong bytes issue on 2.6.15.1 with the 2.6.15-1 patch. After a lot of compiling (emerge -eD world in Gentoo), I ended up with a directory that I couldn't delete. fsck.reiser4 --check log: FSCK: Node (21121314), item (10), [10467f6:6c6f63616c6500:10467f7] (stat40): wrong size (3), Should be (2). FSCK: Node (21121314), item (10), [10467f6:6c6f63616c6500:10467f7] (stat40): wrong bytes (182), Should be (100). fsck.reiser4 --fix log: FSCK: Node (19374202), item (0): 1 mergable units were found in the extent40 unit. Merged. FSCK: Node (21121314), item (10),
Re: reiser4 problems
Unless Vitaly is still around, you will probably have to wait until tomorrow for a response. Thanks for your patience. Hans Sergey Ivanov wrote: Hi, I am sorry to report problems I had this night at my e-mail server. Grepped reiser4 messages from /var/log/messages are at http://parkheights.dyndns.org/r4log.bz2 I have 2 processor system (athlon) with raid5 software array with 5x62.1 GB, giving me 248.4GB for use. I have created lvm2 volumes for imap folders there, and also have /usr, /var, /home and other resides on the same raid5, everything formatted reiser4. Yesterday the server stops working, but answer pings. I've rebooted it with magic SysRQ key combinations after forced unmounting and syncing all partitions. But in the night the problems reappear on some of virtual volumes. In the morning I did remount -o ro and fsck.reiser4, all but one volume was O.K, but one required rebuild-fs. Excuse me, I have not saved the first fsck.reiser4 output. After rebuilding fs and then rebooting the system, I've got immediately problems, the filesystem was not accessible, all attempts to get ls of it finished with i/o error messagees. (I have errors in /etc/fstab, the reiser4 volumes has lines ending with 1 1, not 1 2 as it should be. I'm not sure it attributed to the these problems). The second fsck.reiser4 once more founded some problems, it's the log: --- [EMAIL PROTECTED] ~]# fsck.reiser4 -y --build-fs /dev/evms/imap-seriv *** This is an EXPERIMENTAL version of fsck.reiser4. Read README first. *** Fscking the /dev/evms/imap-seriv block device. Will check the consistency of the Reiser4 SuperBlock. Will build the Reiser4 FileSystem. * fsck.reiser4 started at Tue Mar 21 08:34:40 2006 Reiser4 fs was detected on /dev/evms/imap-seriv. Master super block (16): magic: ReIsEr4 blksize:4096 format: 0x0 (format40) uuid: c2bc9aae-fc5c-43b4-b527-9ff6fcde5b55 label: none Format super block (17): plugin: format40 description:Disk-format for reiser4. magic: ReIsEr40FoRmAt flushes:0 mkfs id:0xbd3e802 blocks: 1834992 free blocks:1059587 root block: 740782 tail policy:0x2 (smart) next oid: 0x77c5f file count: 395956 tree height:4 key policy: LARGE CHECKING STORAGE TREE FSCK: Node (740803): The left delimiting key [29:1(SD):0:2a:0] in the parent node (740782), pos (0/4294967295) does not match the first key [0:0(NAME):0:0: 0] in the node. Fixed. FSCK: The tree height 4 found in the format is wrong. Fixed to 5. Read nodes 440830 Nodes left in the tree 440830 Leaves of them 435415, Twigs of them 5323 Time interval: Tue Mar 21 08:34:41 2006 - Tue Mar 21 08:44:54 2006 CHECKING EXTENT REGIONS. Read twigs 5323 Time interval: Tue Mar 21 08:44:54 2006 - Tue Mar 21 08:46:14 2006 LOOKING FOR UNCONNECTED NODES Read nodes 0 Good nodes 0 Leaves of them 0, Twigs of them 0 Time interval: Tue Mar 21 08:46:14 2006 - Tue Mar 21 08:46:14 2006 CHECKING EXTENT REGIONS. Read twigs 0 Time interval: Tue Mar 21 08:46:14 2006 - Tue Mar 21 08:46:14 2006 INSERTING UNCONNECTED NODES 1. Twigs: done 2. Twigs by item: done 3. Leaves: done 4. Leaves by item: done Twigs: read 0, inserted 0, by item 0, empty 0 Leaves: read 0, inserted 0, by item 0 Time interval: Tue Mar 21 08:46:14 2006 - Tue Mar 21 08:46:14 2006 CHECKING SEMANTIC TREE FSCK: Node (762207), item (5), [6f6e9:6e6577:6f6eb] (stat40): wrong size (20), Fixed to (21). FSCK: Node (762207), item (5), [6f6e9:6e6577:6f6eb] (stat40): wrong bytes (2473), Fixed to (2605). FSCK: Node (773635), item (5), [6f62a:6e6577:6f62c] (stat40): wrong size (6), Fixed to (7). FSCK: Node (773635), item (5), [6f62a:6e6577:6f62c] (stat40): wrong bytes (628), Fixed to (760). FSCK: Node (773635), item (6), [6f62a:746d70:6f62b] (stat40): wrong size (4), Fixed to (3). FSCK: Node (773635), item (6), [6f62a:746d70:6f62b] (stat40): wrong bytes (312), Fixed to (206). Found 395956 objects. Time interval: Tue Mar 21 08:46:14 2006 - Tue Mar 21 09:28:41 2006 CLEANUPING STORAGE TREE ... --- (once more, excuse me, I have copied it from xterm while it was 'cleanuping storage tree', so it's not the full log). After second fsck, I have unmounted and mounted it read only to save data on ext3 partition and to wait answers and suggestions before using reiser4 once more.
Re: reiser4 problems
Thank you, Hans. One additional bit, may be it's about different problem. While copying from reiser4 volumes to newly created ext3 ones, I decided to remount read-only the with mount -o remount,ro command the source of copying. And it results in kernel panics I'm attaching to this mail. Then the cp process become unkillable, and the system did not reboot down remotely, I'll see at which point it hanged when I'll be there. -- Sergey. Hans Reiser wrote: Unless Vitaly is still around, you will probably have to wait until tomorrow for a response. Thanks for your patience. Hans Sergey Ivanov wrote: Hi, I am sorry to report problems I had this night at my e-mail server. [skip] Mar 21 14:01:08 parkheights crond[21683]: (root) CMD (run-parts /etc/cron.hourly) Mar 21 14:13:12 parkheights kernel: 4reiser4[ent:dm-6!(1146)]: disable_write_barrier (fs/reiser4/wander.c:233)[zam-1055]: Mar 21 14:13:13 parkheights kernel: WARNING: disabling write barrier Mar 21 14:13:13 parkheights kernel: Mar 21 14:25:29 parkheights -- MARK -- Mar 21 14:42:26 parkheights kernel: [ cut here ] Mar 21 14:42:27 parkheights kernel: kernel BUG at fs/reiser4/block_alloc.c:149! Mar 21 14:42:33 parkheights kernel: invalid operand: [#1] Mar 21 14:42:42 parkheights kernel: SMP Mar 21 14:42:42 parkheights kernel: Modules linked in: dm_mirror vfat fat nls_base lp ac thermal processor button ide_cd cdrom af_packet pdc202xx_new eepro100 mii hw_random amd_k7_agp agpgart analog ns558 gameport psmouse parport_pc parport usbhid floppy pcspkr ohci_hcd usbcore i810_audio ac97_codec soundcore reiser4 raid5 xor dm_mod rtc ext3 jbd mbcache sata_sil libata sd_mod scsi_mod ide_disk ide_generic amd74xx generic ide_core Mar 21 14:42:42 parkheights kernel: CPU:1 Mar 21 14:42:42 parkheights kernel: EIP:0060:[pg0+550729131/1069798400]Not tainted VLI Mar 21 14:42:42 parkheights kernel: EIP:0060:[e10f85ab]Not tainted VLI Mar 21 14:42:42 parkheights kernel: EFLAGS: 00210297 (2.6.14-vsr4-smp-alt5) Mar 21 14:42:42 parkheights kernel: EIP is at sub_from_ctx_grabbed+0x2b/0x40 [reiser4] Mar 21 14:42:42 parkheights kernel: eax: ebx: ecx: 0001 edx: Mar 21 14:42:42 parkheights kernel: esi: de4f3ea4 edi: df51f400 ebp: 0001 esp: de4f3c8c Mar 21 14:42:42 parkheights kernel: ds: 007b es: 007b ss: 0068 Mar 21 14:42:42 parkheights kernel: Process ent:dm-8! (pid: 1128, threadinfo=de4f2000 task=df5aba90) Mar 21 14:42:42 parkheights kernel: Stack: 0001 e10f8dbb de4f3ea4 0001 de4f3ea4 Mar 21 14:42:42 parkheights kernel:df51f400 e10f9119 de4f3ea4 df51f400 0001 df51f400 de4f3cf8 Mar 21 14:42:42 parkheights kernel:0001 de4f3d2c de4f3d70 e1100e58 de4f3cf8 de4f3d2c de4f3cf0 0044 Mar 21 14:42:42 parkheights kernel: Call Trace: Mar 21 14:42:42 parkheights kernel: [pg0+550731195/1069798400] grabbed2used+0x1b/0x60 [reiser4] Mar 21 14:42:42 parkheights kernel: [e10f8dbb] grabbed2used+0x1b/0x60 [reiser4] Mar 21 14:42:42 parkheights kernel: [pg0+550732057/1069798400] reiser4_alloc_blocks+0x149/0x1a0 [reiser4] Mar 21 14:42:42 parkheights kernel: [e10f9119] reiser4_alloc_blocks+0x149/0x1a0 [reiser4] Mar 21 14:42:42 parkheights kernel: [pg0+550764120/1069798400] get_more_wandered_blocks+0x38/0x50 [reiser4] Mar 21 14:42:42 parkheights kernel: [e1100e58] get_more_wandered_blocks+0x38/0x50 [reiser4] Mar 21 14:42:42 parkheights kernel: [pg0+550766523/1069798400] alloc_wandered_blocks+0x5b/0x90 [reiser4] Mar 21 14:42:42 parkheights kernel: [e11017bb] alloc_wandered_blocks+0x5b/0x90 [reiser4] Mar 21 14:42:42 parkheights kernel: [pg0+550766476/1069798400] alloc_wandered_blocks+0x2c/0x90 [reiser4] Mar 21 14:42:42 parkheights kernel: [e110178c] alloc_wandered_blocks+0x2c/0x90 [reiser4] Mar 21 14:42:42 parkheights kernel: [pg0+550767226/1069798400] commit_tx+0x4a/0xe0 [reiser4] Mar 21 14:42:42 parkheights kernel: [e1101a7a] commit_tx+0x4a/0xe0 [reiser4] Mar 21 14:42:42 parkheights kernel: [pg0+550767875/1069798400] reiser4_write_logs+0x123/0x1b0 [reiser4] Mar 21 14:42:42 parkheights kernel: [e1101d03] reiser4_write_logs+0x123/0x1b0 [reiser4] Mar 21 14:42:42 parkheights kernel: [pg0+550783854/1069798400] current_atom_finish_all_fq+0x1e/0x70 [reiser4] Mar 21 14:42:42 parkheights kernel: [e1105b6e] current_atom_finish_all_fq+0x1e/0x70 [reiser4] Mar 21 14:42:42 parkheights kernel: [pg0+550737328/1069798400] commit_current_atom+0x150/0x270 [reiser4] Mar 21 14:42:42 parkheights kernel: [e10fa5b0] commit_current_atom+0x150/0x270 [reiser4] Mar 21 14:42:42 parkheights kernel: [pg0+550740451/1069798400] try_commit_txnh+0x133/0x1d0 [reiser4] Mar 21 14:42:42 parkheights kernel: [e10fb1e3] try_commit_txnh+0x133/0x1d0 [reiser4] Mar 21 14:42:42 parkheights kernel: [pg0+550740656/1069798400] commit_txnh+0x30/0xc0 [reiser4] Mar 21 14:42:42 parkheights kernel: [e10fb2b0] commit_txnh+0x30/0xc0 [reiser4]
Re: reiser4 problems
Hello, On Tuesday 21 March 2006 21:07, Sergey Ivanov wrote: Hi, I am sorry to report problems I had this night at my e-mail server. Grepped reiser4 messages from /var/log/messages are at http://parkheights.dyndns.org/r4log.bz2 I have 2 processor system (athlon) with raid5 software array with 5x62.1 GB, giving me 248.4GB for use. I have created lvm2 volumes for imap folders there, and also have /usr, /var, /home and other resides on the same raid5, everything formatted reiser4. Yesterday the server stops working, but answer pings. I've rebooted it with magic SysRQ key combinations after forced unmounting and syncing all partitions. But in the night the problems reappear on some of virtual volumes. In the morning I did remount -o ro and fsck.reiser4, all but one volume was O.K, but one required rebuild-fs. Excuse me, I have not saved the first fsck.reiser4 output. After rebuilding fs and then rebooting the system, I've got immediately problems, the filesystem was not accessible, all attempts to get ls of it finished with i/o error messagees. (I have errors in /etc/fstab, the reiser4 volumes has lines ending with 1 1, not 1 2 as it should be. I'm not sure it attributed to the these problems). The second fsck.reiser4 once more founded some problems, it's the log: --- [EMAIL PROTECTED] ~]# fsck.reiser4 -y --build-fs /dev/evms/imap-seriv *** This is an EXPERIMENTAL version of fsck.reiser4. Read README first. *** Fscking the /dev/evms/imap-seriv block device. Will check the consistency of the Reiser4 SuperBlock. Will build the Reiser4 FileSystem. * fsck.reiser4 started at Tue Mar 21 08:34:40 2006 Reiser4 fs was detected on /dev/evms/imap-seriv. CHECKING STORAGE TREE FSCK: Node (740803): The left delimiting key [29:1(SD):0:2a:0] in the parent node (740782), pos (0/4294967295) does not match the first key [0:0(NAME):0:0: 0] in the node. Fixed. FSCK: The tree height 4 found in the format is wrong. Fixed to 5. Read nodes 440830 Nodes left in the tree 440830 Leaves of them 435415, Twigs of them 5323 Time interval: Tue Mar 21 08:34:41 2006 - Tue Mar 21 08:44:54 2006 CHECKING EXTENT REGIONS. Read twigs 5323 Time interval: Tue Mar 21 08:44:54 2006 - Tue Mar 21 08:46:14 2006 LOOKING FOR UNCONNECTED NODES Read nodes 0 Good nodes 0 Leaves of them 0, Twigs of them 0 Time interval: Tue Mar 21 08:46:14 2006 - Tue Mar 21 08:46:14 2006 CHECKING EXTENT REGIONS. Read twigs 0 Time interval: Tue Mar 21 08:46:14 2006 - Tue Mar 21 08:46:14 2006 INSERTING UNCONNECTED NODES 1. Twigs: done 2. Twigs by item: done 3. Leaves: done 4. Leaves by item: done Twigs: read 0, inserted 0, by item 0, empty 0 Leaves: read 0, inserted 0, by item 0 Time interval: Tue Mar 21 08:46:14 2006 - Tue Mar 21 08:46:14 2006 CHECKING SEMANTIC TREE FSCK: Node (762207), item (5), [6f6e9:6e6577:6f6eb] (stat40): wrong size (20), Fixed to (21). FSCK: Node (762207), item (5), [6f6e9:6e6577:6f6eb] (stat40): wrong bytes (2473), Fixed to (2605). FSCK: Node (773635), item (5), [6f62a:6e6577:6f62c] (stat40): wrong size (6), Fixed to (7). FSCK: Node (773635), item (5), [6f62a:6e6577:6f62c] (stat40): wrong bytes (628), Fixed to (760). FSCK: Node (773635), item (6), [6f62a:746d70:6f62b] (stat40): wrong size (4), Fixed to (3). FSCK: Node (773635), item (6), [6f62a:746d70:6f62b] (stat40): wrong bytes (312), Fixed to (206). Found 395956 objects. Time interval: Tue Mar 21 08:46:14 2006 - Tue Mar 21 09:28:41 2006 CLEANUPING STORAGE TREE ... --- (once more, excuse me, I have copied it from xterm while it was 'cleanuping storage tree', so it's not the full log). wrong bytes is not a big problem, reiser4 indeed counted them wrongly some time ago, although it seems to be fixed already. the only serious problem here is at the beginning of the 'CHECKING STORAGE TREE' pass -- there must not be a key [0:0(NAME):0:0:0]. After second fsck, I have unmounted and mounted it read only to save data on ext3 partition and to wait answers and suggestions before using reiser4 once more. which reiser4progs version do you use? it is already difficult to say why this strange key appeared -- you have already run several build-fs runs -- although it may be related to remount (I remember we used to have some problems before) or to fsck --build-fs. unmount you fs please and run 'fsck --check' on the unmounted fs -- check that all is right there now. which kernel version do you use? -- Vitaly
Re: Reiser4 problems on gentoo 2.6.14-rc1-mm1
Hello I believe it is fixed in 2.6.14-rc2-mm2. Please use it. PS: if it still does not work - try to set REISER4_USE_EFLUSH macro (it is in file fs/reiser4/reiser4.h) to 1. If that does not help - please report. Václav Hůla wrote: Hi, i'm getting frequent lockups in my testing chrooted environment (Athlon XP, gcc version 3.4.4 (Gentoo 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8)) during emerge. When this occurs, further operations on the reiser4 partitions are impossible, and following can be found in /var/log/messages. Rest of the system (on reiser v3 partition) works fine. Oct 7 12:28:12 cit2 kernel: [ cut here ] Oct 7 12:28:12 cit2 kernel: Modules linked in: usbnet it87 hwmon_vid i2c_isa i2c_viapro ipt_state ipt_MASQUERADE ipt_LOG iptable_nat ip_conntrack iptable_mangle iptable_filter ip_tables snd_pcm_oss snd_mixe r_oss snd_seq_oss snd_seq_midi_event snd_seq snd_cmipci snd_opl3_lib snd_hwdep snd_via82xx snd_ac97_codec snd_ac97_bus snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcor e sd_mod vfat fat usbhid usb_storage ehci_hcd via_agp agpgart wacom radeonfb i2c_algo_bit cfbcopyarea cfbimgblt cfbfillrect i2c_core softcursor Oct 7 12:28:12 cit2 kernel: CPU:0 Oct 7 12:28:12 cit2 kernel: EIP:0060:[c01cdc0b]Not tainted VLI Oct 7 12:28:12 cit2 kernel: EFLAGS: 00010297 (2.6.14-rc1-mm1) Oct 7 12:28:12 cit2 kernel: EIP is at sub_from_ctx_grabbed+0x3b/0x50 Oct 7 12:28:12 cit2 kernel: eax: ebx: ecx: 0001 edx: Oct 7 12:28:12 cit2 kernel: esi: cc7ce940 edi: d1e04000 ebp: c2629c60 esp: c07f3d44 Oct 7 12:28:12 cit2 kernel: ds: 007b es: 007b ss: 0068 Oct 7 12:28:12 cit2 kernel: Process ld (pid: 31883, threadinfo=c07f2000 task=ccaa2580) Oct 7 12:28:12 cit2 kernel: Stack: 0001 c01cec2f cc7ce940 0001 d485fec0 d485fec0 Oct 7 12:28:12 cit2 kernel:cc2876c0 c01d0b4d cc2876c0 0001 d485fec0 d485fec0 c2629d0c Oct 7 12:28:12 cit2 kernel:c01d0bac d485fec0 cc2876c0 c01d0bde d485fec0 c07f3e2c Oct 7 12:28:12 cit2 kernel: Call Trace: Oct 7 12:28:12 cit2 kernel: [c01cec2f] grabbed2flush_reserved_nolock+0x3f/0x80 Oct 7 12:28:12 cit2 kernel: [c01d0b4d] do_jnode_make_dirty+0x11d/0x150 Oct 7 12:28:12 cit2 kernel: [c01d0bac] jnode_make_dirty_locked+0x2c/0x40 Oct 7 12:28:12 cit2 kernel: [c01d0bde] znode_make_dirty+0x1e/0x90 Oct 7 12:28:12 cit2 kernel: [c01e9a72] update_sd_at+0xd2/0x220 Oct 7 12:28:12 cit2 kernel: [c01e9949] locate_inode_sd+0xa9/0x100 Oct 7 12:28:12 cit2 kernel: [c01e9c3b] update_sd+0x7b/0xa0 Oct 7 12:28:12 cit2 kernel: [c01dc920] reiser4_dirty_inode+0x0/0xa0 Oct 7 12:28:12 cit2 kernel: [c01e8ba0] write_sd_by_inode_common+0xb0/0xc0 Oct 7 12:28:12 cit2 kernel: [c01c34ec] jrelse_tail+0x3c/0x50 Oct 7 12:28:12 cit2 kernel: [c01e0638] reiser4_update_sd+0x28/0x40 Oct 7 12:28:12 cit2 kernel: [c01dc920] reiser4_dirty_inode+0x0/0xa0 Oct 7 12:28:12 cit2 kernel: [c01dc94c] reiser4_dirty_inode+0x2c/0xa0 Oct 7 12:28:12 cit2 kernel: [c01dc920] reiser4_dirty_inode+0x0/0xa0 Oct 7 12:28:12 cit2 kernel: [c017849b] __mark_inode_dirty+0xdb/0x190 Oct 7 12:28:12 cit2 kernel: [c011a13d] current_fs_time+0x4d/0x60 Oct 7 12:28:12 cit2 kernel: [c016fc46] update_atime+0x66/0xa0 Oct 7 12:28:12 cit2 kernel: [c01ec884] read_unix_file+0x394/0x400 Oct 7 12:28:12 cit2 kernel: [c01547ac] vfs_read+0x1ac/0x1c0 Oct 7 12:28:12 cit2 kernel: [c0154b11] sys_read+0x51/0x80 Oct 7 12:28:12 cit2 kernel: [c0102d5f] sysenter_past_esp+0x54/0x75 Oct 7 12:28:12 cit2 kernel: Code: 24 14 8b 4c 24 10 8b 56 60 8b 46 5c 39 da 76 15 29 c8 19 da 89 46 5c 89 56 60 8b 1c 24 8b 74 24 04 83 c4 08 c3 72 04 39 c8 73 e5 0f 0b 95 00 f8 e7 37 c0 eb db 8d 74 26 00 8d bc 27 00 00 00 00 Oct 7 12:28:12 cit2 kernel: 4reiser4[ld(31883)]: release_unix_file (fs/reiser4/plugin/file/file.c:2683)[vs-44]: Oct 7 12:28:12 cit2 kernel: WARNING: out of memory? Oct 7 12:28:12 cit2 kernel: reiser4[ld(31883)]: release_unix_file (fs/reiser4/plugin/file/file.c:2683)[vs-44]: Oct 7 12:28:12 cit2 kernel: WARNING: out of memory? Oct 7 12:28:12 cit2 kernel: reiser4[ld(31883)]: release_unix_file (fs/reiser4/plugin/file/file.c:2683)[vs-44]: Oct 7 12:28:12 cit2 kernel: WARNING: out of memory? Ax
Re: Reiser4 problems on gentoo 2.6.14-rc1-mm1
Dne středa 12 října 2005 13:17 Vladimir V. Saveliev napsal(a): Hello I believe it is fixed in 2.6.14-rc2-mm2. Please use it. PS: if it still does not work - try to set REISER4_USE_EFLUSH macro (it is in file fs/reiser4/reiser4.h) to 1. If that does not help - please report. But I cannot compile 2.6.14-rc2-mm2: CC fs/reiser4/debug.o In file included from fs/reiser4/lock.h:15, from fs/reiser4/context.h:14, from fs/reiser4/debug.c:25: fs/reiser4/txnmgr.h: In function `spin_atom_init': fs/reiser4/txnmgr.h:512: error: duplicate case value fs/reiser4/txnmgr.h:512: error: previously used here fs/reiser4/txnmgr.h: In function `spin_txnh_init': fs/reiser4/txnmgr.h:513: error: duplicate case value fs/reiser4/txnmgr.h:513: error: previously used here fs/reiser4/txnmgr.h: In function `spin_txnmgr_init': fs/reiser4/txnmgr.h:514: error: duplicate case value fs/reiser4/txnmgr.h:514: error: previously used here In file included from fs/reiser4/context.h:14, from fs/reiser4/debug.c:25: fs/reiser4/lock.h: In function `spin_stack_init': fs/reiser4/lock.h:198: error: duplicate case value fs/reiser4/lock.h:198: error: previously used here In file included from fs/reiser4/znode.h:16, from fs/reiser4/tree.h:15, from fs/reiser4/super.h:9, from fs/reiser4/debug.c:26: fs/reiser4/jnode.h: In function `spin_jnode_init': fs/reiser4/jnode.h:344: error: duplicate case value fs/reiser4/jnode.h:344: error: previously used here fs/reiser4/jnode.h: In function `spin_jload_init': fs/reiser4/jnode.h:348: error: duplicate case value fs/reiser4/jnode.h:348: error: previously used here In file included from fs/reiser4/super.h:9, from fs/reiser4/debug.c:26: fs/reiser4/tree.h: In function `spin_epoch_init': fs/reiser4/tree.h:169: error: duplicate case value fs/reiser4/tree.h:169: error: previously used here In file included from fs/reiser4/debug.c:26: fs/reiser4/super.h: In function `spin_super_init': fs/reiser4/super.h:379: error: duplicate case value fs/reiser4/super.h:379: error: previously used here make[2]: *** [fs/reiser4/debug.o] Error 1 make[1]: *** [fs/reiser4] Error 2 make: *** [fs] Error 2 Ax -- Václav Hůla, správce poštovního serveru Přírodovědecká fakulta Univerzita Karlova v Praze
Re: Reiser4 problems on gentoo 2.6.14-rc1-mm1
V?clav H?la wrote (ao): Dne st?eda 12 ??jna 2005 13:17 Vladimir V. Saveliev napsal(a): I believe it is fixed in 2.6.14-rc2-mm2. Please use it. PS: if it still does not work - try to set REISER4_USE_EFLUSH macro (it is in file fs/reiser4/reiser4.h) to 1. If that does not help - please report. But I cannot compile 2.6.14-rc2-mm2: This patch works for me: http://marc.theaimsgroup.com/?l=reiserfsm=112806903501734w=4 -- Humilis IT Services and Solutions http://www.humilis.net
Re: Reiser4 problems on gentoo 2.6.14-rc1-mm1
Hi. Dne středa 12 října 2005 13:17 Vladimir V. Saveliev napsal(a): Hello I believe it is fixed in 2.6.14-rc2-mm2. Please use it. PS: if it still does not work - try to set REISER4_USE_EFLUSH macro (it is in file fs/reiser4/reiser4.h) to 1. If that does not help - please report. After patching (thanks Sander) I managed to compile 2.6.14-rc2-mm2, looks working. (after one-and-half hour of compiling no errors in syslog) Ax -- Václav Hůla, správce poštovního serveru Přírodovědecká fakulta Univerzita Karlova v Praze
Re: reiser4 problems on amd64: things to try?
Hello On Mon, 2005-01-03 at 20:37, Sander wrote: Hello all, Tomorrow morning I'll reinstall (and reformat to reiser3) a dual Opteron which has a troublesome reiser4 fs. Should I run some tests, or retrieve some debug info from the reiser4 fs before I reformat? Please describe the problem you had with reiser4. Sorry, if you did that already. Then please do that one more time.
Re: reiser4 problems on amd64: things to try?
Hi, For some reason mails to the mailinglist don't make it. Also not to the archives, but I got no error back yet. And www.namesys.com was unreachable this morning (GMT+1). Vladimir Saveliev wrote (ao): On Mon, 2005-01-03 at 20:37, Sander wrote: Tomorrow morning I'll reinstall (and reformat to reiser3) a dual Opteron which has a troublesome reiser4 fs. Should I run some tests, or retrieve some debug info from the reiser4 fs before I reformat? Please describe the problem you had with reiser4. This was on kernel 2.6.10-rc3-mm1. bonnie++ went just fine with reiser4 on top of disk, raid0, raid1, raid5 and raid10. apt-get (Debian) on reiser4 raid10 gave segfaults so I let that run om tmpfs. I believe useradd also gave segfaults an crashed the system. Not sure though. I've reformatted the system already to reiser3, but I might be able to do some tests on reiser4 on a loopback device? -- Humilis IT Services and Solutions http://www.humilis.net
Re: reiser4 problems in 2.6.10-rc1-mm
-- and then at Fri, 19 Nov 2004 07:41:24 +, it was written ... Re: 2.6.10-rc2-mm1: oops when accessing reiser4 fs's(maybe fix provided) on this very same list, since Mathieu Segaud seemed to have problems similar to mine. This did indeed fix my bootup oopsing problems, however the filesystem still oopses+segfaults some important applications - ie apt-get as described in the previous post. Still getting the apt-get update BUG failure with 2.6.10-rc2-mm3. As reported under a different thread, there seems to be a sometimes factor involved, which doesn't help at all. cheers, Cal
Re: reiser4 problems in 2.6.10-rc1-mm
On 11/19/04 15:44:01, Cal wrote: and then at Fri, 19 Nov 2004 12:42:45 +0100, it was written ... Could you try 2.6.10-rc2-mm2, reiser4 is pretty stable in this tree, and contains more fix bits. Didn't have the time yet, but seems Cal has.. Lost in the alchemy, I didn't notice the update, so thanks for the update pointer. The problem still happens in 2.6.10-rc2-mm2:- [snip kernel oops] Last night, with a blend of about 60/40 alchemy/engineering, I merged base 2.6.10-rc2 with 2.6.10-rc2-bk3, reiser4-for-2.6.10-rc1, selected fixes from 2.6.10-mm1 and the reiserfs mailing list, plus ck patches. So far that build performs just fine. Now I guess I need to figure out the difference between that and 2.6.10-mm2. That said, I cheerfully acknowledge that the mm series is the best place to be if using reiser4. Wow... while you're figuring out which part fixes it, do you mind diffing your tree against 2.6.10-rc2-mm2 and posting the patch? I'll gladly try it out... might even take a look at the difference in the reiser code to see what's been changed (on the assumption that it's reiser4 that's causing the problem, and not some sideeffect). Cheers, Kacper -- Please do not cc: me. I'm on the list. I read the list, really I do. I do not need HTML email, virus warnings or unsolicited forwards. Get my GnuPG public key from pgp.mit.edu. Signed mail preferred. Please encrypt where appropriate. pgpBUipU2XBym.pgp Description: PGP signature
Re: reiser4 problems in 2.6.10-rc1-mm
However, should anyone more knowledgable about reiser4 have any ideas as to what's causing this oops, I'd be more than happy to debug a little further. Just so you don't feel so alone: I'm having the same problems (apt-get update), so you're not alone. I haven't spoken up earlier because as yet, I don't have anything constructive to offer. But I'm trying! cheers, Cal .
Re: reiser4 problems in 2.6.10-rc1-mm
Cal [EMAIL PROTECTED] disait dernièrement que : However, should anyone more knowledgable about reiser4 have any ideas as to what's causing this oops, I'd be more than happy to debug a little further. Just so you don't feel so alone: I'm having the same problems (apt-get update), so you're not alone. I haven't spoken up earlier because as yet, I don't have anything constructive to offer. But I'm trying! Could you try 2.6.10-rc2-mm2, reiser4 is pretty stable in this tree, and contains more fix bits. cheers, Cal . -- Looks clean and obviously correct to me, but then _everything_ I write always looks obviously correct yo me. - Linus
Re: reiser4 problems in 2.6.10-rc1-mm
and then at Fri, 19 Nov 2004 12:42:45 +0100, it was written ...
Could you try 2.6.10-rc2-mm2, reiser4 is pretty stable in this tree,
and contains more fix bits.
Lost in the alchemy, I didn't notice the update, so thanks for the
update pointer. The problem still happens in 2.6.10-rc2-mm2:-
kernel BUG at fs/reiser4/plugin/file/tail_conversion.c:58!
invalid operand: [#1]
PREEMPT SMP
Modules linked in: snd_emu10k1 snd_rawmidi snd_seq_device
snd_ac97_codec snd_pcm snd_rtctimer snd_timer snd_page_alloc
snd_util_mem snd_hwdep snd soundcore i2c_viapro i2c_core usbhid
uhci_hcd usbcore 8139too mii crc32 pcspkr CPU:1
EIP:0060:[c0215f09]Not tainted VLI
EFLAGS: 00210282 (2.6.10-rc2-mm2)
EIP is at get_nonexclusive_access+0x29/0x40
eax: f6fbdf1c ebx: f5e42c58 ecx: f78a2040 edx: f5e42be0
esi: f5e42c18 edi: f5e42be0 ebp: f6d508b4 esp: f6fbdc40
ds: 007b es: 007b ss: 0068
Process apt-get (pid: 2314, threadinfo=f6fbc000 task=f784b570)
Stack: c0214be0 f5e42be0 f7906400
Call Trace:
[c0214be0] unix_file_filemap_nopage+0x50/0xa0
[c0148c1e] do_no_page+0xce/0x3a0
[c02fb958] io_schedule+0x28/0x40
[c014911e] handle_mm_fault+0x10e/0x1b0
[c0147475] follow_page+0x25/0x30
[c01475f8] get_user_pages+0x138/0x3c0
[c0214037] reiser4_get_user_pages+0x97/0xd0
[c0214714] read_unix_file+0x2f4/0x310
[c016362d] inode_get_bytes+0x3d/0x60
[c01cf8dc] init_context+0x6c/0xa0
[c01e77f7] reiser4_read+0x77/0xc0
[c0158b3d] vfs_read+0xed/0x190
[c0158eb1] sys_read+0x51/0x80
[c0102983] syscall_call+0x7/0xb
Code: 00 00 b8 00 e0 ff ff 8b 54 24 04 21 e0 8b 00 8b 80 e0 04 00 00
8b 40 4c 8b 48 10 85 c9 75 0c 89 d0 f0 ff 00 0f 88 52 12 00 00 c3 0f
0b 3a 00 00 7e 32 c0 eb ea 8d b6 00 00 00 00 8d bc 27 00
00
Last night, with a blend of about 60/40 alchemy/engineering, I merged
base 2.6.10-rc2 with 2.6.10-rc2-bk3, reiser4-for-2.6.10-rc1, selected
fixes from 2.6.10-mm1 and the reiserfs mailing list, plus ck patches.
So far that build performs just fine. Now I guess I need to figure
out the difference between that and 2.6.10-mm2. That said, I
cheerfully acknowledge that the mm series is the best place to be if
using reiser4.
cheers, Cal
Re: reiser4 problems in 2.6.10-rc1-mm
On 11/16/04 23:55:53, Kacper Wysocki wrote: Hello, I decided to try out reiser4 yesterday, when I got a new harddrive for my laptop. In the process, I had some terrible problems, and gave up after a good full day of trying to make it work. [snip] Steps to reproduce: run 'apt-get update' (or any apt-get command really, and some other apps as well). 'apt-get update' will fetch all the index files and then oops on 'reading package lists..' First time after reboot: recoverable kernel oops. Second time: process enters unkillable sleep, as does strace and gdb when attempting to attach to it. [snip] Hi, I'm replying to my own message here, but I made some progress on this today: after basically restoring the filesystem again, I used the missing context fix patch from the thread Re: 2.6.10-rc2-mm1: oops when accessing reiser4 fs's(maybe fix provided) on this very same list, since Mathieu Segaud seemed to have problems similar to mine. This did indeed fix my bootup oopsing problems, however the filesystem still oopses+segfaults some important applications - ie apt-get as described in the previous post. I'm not posting the new (slightly different)oops here, as I noticed that the previous oopses were a little hard to read due to all the syslog crap, and I'm not sure anyone's interested, since I did not receive any replies to my previous post. Also, my reiserfs (v3) partition seems to be working fine (this mere fact rules out a corrupted file system due to usb tranfer errors and most possibilities of physical problems with my new harddrive). However, should anyone more knowledgable about reiser4 have any ideas as to what's causing this oops, I'd be more than happy to debug a little further. Cheers, Kacper pgpE8eoqxcBkN.pgp Description: PGP signature
