Reiser4 crash

Reiser4 crash

[Hubert (Chan) Chathi]

Reiser4 sometimes crashes:

2007-10-17_14:59:54.11562 kern.alert: [54537.551000] BUG: unable to handle kernel NULL pointer dereference at virtual address 00000000
2007-10-17_14:59:54.16463 kern.alert: [54537.551000]  printing eip:
2007-10-17_14:59:54.16467 kern.warn: [54537.551000] c01f5fd3
2007-10-17_14:59:54.16470 kern.alert: [54537.551000] *pde = 00000000
2007-10-17_14:59:54.16472 <0>[54537.551000] Oops: 0000 [#1]
2007-10-17_14:59:54.16475 <0>[54537.551000] PREEMPT
2007-10-17_14:59:54.16477 kern.warn: [54537.551000] Modules linked in: isofs nls_utf8 udf ext3 jbd mbcache sd_mod firewire_sbp2 usblp wacom dock af_packet video thermal fan button processor ac battery cpufreq_powersave cpufreq_ondemand cpufreq_conservative binfmt_misc ipt_ULOG nf_conntrack_ipv4 xt_state xt_tcpudp ip6table_filter ip6_tables ipv6 iptable_filter ip_tables ipt_REJECT ip_queue nf_conntrack_ftp nf_conntrack nfnetlink x_tables deflate twofish twofish_common camellia serpent des ecb aes xcbc sha256 sha1 md5 crypto_null af_key blowfish cbc blkcipher fuse dm_crypt dm_mod nvram radeon drm cpufreq_userspace sg sr_mod sbp2 scsi_mod usbhid irtty_sir sir_dev pcmcia snd_intel8x0m snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss firewire_ohci firewire_core nsc_ircc ipw2100 ir
 da crc_itu_t snd_pcm snd_timer parport_pc parport ide_cd i2c_i801 ieee80211 ieee80211_crypt rtc crc_ccitt e1000 snd soundcore snd_page_alloc cdrom firmware_class ohci1394 ieee1394 yenta_socket rsrc_nonstatic pcmcia_core ehci_hcd uhci_hcd intel_agp agpgart evdev usbcore unix
2007-10-17_14:59:54.16500 <0>[54537.551000] CPU:    0
2007-10-17_14:59:54.16503 <0>[54537.551000] EIP:    0060:[<c01f5fd3>]    Not tainted VLI
2007-10-17_14:59:54.16505 <0>[54537.551000] EFLAGS: 00010286   (2.6.22.1 #1)
2007-10-17_14:59:54.16508 <0>[54537.551000] EIP is at reiser4_tree_by_page+0x3/0x20
2007-10-17_14:59:54.16511 <0>[54537.551000] eax: 00000000   ebx: 00000000   ecx: 00000001   edx: eec19024
2007-10-17_14:59:54.16513 <0>[54537.551000] esi: c1472aa0   edi: c1472aa0   ebp: e718de20   esp: e718dd2c
2007-10-17_14:59:54.16516 <0>[54537.551000] ds: 007b   es: 007b   fs: 0000  gs:
0033  ss: 0068
2007-10-17_14:59:54.16519 <0>[54537.551000] Process sshd (pid: 426, ti=e718c000
task=d9b974a0 task.ti=e718c000)
2007-10-17_14:59:54.16521 <0>[54537.551000] Stack: c01e016a 00000000 7377642b 00706173 00000000 c1472aa0 e718de3c e718de20
2007-10-17_14:59:54.16524 <0>[54537.551000]        c020580c e718de20 00000001 00000000 00000002 00000002 00000002 00000000
2007-10-17_14:59:54.16527 <0>[54537.551000]        00000000 00000000 eec19024 00000000 00000000 00000001 eec0fea8 eec19024
2007-10-17_14:59:54.16530 <0>[54537.551000] Call Trace:
2007-10-17_14:59:54.16534 <0>[54537.551000]  [<c01e016a>] jnode_of_page+0x1a/0x270
2007-10-17_14:59:54.16537 <0>[54537.551000]  [<c020580c>] uf_readpages_filler+0x11c/0x2d0
2007-10-17_14:59:54.16540 <0>[54537.551000]  [<c015a3cd>] read_cache_pages+0x8d/0xd0
2007-10-17_14:59:54.16542 <0>[54537.551000]  [<c02056f0>] uf_readpages_filler+0x0/0x2d0
2007-10-17_14:59:54.16545 <0>[54537.551000]  [<c02549a2>] __spin_lock_init+0x32/0x90
2007-10-17_14:59:54.16548 <0>[54537.551000]  [<c01eb5e3>] reiser4_txn_begin+0x43/0x60
2007-10-17_14:59:54.16550 <0>[54537.551000]  [<c01e8bf6>] _reiser4_init_context+0x66/0x90
2007-10-17_14:59:54.16553 <0>[54537.551000]  [<c0205a0a>] readpages_unix_file+0x4a/0xa0
2007-10-17_14:59:54.16555 <0>[54537.551000]  [<c02059c0>] readpages_unix_file+0x0/0xa0
2007-10-17_14:59:54.16558 <0>[54537.551000]  [<c0159dc4>] __do_page_cache_readahead+0x174/0x260
2007-10-17_14:59:54.16561 <0>[54537.551000]  [<c01530cf>] find_get_page+0x1f/0x60
2007-10-17_14:59:54.16563 <0>[54537.551000]  [<c0155aee>] filemap_nopage+0x14e/0x3b0
2007-10-17_14:59:54.16566 <0>[54537.551000]  [<c015fb9a>] __handle_mm_fault+0x12a/0x970
2007-10-17_14:59:54.16569 <0>[54537.551000]  [<c0174597>] generic_file_llseek+0x37/0xd0
2007-10-17_14:59:54.16571 <0>[54537.551000]  [<c0116399>] do_page_fault+0x259/0x620
2007-10-17_14:59:54.16574 <0>[54537.551000]  [<c0116320>] do_page_fault+0x1e0/0x620
2007-10-17_14:59:54.16577 <0>[54537.551000]  [<c0174560>] generic_file_llseek+0x0/0xd0
2007-10-17_14:59:54.16581 <0>[54537.551000]  [<c0116140>] do_page_fault+0x0/0x620
2007-10-17_14:59:54.16586 <0>[54537.551000]  [<c037891a>] error_code+0x6a/0x70
2007-10-17_14:59:54.16589 <0>[54537.551000]  =======================
2007-10-17_14:59:54.16592 <0>[54537.551000] Code: ff 8b 06 90 8d 74 26 00 e8 6b
af fe ff e9 fd fe ff ff 8b 06 bb fe ff ff ff e8 5a af fe ff e9 ec fe ff ff 90 90 90 90 90 8b 40 10 <8b> 00 8b 80 24 01 00 00 8b 80 9c 02 00 00 83 c0 3c c3 8d 74 26
2007-10-17_14:59:54.16595 <0>[54537.551000] EIP: [<c01f5fd3>] reiser4_tree_by_page+0x3/0x20 SS:ESP 0068:e718dd2c
2007-10-17_14:59:54.16598 kern.warn: [54537.553000] reiser4[sshd(426)]: release_unix_file (fs/reiser4/plugin/file/file.c:2409)[vs-44]:
2007-10-17_14:59:54.16601 kern.warn: [54537.553000] WARNING: out of memory?
2007-10-17_14:59:54.16603 kern.warn: [54537.553000] reiser4[sshd(426)]: release_unix_file (fs/reiser4/plugin/file/file.c:2409)[vs-44]:
2007-10-17_14:59:54.16606 kern.warn: [54537.553000] WARNING: out of memory?

I'm running Linux 2.6.22.1 with reiser4-for-2.6.22.patch.gz.  It seems
to be crashing on the filesystem that's running on top of a dmcrypt
device.

-- 
Hubert Chathi - Email/Jabber: hubert@uhoreg.ca - http://www.uhoreg.ca/
PGP/GnuPG key: 1024D/124B61FA   (Key available at wwwkeys.pgp.net)
Fingerprint: 96C5 012F 5F74 A5F7 1FF7  5291 AF29 C719 124B 61FA

Re: Reiser4 crash

[Edward Shishkin]

Hmm.. this is the bug encountered by Zan Lynx a long time ago.
So my fixup was insufficient. It seems some race take place here,
I will try to catch this..

Thanks,
Edward.

Hubert (Chan) Chathi wrote:

>Reiser4 sometimes crashes:
>
>2007-10-17_14:59:54.11562 kern.alert: [54537.551000] BUG: unable to handle kernel NULL pointer dereference at virtual address 00000000
>2007-10-17_14:59:54.16463 kern.alert: [54537.551000]  printing eip:
>2007-10-17_14:59:54.16467 kern.warn: [54537.551000] c01f5fd3
>2007-10-17_14:59:54.16470 kern.alert: [54537.551000] *pde = 00000000
>2007-10-17_14:59:54.16472 <0>[54537.551000] Oops: 0000 [#1]
>2007-10-17_14:59:54.16475 <0>[54537.551000] PREEMPT
>2007-10-17_14:59:54.16477 kern.warn: [54537.551000] Modules linked in: isofs nls_utf8 udf ext3 jbd mbcache sd_mod firewire_sbp2 usblp wacom dock af_packet video thermal fan button processor ac battery cpufreq_powersave cpufreq_ondemand cpufreq_conservative binfmt_misc ipt_ULOG nf_conntrack_ipv4 xt_state xt_tcpudp ip6table_filter ip6_tables ipv6 iptable_filter ip_tables ipt_REJECT ip_queue nf_conntrack_ftp nf_conntrack nfnetlink x_tables deflate twofish twofish_common camellia serpent des ecb aes xcbc sha256 sha1 md5 crypto_null af_key blowfish cbc blkcipher fuse dm_crypt dm_mod nvram radeon drm cpufreq_userspace sg sr_mod sbp2 scsi_mod usbhid irtty_sir sir_dev pcmcia snd_intel8x0m snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss firewire_ohci firewire_core nsc_ircc ipw2100 i
 rda crc_itu_t snd_pcm snd_timer parport_pc parport ide_cd i2c_i801 ieee80211 ieee80211_crypt rtc crc_ccitt e1000 snd soundcore snd_page_alloc cdrom firmware_class ohci1394 ieee1394 yenta_socket rsrc_nonstatic pcmcia_core ehci_hcd uhci_hcd intel_agp agpgart evdev usbcore unix
>2007-10-17_14:59:54.16500 <0>[54537.551000] CPU:    0
>2007-10-17_14:59:54.16503 <0>[54537.551000] EIP:    0060:[<c01f5fd3>]    Not tainted VLI
>2007-10-17_14:59:54.16505 <0>[54537.551000] EFLAGS: 00010286   (2.6.22.1 #1)
>2007-10-17_14:59:54.16508 <0>[54537.551000] EIP is at reiser4_tree_by_page+0x3/0x20
>2007-10-17_14:59:54.16511 <0>[54537.551000] eax: 00000000   ebx: 00000000   ecx: 00000001   edx: eec19024
>2007-10-17_14:59:54.16513 <0>[54537.551000] esi: c1472aa0   edi: c1472aa0   ebp: e718de20   esp: e718dd2c
>2007-10-17_14:59:54.16516 <0>[54537.551000] ds: 007b   es: 007b   fs: 0000  gs:
>0033  ss: 0068
>2007-10-17_14:59:54.16519 <0>[54537.551000] Process sshd (pid: 426, ti=e718c000
>task=d9b974a0 task.ti=e718c000)
>2007-10-17_14:59:54.16521 <0>[54537.551000] Stack: c01e016a 00000000 7377642b 00706173 00000000 c1472aa0 e718de3c e718de20
>2007-10-17_14:59:54.16524 <0>[54537.551000]        c020580c e718de20 00000001 00000000 00000002 00000002 00000002 00000000
>2007-10-17_14:59:54.16527 <0>[54537.551000]        00000000 00000000 eec19024 00000000 00000000 00000001 eec0fea8 eec19024
>2007-10-17_14:59:54.16530 <0>[54537.551000] Call Trace:
>2007-10-17_14:59:54.16534 <0>[54537.551000]  [<c01e016a>] jnode_of_page+0x1a/0x270
>2007-10-17_14:59:54.16537 <0>[54537.551000]  [<c020580c>] uf_readpages_filler+0x11c/0x2d0
>2007-10-17_14:59:54.16540 <0>[54537.551000]  [<c015a3cd>] read_cache_pages+0x8d/0xd0
>2007-10-17_14:59:54.16542 <0>[54537.551000]  [<c02056f0>] uf_readpages_filler+0x0/0x2d0
>2007-10-17_14:59:54.16545 <0>[54537.551000]  [<c02549a2>] __spin_lock_init+0x32/0x90
>2007-10-17_14:59:54.16548 <0>[54537.551000]  [<c01eb5e3>] reiser4_txn_begin+0x43/0x60
>2007-10-17_14:59:54.16550 <0>[54537.551000]  [<c01e8bf6>] _reiser4_init_context+0x66/0x90
>2007-10-17_14:59:54.16553 <0>[54537.551000]  [<c0205a0a>] readpages_unix_file+0x4a/0xa0
>2007-10-17_14:59:54.16555 <0>[54537.551000]  [<c02059c0>] readpages_unix_file+0x0/0xa0
>2007-10-17_14:59:54.16558 <0>[54537.551000]  [<c0159dc4>] __do_page_cache_readahead+0x174/0x260
>2007-10-17_14:59:54.16561 <0>[54537.551000]  [<c01530cf>] find_get_page+0x1f/0x60
>2007-10-17_14:59:54.16563 <0>[54537.551000]  [<c0155aee>] filemap_nopage+0x14e/0x3b0
>2007-10-17_14:59:54.16566 <0>[54537.551000]  [<c015fb9a>] __handle_mm_fault+0x12a/0x970
>2007-10-17_14:59:54.16569 <0>[54537.551000]  [<c0174597>] generic_file_llseek+0x37/0xd0
>2007-10-17_14:59:54.16571 <0>[54537.551000]  [<c0116399>] do_page_fault+0x259/0x620
>2007-10-17_14:59:54.16574 <0>[54537.551000]  [<c0116320>] do_page_fault+0x1e0/0x620
>2007-10-17_14:59:54.16577 <0>[54537.551000]  [<c0174560>] generic_file_llseek+0x0/0xd0
>2007-10-17_14:59:54.16581 <0>[54537.551000]  [<c0116140>] do_page_fault+0x0/0x620
>2007-10-17_14:59:54.16586 <0>[54537.551000]  [<c037891a>] error_code+0x6a/0x70
>2007-10-17_14:59:54.16589 <0>[54537.551000]  =======================
>2007-10-17_14:59:54.16592 <0>[54537.551000] Code: ff 8b 06 90 8d 74 26 00 e8 6b
>af fe ff e9 fd fe ff ff 8b 06 bb fe ff ff ff e8 5a af fe ff e9 ec fe ff ff 90 90 90 90 90 8b 40 10 <8b> 00 8b 80 24 01 00 00 8b 80 9c 02 00 00 83 c0 3c c3 8d 74 26
>2007-10-17_14:59:54.16595 <0>[54537.551000] EIP: [<c01f5fd3>] reiser4_tree_by_page+0x3/0x20 SS:ESP 0068:e718dd2c
>2007-10-17_14:59:54.16598 kern.warn: [54537.553000] reiser4[sshd(426)]: release_unix_file (fs/reiser4/plugin/file/file.c:2409)[vs-44]:
>2007-10-17_14:59:54.16601 kern.warn: [54537.553000] WARNING: out of memory?
>2007-10-17_14:59:54.16603 kern.warn: [54537.553000] reiser4[sshd(426)]: release_unix_file (fs/reiser4/plugin/file/file.c:2409)[vs-44]:
>2007-10-17_14:59:54.16606 kern.warn: [54537.553000] WARNING: out of memory?
>
>I'm running Linux 2.6.22.1 with reiser4-for-2.6.22.patch.gz.  It seems
>to be crashing on the filesystem that's running on top of a dmcrypt
>device.
>
>  
>

Re: Reiser4 crash

[Hubert Chathi]

On Thu, 18 Oct 2007 17:34:49 +0400, Edward Shishkin <edward@namesys.com> said:

> Hmm.. this is the bug encountered by Zan Lynx a long time ago.  So my
> fixup was insufficient. It seems some race take place here, I will try
> to catch this..

I haven't had this problem in a while. (no changes -- same kernel,
reiser4 versions)  Perhaps it was just a spurious hardware error.

> Hubert (Chan) Chathi wrote:

>Reiser4 sometimes crashes:
>> 
>> 2007-10-17_14:59:54.11562 kern.alert: [54537.551000] BUG: unable to
>> handle kernel NULL pointer dereference at virtual address 00000000
>> 2007-10-17_14:59:54.16463 kern.alert: [54537.551000] printing eip:
>> 2007-10-17_14:59:54.16467 kern.warn: [54537.551000] c01f5fd3
>> 2007-10-17_14:59:54.16470 kern.alert: [54537.551000] *pde = 00000000
>> 2007-10-17_14:59:54.16472 <0>[54537.551000] Oops: 0000 [#1]
>> 2007-10-17_14:59:54.16475 <0>[54537.551000] PREEMPT
>> 2007-10-17_14:59:54.16477 kern.warn: [54537.551000] Modules linked
>> in: isofs nls_utf8 udf ext3 jbd mbcache sd_mod firewire_sbp2 usblp
>> wacom dock af_packet video thermal fan button processor ac battery
>> cpufreq_powersave cpufreq_ondemand cpufreq_conservative binfmt_misc
>> ipt_ULOG nf_conntrack_ipv4 xt_state xt_tcpudp ip6table_filter
>> ip6_tables ipv6 iptable_filter ip_tables ipt_REJECT ip_queue
>> nf_conntrack_ftp nf_conntrack nfnetlink x_tables deflate twofish
>> twofish_common camellia serpent des ecb aes xcbc sha256 sha1 md5
>> crypto_null af_key blowfish cbc blkcipher fuse dm_crypt dm_mod nvram
>> radeon drm cpufreq_userspace sg sr_mod sbp2 scsi_mod usbhid irtty_sir
>> sir_dev pcmcia snd_intel8x0m snd_intel8x0 snd_ac97_codec ac97_bus
>> snd_pcm_oss snd_mixer_oss firewire_ohci firewire_core nsc_ircc
>> ipw2100 i
> rda crc_itu_t snd_pcm snd_timer parport_pc parport ide_cd i2c_i801
> ieee80211 ieee80211_crypt rtc crc_ccitt e1000 snd soundcore
> snd_page_alloc cdrom firmware_class ohci1394 ieee1394 yenta_socket
> rsrc_nonstatic pcmcia_core ehci_hcd uhci_hcd intel_agp agpgart evdev
> usbcore unix
>> 2007-10-17_14:59:54.16500 <0>[54537.551000] CPU: 0
>> 2007-10-17_14:59:54.16503 <0>[54537.551000] EIP: 0060:[<c01f5fd3>]
>> Not tainted VLI 2007-10-17_14:59:54.16505 <0>[54537.551000] EFLAGS:
>> 00010286 (2.6.22.1 #1) 2007-10-17_14:59:54.16508 <0>[54537.551000]
>> EIP is at reiser4_tree_by_page+0x3/0x20 2007-10-17_14:59:54.16511
>> <0>[54537.551000] eax: 00000000 ebx: 00000000 ecx: 00000001 edx:
>> eec19024 2007-10-17_14:59:54.16513 <0>[54537.551000] esi: c1472aa0
>> edi: c1472aa0 ebp: e718de20 esp: e718dd2c 2007-10-17_14:59:54.16516
>> <0>[54537.551000] ds: 007b es: 007b fs: 0000 gs: 0033 ss: 0068
>> 2007-10-17_14:59:54.16519 <0>[54537.551000] Process sshd (pid: 426,
>> ti=e718c000 task=d9b974a0 task.ti=e718c000) 2007-10-17_14:59:54.16521
>> <0>[54537.551000] Stack: c01e016a 00000000 7377642b 00706173 00000000
>> c1472aa0 e718de3c e718de20 2007-10-17_14:59:54.16524
>> <0>[54537.551000] c020580c e718de20 00000001 00000000 00000002
>> 00000002 00000002 00000000 2007-10-17_14:59:54.16527
>> <0>[54537.551000] 00000000 00000000 eec19024 00000000 00000000
>> 00000001 eec0fea8 eec19024 2007-10-17_14:59:54.16530
>> <0>[54537.551000] Call Trace: 2007-10-17_14:59:54.16534
>> <0>[54537.551000] [<c01e016a>] jnode_of_page+0x1a/0x270
>> 2007-10-17_14:59:54.16537 <0>[54537.551000] [<c020580c>]
>> uf_readpages_filler+0x11c/0x2d0 2007-10-17_14:59:54.16540
>> <0>[54537.551000] [<c015a3cd>] read_cache_pages+0x8d/0xd0
>> 2007-10-17_14:59:54.16542 <0>[54537.551000] [<c02056f0>]
>> uf_readpages_filler+0x0/0x2d0 2007-10-17_14:59:54.16545
>> <0>[54537.551000] [<c02549a2>] __spin_lock_init+0x32/0x90
>> 2007-10-17_14:59:54.16548 <0>[54537.551000] [<c01eb5e3>]
>> reiser4_txn_begin+0x43/0x60 2007-10-17_14:59:54.16550
>> <0>[54537.551000] [<c01e8bf6>] _reiser4_init_context+0x66/0x90
>> 2007-10-17_14:59:54.16553 <0>[54537.551000] [<c0205a0a>]
>> readpages_unix_file+0x4a/0xa0 2007-10-17_14:59:54.16555
>> <0>[54537.551000] [<c02059c0>] readpages_unix_file+0x0/0xa0
>> 2007-10-17_14:59:54.16558 <0>[54537.551000] [<c0159dc4>]
>> __do_page_cache_readahead+0x174/0x260 2007-10-17_14:59:54.16561
>> <0>[54537.551000] [<c01530cf>] find_get_page+0x1f/0x60
>> 2007-10-17_14:59:54.16563 <0>[54537.551000] [<c0155aee>]
>> filemap_nopage+0x14e/0x3b0 2007-10-17_14:59:54.16566
>> <0>[54537.551000] [<c015fb9a>] __handle_mm_fault+0x12a/0x970
>> 2007-10-17_14:59:54.16569 <0>[54537.551000] [<c0174597>]
>> generic_file_llseek+0x37/0xd0 2007-10-17_14:59:54.16571
>> <0>[54537.551000] [<c0116399>] do_page_fault+0x259/0x620
>> 2007-10-17_14:59:54.16574 <0>[54537.551000] [<c0116320>]
>> do_page_fault+0x1e0/0x620 2007-10-17_14:59:54.16577 <0>[54537.551000]
>> [<c0174560>] generic_file_llseek+0x0/0xd0 2007-10-17_14:59:54.16581
>> <0>[54537.551000] [<c0116140>] do_page_fault+0x0/0x620
>> 2007-10-17_14:59:54.16586 <0>[54537.551000] [<c037891a>]
>> error_code+0x6a/0x70 2007-10-17_14:59:54.16589 <0>[54537.551000]
>> ======================= 2007-10-17_14:59:54.16592 <0>[54537.551000]
>> Code: ff 8b 06 90 8d 74 26 00 e8 6b af fe ff e9 fd fe ff ff 8b 06 bb
>> fe ff ff ff e8 5a af fe ff e9 ec fe ff ff 90 90 90 90 90 8b 40 10
>> <8b> 00 8b 80 24 01 00 00 8b 80 9c 02 00 00 83 c0 3c c3 8d 74 26
>> 2007-10-17_14:59:54.16595 <0>[54537.551000] EIP: [<c01f5fd3>]
>> reiser4_tree_by_page+0x3/0x20 SS:ESP 0068:e718dd2c
>> 2007-10-17_14:59:54.16598 kern.warn: [54537.553000]
>> reiser4[sshd(426)]: release_unix_file
>> (fs/reiser4/plugin/file/file.c:2409)[vs-44]:
>> 2007-10-17_14:59:54.16601 kern.warn: [54537.553000] WARNING: out of
>> memory?  2007-10-17_14:59:54.16603 kern.warn: [54537.553000]
>> reiser4[sshd(426)]: release_unix_file
>> (fs/reiser4/plugin/file/file.c:2409)[vs-44]:
>> 2007-10-17_14:59:54.16606 kern.warn: [54537.553000] WARNING: out of
>> memory?
>> 
>> I'm running Linux 2.6.22.1 with reiser4-for-2.6.22.patch.gz.  It
>> seems to be crashing on the filesystem that's running on top of a
>> dmcrypt device.
>> 
>> 
>> 

-- 
Hubert Chathi - Email/Jabber: hubert@uhoreg.ca - http://www.uhoreg.ca/
PGP/GnuPG key: 1024D/124B61FA   (Key available at wwwkeys.pgp.net)
Fingerprint: 96C5 012F 5F74 A5F7 1FF7  5291 AF29 C719 124B 61FA

Reiser4 crash

[geearf]

Hello ML,

just to report one issue that I had yesterday with r4:

I restarted Xorg the hard way (ctrl alt backspace) without any real reason for that, just to try some different xorg.conf and then I could not log in KDE anymore (I had a bad crash the previous day so it could have been related).
Result was that certain files were corrupted and fsck.reiser4 did not fully help. To fix my issues I had to fsck the partition and manually remove anything in /tmp and /var/tmp from another OS. Removing anything in /var/tmp while using that partition as the OS would result in a crash even after fsck said everything was fixed...

What I saw in dmsg was pretty much the same we had a year ago when KDE4 was out, with the "out of memory?" warning and stuff till Edward fixed R4.


I am not sure how relevant this report is but I thought I would still give it...
I am using 2.6.27 with Edward's patch on Debian AMD64/Sid.


Thanks,
John

Re: Reiser4 crash

[Edward Shishkin]

geearf@free.fr wrote:
> Hello ML,
>
> just to report one issue that I had yesterday with r4:
>
> I restarted Xorg the hard way (ctrl alt backspace) without any real reason for that, just to try some different xorg.conf and then I could not log in KDE anymore (I had a bad crash the previous day so it could have been related).
> Result was that certain files were corrupted and fsck.reiser4 did not fully help. To fix my issues I had to fsck the partition and manually remove anything in /tmp and /var/tmp from another OS. Removing anything in /var/tmp while using that partition as the OS would result in a crash even after fsck said everything was fixed...
>   

It is reproducible?
Compression is disabled?

if both is "yes", then, please, pack the metadata by
debugfs.reiser4 -P /dev/xxx | gzip > meta.gz
and let me download the file meta.gz

> What I saw in dmsg was pretty much the same we had a year ago when KDE4 was out, with the "out of memory?" warning and stuff till Edward fixed R4.
>
>   

Yes, it looks like a bug in handling some special
case of incomplete conversion. Anyway, detailed
kernel complaints are highly desirable..

Thanks,
Edward.
> I am not sure how relevant this report is but I thought I would still give it...
> I am using 2.6.27 with Edward's patch on Debian AMD64/Sid.
>
>
> Thanks,
> John
>
> --
> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>   

Re: Reiser4 crash

[geearf]

----- Mail Original -----
De: "Edward Shishkin" <edward.shishkin@gmail.com>
À: geearf@free.fr
Cc: reiserfs-devel@vger.kernel.org
Envoyé: Dimanche 16 Novembre 2008 15:34:53 GMT -08:00 USA/Canada - États du Pacifique
Objet: Re: Reiser4 crash

geearf@free.fr wrote:
>> Hello ML,
>>
>> just to report one issue that I had yesterday with r4:
>>
>> I restarted Xorg the hard way (ctrl alt backspace) without any real reason for that, just to try some different xorg.conf and >>then I could not log in KDE anymore (I had a bad crash the previous day so it could have been related).
>> Result was that certain files were corrupted and fsck.reiser4 did not fully help. To fix my issues I had to fsck the partition >>and manually remove anything in /tmp and /var/tmp from another OS. Removing anything in /var/tmp while using that partition as >>the OS would result in a crash even after fsck said everything was fixed...
>>   

>It is reproducible?
I have no idea how, and I do not have much time to corrupt my system this week.
>Compression is disabled?
It was enabled

>if both is "yes", then, please, pack the metadata by
>debugfs.reiser4 -P /dev/xxx | gzip > meta.gz
>and let me download the file meta.gz

>> What I saw in dmsg was pretty much the same we had a year ago when KDE4 was out, with the "out of memory?" warning and stuff till Edward fixed R4.
>
>   

>Yes, it looks like a bug in handling some special
>case of incomplete conversion. Anyway, detailed
>kernel complaints are highly desirable..

>Thanks,
>Edward.

Sorry I did not keep any data after fixing the fs...

John
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Reiser4 crash

[Edward Shishkin]

Hubert Chathi <hubert () uhoreg ! ca>  wrote:
> On Thu, 18 Oct 2007 17:34:49 +0400, Edward Shishkin <edward@namesys.com> said:
>
> > Hmm.. this is the bug encountered by Zan Lynx a long time ago.  So my
> > fixup was insufficient. It seems some race take place here, I will try
> > to catch this..
>
> I haven't had this problem in a while. (no changes -- same kernel,
> reiser4 versions)  Perhaps it was just a spurious hardware error.

I would be more pessimistic ;)

>
> > Hubert (Chan) Chathi wrote:
>
> >Reiser4 sometimes crashes:
> >>
> >> 2007-10-17_14:59:54.11562 kern.alert: [54537.551000] BUG: unable to
> >> handle kernel NULL pointer dereference at virtual address 00000000
> >> 2007-10-17_14:59:54.16463 kern.alert: [54537.551000] printing eip:
> >> 2007-10-17_14:59:54.16467 kern.warn: [54537.551000] c01f5fd3
> >> 2007-10-17_14:59:54.16470 kern.alert: [54537.551000] *pde = 00000000
> >> 2007-10-17_14:59:54.16472 <0>[54537.551000] Oops: 0000 [#1]
> >> 2007-10-17_14:59:54.16475 <0>[54537.551000] PREEMPT
>

Re: Reiser4 crash

[Hubert Chathi]

On Thu, 15 Nov 2007 00:28:33 +0300, "Edward Shishkin" <edward.shishkin@gmail.com> said:

> Hubert Chathi <hubert () uhoreg ! ca>  wrote:
>> On Thu, 18 Oct 2007 17:34:49 +0400, Edward Shishkin
>> <edward@namesys.com> said:
>> 
>> > Hmm.. this is the bug encountered by Zan Lynx a long time ago.  So
>> my > fixup was insufficient. It seems some race take place here, I
>> will try > to catch this..
>> 
>> I haven't had this problem in a while. (no changes -- same kernel,
>> reiser4 versions) Perhaps it was just a spurious hardware error.

> I would be more pessimistic ;)

You're right.  Reiser4 was crashing fairly often until I reported the
problem on the list.  After I reported the problem, it stopped
crashing.  Now that I have said that all is now fine, it will surely
start crashing again! ;)

-- 
Hubert Chathi - Email/Jabber: hubert@uhoreg.ca - http://www.uhoreg.ca/
PGP/GnuPG key: 1024D/124B61FA   (Key available at wwwkeys.pgp.net)
Fingerprint: 96C5 012F 5F74 A5F7 1FF7  5291 AF29 C719 124B 61FA

reiser4 crash

[Andrew Benton]

I've been using reiser4 for a couple of months. A couple of days ago I
did something stupid with Abiword, the disk started thrashing and as the
system crashed it left this on the screen

------------[ cut here ]------------
kernel BUG at fs/reiser4/plugin/file/tail_conversion.c:58!
invalid operand:0000 [#1]
SMP
Modules linked in: nvidia
CPU:    0
EIP:    0060:[<c020144e>]    Tainted: P      VLI
EFLAGS: 00010282   (2.6.10-rc2-bk13)
EIP is at get_nonexclusive_access+0x29/0x33
eax: df033eac   ebx: df032000   ecx: d96fee80   edx: de5a70dc
esi: 00000000   edi: de5a70dc   ebp: de5a7144   esp:df033d84
ds: 007b   es: 007b   ss: 0068
Process syslogd (pid: 1488, threadinfo=df032000 task=df7df020)
Stack: c0200633 de5a70dc 0804dcc7 00000001 00000001 df033bdc 00000000
df032000
        00000000 00000001 00000001 00000001 00000000 00000001 00000001
c13a0a40
        de91d144 de91d10c c0200183 df033ddc 0804b000 c01c0492 d96fee80
00101cca
Call Trace:
[<c0200633>] write_unix_file+0x2a1/0x45b
[<c0200183>] unix_file_filemap_nopage+0xaa/0xcf
[<c01c0492>] atom_should_commit+0x5a/0x60
[<c01bd241>] init_context+0x75/0xb4
[<c01d3f46>] reiser4_write+0x8f/0xfc
[<c0261e36>] copy_from_user+0x42/0x70
[<c01524b0>] do_readv_writev+0x170/0x29a
[<c01d3eb7>] reiser4_write+0x0/0xfc
[<c037515f>] sys_recv+0x37/0x3b
[<c015268e>] vfs_writev+0x58/0x5c
[<c0152763>] sys_writev+0x51/0x80
[<c010264d>] sysenter_past_esp+0x52/0x71
Code: 00 c3 b8 00 e0 ff ff 21 e0 8b 00 8b 80 d4 04 00 00 8b 54 24 04 8b 
40 44 8b 48 0c 85 c9 75 0c 89 d0 f0 ff 00 0f 88 b8 11 00 00 c3 <0f> 0b 
3a 00 e4 58 43 c0 eb ea 8b 44 24 04 ba ff ff ff ff f0 0f

To me this looked very similar to 
http://www.uwsg.iu.edu/hypermail/linux/kernel/0411.3/0493.html so I 
applied Vladimir Saveliev's patch, recompiled and the patch seems to 
have done the trick.

# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
# 2004/11/23 14:07:34+03:00 vs@xxxxxxxxxxxxxxxxxxxxx
# read_unix_file: missing calls to txn_restart() are added
#
# plugin/file/file.c
# 2004/11/23 14:07:31+03:00 vs@xxxxxxxxxxxxxxxxxxxxx +4 -1
# read_unix_file: missing calls to txn_restart() are added
#
diff -Nru a/plugin/file/file.c b/plugin/file/file.c
--- a/plugin/file/file.c 2004-11-23 14:45:34 +03:00
+++ b/plugin/file/file.c 2004-11-23 14:45:34 +03:00
@@ -1741,6 +1741,8 @@
while (left > 0) {
size_t to_read;

+ txn_restart_current();
+
size = i_size_read(inode);
if (*off >= size)
/* position to read from is past the end of file */
@@ -1774,7 +1776,6 @@
if (user_space)
reiser4_put_user_pages(pages, nr_pages);
drop_nonexclusive_access(uf_info);
- txn_restart_current();

if (read < 0) {
result = read;
@@ -1974,6 +1975,8 @@

drop_nonexclusive_access(unix_file_inode_data(inode));
up_read(&reiser4_inode_data(inode)->coc_sem);
+
+ txn_restart_current();

reiser4_exit_context(&ctx);
return page;

Now if I give Abiword further abuse, memory fills, the disk thrashes but 
when the swap partition is about half full Abiword caves and the system 
recovers.

Re: reiser4 crash

[Frank Denis (Jedi/Sector One)]

On Sat, Dec 04, 2004 at 11:46:50AM +0000, Andrew Benton wrote:
> I've been using reiser4 for a couple of months. A couple of days ago I
> did something stupid with Abiword, the disk started thrashing and as the
> system crashed it left this on the screen

  You need that patch.

diff -urN linux-2.6.10-rc2-mm4/fs/reiser4/plugin/file/file.c /usr/src/linux-2.6.10-rc2-mm4-jedi1/fs/reiser4/plugin/file/file.c
--- linux-2.6.10-rc2-mm4/fs/reiser4/plugin/file/file.c	2004-12-03 22:31:54.502630648 +0100
+++ /usr/src/linux-2.6.10-rc2-mm4-jedi1/fs/reiser4/plugin/file/file.c	2004-12-03 22:17:11.113926144 +0100
@@ -1741,6 +1741,8 @@
 	while (left > 0) {
 		size_t to_read;		
 
+		txn_restart_current();
+
 		size = i_size_read(inode);
 		if (*off >= size)
 			/* position to read from is past the end of file */
@@ -1774,7 +1776,6 @@
 		if (user_space)
 			reiser4_put_user_pages(pages, nr_pages);
 		drop_nonexclusive_access(uf_info);
-		txn_restart_current();
 
 		if (read < 0) {
 			result = read;
@@ -1975,6 +1976,8 @@
 	drop_nonexclusive_access(unix_file_inode_data(inode));
 	up_read(&reiser4_inode_data(inode)->coc_sem);
 
+	txn_restart_current();
+
 	reiser4_exit_context(&ctx);
 	return page;
 }

--
Frank - my stupid blog: http://00f.net

Re: reiser4 crash

[Frank Denis (Jedi/Sector One)]

On Sat, Dec 04, 2004 at 11:46:50AM +0000, Andrew Benton wrote:
> To me this looked very similar to 
> http://www.uwsg.iu.edu/hypermail/linux/kernel/0411.3/0493.html

  Oops I didn't read the end of your mail :(
  
--
Frank - my stupid blog: http://00f.net

Re: reiser4 crash

[Mark Nipper]

[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]

On 04 Dec 2004, Andrew Benton wrote:
> I've been using reiser4 for a couple of months. A couple of days ago I
> did something stupid with Abiword, the disk started thrashing and as the
> system crashed it left this on the screen
<snipped>

	Which if you are trying to patch this against the current
Namesys 2.6.10-rc1 patches requires Saveliev's previous patch
from a couple of weeks ago which I've also attached to this
thread now as I'm in the middle of upgrading to 2.6.10-rc3 and
had to go looking for the previous patch myself.  :)

-- 
Mark Nipper                                                e-contacts:
4475 Carter Creek Parkway                           nipsy@bitgnome.net
Apartment 724                               http://nipsy.bitgnome.net/
Bryan, Texas, 77802-4481           AIM/Yahoo: texasnipsy ICQ: 66971617
(979)575-3193                                      MSN: nipsy@tamu.edu

-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GG/IT d- s++:+ a- C++$ UBL++++$ P--->+++ L+++$ !E---
W++(--) N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--)
Y+ PGP t+ 5 X R tv b+++@ DI+(++) D+ G e h r++ y+(**)
------END GEEK CODE BLOCK------

---begin random quote of the moment---
"I know the forces of spontaneous, emergent life are stronger
than the forces of evil, repression and death, and the forces of
death will destroy themselves."
 -- William S. Burroughs
----end random quote of the moment----

[-- Attachment #2: 1.1755 --]
[-- Type: text/plain, Size: 994 bytes --]

# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
#   2004/11/15 16:23:47+03:00 vs@tribesman.namesys.com 
#   unix_file_filemap_nopage: missing context creation is added
# 
# plugin/file/file.c
#   2004/11/15 16:23:45+03:00 vs@tribesman.namesys.com +5 -1
#   unix_file_filemap_nopage: missing context creation is added
# 
diff -Nru a/plugin/file/file.c b/plugin/file/file.c
--- a/plugin/file/file.c	2004-11-17 09:36:11 +03:00
+++ b/plugin/file/file.c	2004-11-17 09:36:11 +03:00
@@ -1961,8 +1961,10 @@
 {
 	struct page *page;
 	struct inode *inode;
-
+	reiser4_context ctx;
+	
 	inode = area->vm_file->f_dentry->d_inode;
+	init_context(&ctx, inode->i_sb);
 
 	/* block filemap_nopage if copy on capture is processing with a node of this file */
 	down_read(&reiser4_inode_data(inode)->coc_sem);
@@ -1972,6 +1974,8 @@
 
 	drop_nonexclusive_access(unix_file_inode_data(inode));
 	up_read(&reiser4_inode_data(inode)->coc_sem);
+
+	reiser4_exit_context(&ctx);
 	return page;
 }
 

Re: reiser4 crash

[Andrew Benton]

Mark Nipper wrote:

> <snipped>
> 
> 	Which if you are trying to patch this against the current
> Namesys 2.6.10-rc1 patches requires Saveliev's previous patch
> from a couple of weeks ago

Yes, that patch is in the current 2.6.10-rc2-mm4 patch. The fix, 
however, isn't.

RE: reiser4 crash

[Yiannis Mavroukakis]

 
I've been seeing people having trouble with reiser4 crashing and I'm jealous :-) I want
mine to crash too, it's not fair I haven't had a spot of trouble since I installed the 
patches my Unreal Tournament server hasn't gone down once! :P :P :P

Yiannis.

-----Original Message-----
From: Vladimir Saveliev [mailto:vs@namesys.com] 
Sent: 25 November 2004 16:55
To: hihone@bigpond.net.au
Cc: Markus Törnqvist; reiserfs-list@namesys.com
Subject: Re: reiser4 crash

Hello

On Thu, 2004-11-25 at 15:35, Cal wrote:
> ----------
> and then at Thu, 25 Nov 2004 14:05:45 +0200, it was written ...
>  >ftp://ftp.namesys.com/pub/reiser4-for-2.6/2.6.9/

There was an update today. Please make sure you got patch number 2.

>  >http://marc.theaimsgroup.com/?l=reiserfs&m=110121057720746&w=2
>  >
>  >It is possible the posted patch is included in the second patch  >at 
> namesys.
>  >
>  >I'd still like to know about the two -cko patches though, as I can't  
> >remember which ones they were (I'm at the office) and if they  
> >should be included and whatever....
>  >
> Cool, thanks!  I found the mailing list one, and with that applied to 
> 2.6.10-rc2-mm3, the first run of apt-get update completed 
> successfully.  That's good!
> 
> I've been looking after grandkids for a couple of days, so I missed 
> the recent 2.6.9 updates on ftp.namesys.com.  I'm more interested in 
> 2.6.10-rcx+, but l'll maybe take a look at the 2.6.9 stuff.
> 
> I'm a little confused about the cko reference.  I'm happily running
> 2.6.9-cko3 ona seconfd system, but I've not seen any breakdown of the 
> cko series (ie, the two particular cko patches you're referencing).
> 
> cheers, and thanks
> Cal
> 


________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs.

Note:__________________________________________________________________
This message is for the named person's use only. It may contain
confidential, proprietary or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission.
If you receive this message in error, please immediately delete it and
all copies of it from your system, destroy any hard copies of it and
notify the sender. You must not, directly or indirectly, use, disclose,
distribute, print, or copy any part of this message if you are not the
intended recipient. Jaguar Freight Services and any of its subsidiaries
each reserve the right to monitor all e-mail communications through its
networks.
Any views expressed in this message are those of the individual sender,
except where the message states otherwise and the sender is authorized
to state them to be the views of any such entity.
________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs.

reiser4 crash

[Sami Liedes]

Attached are the oops and fsck.reiser4 output.

This happened after using reiser4 for only 1,5 days.

	Sami


--- oops ---------------------------------------------------
kernel BUG at fs/reiser4/plugin/file/tail_conversion.c:32!
invalid operand: 0000 [#1]
PREEMPT
Modules linked in: ide_cd cdrom ipt_MASQUERADE ipt_REJECT ipt_state iptable_filter i2c_viapro ehci_hcd uhci_hcd usbcore via_agp evdev dm_mod i2c_isa i2c_core snd_via82xx snd_ac97_codec snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore radeon agpgart 8139too mii crc32 ip_nat_irc ip_nat_ftp iptable_nat ip_tables ip_conntrack_irc ip_conntrack_ftp ip_conntrack 3c59x lp parport af_packet
CPU:    0
EIP:    0060:[<c01c92f2>]    Not tainted VLI
EFLAGS: 00210286   (2.6.10-rc1)
EIP is at get_exclusive_access+0x32/0x40
eax: ce4dfc60   ebx: c5a64a84   ecx: c5a64a78   edx: 00000000
esi: 00000000   edi: c5a64a78   ebp: d9b97dec   esp: d9b97dec
ds: 007b   es: 007b   ss: 0068
Process aptitude (pid: 7704, threadinfo=d9b96000 task=c4bf6a00)
Stack: d9b97ed8 c01c855c 00000001 d9b97e44 d9b97dfc d9b97dfc d9b97e00 dea45ba0
       00000014 d9b96000 00000aa9 d9b96000 d9b96000 00000001 00000001 008a1470
       00000000 00000000 00000008 c5a64ad0 b6f19000 ddc5fba0 00008000 008a1470
Call Trace:
 [<c0104e7a>] show_stack+0x7a/0x90
 [<c0104ffd>] show_registers+0x14d/0x1b0
 [<c01051e4>] die+0xe4/0x170
 [<c0105674>] do_invalid_op+0xe4/0xf0
 [<c0104ab9>] error_code+0x2d/0x38
 [<c01c855c>] write_unix_file+0x1fc/0x4c0
 [<c01a0bbd>] reiser4_write+0x6d/0xb0
 [<c014c59f>] vfs_write+0xbf/0x110
 [<c014c6a1>] sys_write+0x41/0x70
 [<c01040af>] syscall_call+0x7/0xb
Code: ff 21 e0 89 e5 8b 00 8b 80 b8 04 00 00 8b 40 3c 8b 40 08 85 c0 75 14 ba 01 00 ff ff 89 c8 0f c1 10 85 d2 0f 85 ce 0f 00 00 c9 c3 <0f> 0b 20 00 40 90 2b c0 eb e2 8d 74 26 00 55 89 e5 ba ff ff 00
------------------------------------------------------------

--- fsck.reiser4 -------------------------------------------
# fsck.reiser4 /dev/hdd3
*******************************************************************
This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
*******************************************************************

Fscking the /dev/hdd3 block device.
Will check the consistency of the Reiser4 SuperBlock.
Will check the consistency of the Reiser4 FileSystem.
Continue?
(Yes/No): y
***** fsck.reiser4 started at Fri Nov 19 10:13:55 2004
Reiser4 journal (journal40) on /dev/hdd3: 0 transactions replayed of the total 0 blocks.
Reiser4 fs was detected on /dev/hdd3.
Master super block (16):
magic:          ReIsEr4
blksize:        4096
format:         0x0 (format40)
uuid:           bff15455-f079-4543-abff-da68ef05fcbe
label:          <none>

Format super block (17):
plugin:         format40
description:    Disk-format for reiser4, ver. 1.0.0
magic:          ReIsEr40FoRmAt
flushes:        0
mkfs id:        0x4a43a302
blocks:         49596671
free blocks:    34064528
root block:     15337898
tail policy:    0x2 (smart)
next oid:       0x98aa0
file count:     518379
tree height:    4
key policy:     LARGE


CHECKING STORAGE TREE
        Read nodes 357991
        Nodes left in the tree 357991
                Leaves of them 352551, Twigs of them 5356
        Time interval: Fri Nov 19 10:14:09 2004 - Fri Nov 19 10:16:42 2004
CHECKING EXTENT REGIONS.
        Read twigs 5356
        Time interval: Fri Nov 19 10:16:42 2004 - Fri Nov 19 10:17:11 2004
CHECKING SEMANTIC TREE
FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316682], item [1], unit [37]: entry has wrong offset
[7d8ff:0(NAME):130365f62657374:6d616e5f6c756b65:226514768dc110cd]. Should be
[7d8ff:0(NAME):130365f62657374:6d616e5f6c756b65:2265147666480f1d].
FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316682], item [1], unit [44]: entry has wrong offset
[7d8ff:0(NAME):132365f68e4e470:6172695f6d616c6a:92d8f19d65d95be]. Should be
[7d8ff:0(NAME):132365f68e4e470:6172695f6d616c6a:92d2e1933fbf67e].
FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316682], item [1], unit [47]: entry has wrong offset
[7d8ff:0(NAME):133305f53757669:5f6c61756c61615f:bd25b6a72855fe86]. Should be
[7d8ff:0(NAME):133305f53757669:5f6c61756c61615f:bd2555a4d3c14cb6].
FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316682], item [1], unit [51]: entry has wrong offset
[7d8ff:0(NAME):133365f41737472:69645f6ae46e6e69:16db1dfa6f08ba]. Should be [7d8ff:0(NAME):133365f41737472:69645f6ae46e6e69:16db1dd2f6070a].
FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316682], item [1], unit [52]: entry has wrong offset
[7d8ff:0(NAME):133375f69686d65:656c6c6973656e5f:9b778ff47749f37e]. Should be
[7d8ff:0(NAME):133375f69686d65:656c6c6973656e5f:d80e781b2fea179e].
FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316682], item [1], unit [55]: entry has wrong offset
[7d8ff:0(NAME):134305f796c6ce4:7479736d756e6961:40640ac5d13ba022]. Should be
[7d8ff:0(NAME):134305f796c6ce4:7479736d756e6961:4063a8f81c2f3c82].
FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316682], item [1], unit [56]: entry has wrong offset
[7d8ff:0(NAME):134315f796c6ce4:74796b73657373e4:1bd83c4b92407]. Should be [7d8ff:0(NAME):134315f796c6ce4:74796b73657373e4:1b4b2452fa157].
FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316682], item [1], unit [57]: entry has wrong offset
[7d8ff:0(NAME):134325f41737472:69645f6a616b6161:d15a16be63d261bd]. Should be
[7d8ff:0(NAME):134325f41737472:69645f6a616b6161:a86ba0c7a2097cad].
FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316682], item [1], unit [58]: entry has wrong offset
[7d8ff:0(NAME):134335f41737472:69645f6a616b6161:f394bffd7800956b]. Should be
[7d8ff:0(NAME):134335f41737472:69645f6a616b6161:9adefe5be00c50db].
FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [1]: entry has wrong offset
[7d8ff:0(NAME):134375f52697374:6f5f7475746b6969:f9c07c6a924c893]. Should be
[7d8ff:0(NAME):134375f52697374:6f5f7475746b6969:da3b247a1b994e3].
FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [3]: entry has wrong offset
[7d8ff:0(NAME):134395f796c6569:736b7576615f68e4:3eb28bdf41f7c]. Should be [7d8ff:0(NAME):134395f796c6569:736b7576615f68e4:ffffb751cef2d5ec].
FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [4]: entry has wrong offset
[7d8ff:0(NAME):135305f796c6569:736b7576615f68e4:1da264211f344b2]. Should be
[7d8ff:0(NAME):135305f796c6569:736b7576615f68e4:ffdda5ab1a577fa2].
FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [6]: entry has wrong offset
[7d8ff:0(NAME):135335f43796265:72746f702d6d6965:b20dc6112b27f52]. Should be
[7d8ff:0(NAME):135335f43796265:72746f702d6d6965:ccfc58ed8054c342].
FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [8]: entry has wrong offset
[7d8ff:0(NAME):135355f4b696d6d:6f5f6a6f6e676cf6:74232d69e18ad511]. Should be
[7d8ff:0(NAME):135355f4b696d6d:6f5f6a6f6e676cf6:6de148b3d7414451].
FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [9]: entry has wrong offset
[7d8ff:0(NAME):135365f746f696e:656e5f6c61686a61:4aa9262d28f]. Should be [7d8ff:0(NAME):135365f746f696e:656e5f6c61686a61:3dd30c60acf].
FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [13]: entry has wrong offset
[7d8ff:0(NAME):136305f73756c68:6173656e5f7279f6:920d173e51c09120]. Should be
[7d8ff:0(NAME):136305f73756c68:6173656e5f7279f6:123bb47cc8f6ecb0].
FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [14]: entry has wrong offset
[7d8ff:0(NAME):136315f726f7376:6f6a6f756b6f6e5f:10a171aa582999fd]. Should be
[7d8ff:0(NAME):136315f726f7376:6f6a6f756b6f6e5f:a9800daf3c0bd7bd].
FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [16]: entry has wrong offset
[7d8ff:0(NAME):136335f41737472:69645f7469656e61:6a200ab82eeb86b5]. Should be
[7d8ff:0(NAME):136335f41737472:69645f7469656e61:b84c800b0213e2f5].
FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [17]: entry has wrong offset
[7d8ff:0(NAME):136345f41737472:69645f6d79796de4:64e2323fe411e0]. Should be
[7d8ff:0(NAME):136345f41737472:69645f6d79796de4:d7766c3b7e1b2cd0].
FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [25]: entry has wrong offset
[7d8ff:0(NAME):138325f6e79745f:5069726a6f6e5f68:64bc351919bfc2b]. Should be
[7d8ff:0(NAME):138325f6e79745f:5069726a6f6e5f68:9b6fa2f69d3a3b5b].
FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [26]: entry has wrong offset
[7d8ff:0(NAME):138335f74616e73:73696e5f7079f672:be4c8ad1d6bf024]. Should be
[7d8ff:0(NAME):138335f74616e73:73696e5f7079f672:be09da7adf42944].
FSCK: Directory [7da90:6ce4e46b000000:7daa0] (dir40), node [4318266], item [1], unit [2]: entry has wrong offset
[7daa0:0(NAME):132303032313232:302d796c6569736c:5ea48bc52d18]. Should be [7daa0:0(NAME):132303032313232:302d796c6569736c:fffff4bfe92140a8].
FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319242], item [0], unit [34]: entry has wrong offset
[7dc25:0(NAME):130365f62657374:6d616e5f6c756b65:226514768dc110cd]. Should be
[7dc25:0(NAME):130365f62657374:6d616e5f6c756b65:2265147666480f1d].
FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319242], item [0], unit [41]: entry has wrong offset
[7dc25:0(NAME):132365f68e4e470:6172695f6d616c6a:92d8f19d65d95be]. Should be
[7dc25:0(NAME):132365f68e4e470:6172695f6d616c6a:92d2e1933fbf67e].
FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319242], item [0], unit [44]: entry has wrong offset
[7dc25:0(NAME):133305f53757669:5f6c61756c61615f:bd25b6a72855fe86]. Should be
[7dc25:0(NAME):133305f53757669:5f6c61756c61615f:bd2555a4d3c14cb6].
FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319242], item [0], unit [48]: entry has wrong offset
[7dc25:0(NAME):133365f41737472:69645f6ae46e6e69:16db1dfa6f08ba]. Should be [7dc25:0(NAME):133365f41737472:69645f6ae46e6e69:16db1dd2f6070a].
FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319242], item [0], unit [49]: entry has wrong offset
[7dc25:0(NAME):133375f69686d65:656c6c6973656e5f:9b778ff47749f37e]. Should be
[7dc25:0(NAME):133375f69686d65:656c6c6973656e5f:d80e781b2fea179e].
FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319242], item [0], unit [52]: entry has wrong offset
[7dc25:0(NAME):134305f796c6ce4:7479736d756e6961:40640ac5d13ba022]. Should be
[7dc25:0(NAME):134305f796c6ce4:7479736d756e6961:4063a8f81c2f3c82].
FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319242], item [0], unit [53]: entry has wrong offset
[7dc25:0(NAME):134315f796c6ce4:74796b73657373e4:1bd83c4b92407]. Should be [7dc25:0(NAME):134315f796c6ce4:74796b73657373e4:1b4b2452fa157].
FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319242], item [0], unit [54]: entry has wrong offset
[7dc25:0(NAME):134325f41737472:69645f6a616b6161:d15a16be63d261bd]. Should be
[7dc25:0(NAME):134325f41737472:69645f6a616b6161:a86ba0c7a2097cad].
FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319242], item [0], unit [55]: entry has wrong offset
[7dc25:0(NAME):134335f41737472:69645f6a616b6161:f394bffd7800956b]. Should be
[7dc25:0(NAME):134335f41737472:69645f6a616b6161:9adefe5be00c50db].
FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319242], item [0], unit [58]: entry has wrong offset
[7dc25:0(NAME):134375f52697374:6f5f7475746b6969:f9c07c6a924c893]. Should be
[7dc25:0(NAME):134375f52697374:6f5f7475746b6969:da3b247a1b994e3].
FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319242], item [0], unit [60]: entry has wrong offset
[7dc25:0(NAME):134395f796c6569:736b7576615f68e4:3eb28bdf41f7c]. Should be [7dc25:0(NAME):134395f796c6569:736b7576615f68e4:ffffb751cef2d5ec].
FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319243], item [0], unit [0]: entry has wrong offset
[7dc25:0(NAME):135305f796c6569:736b7576615f68e4:1da264211f344b2]. Should be
[7dc25:0(NAME):135305f796c6569:736b7576615f68e4:ffdda5ab1a577fa2].
FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319243], item [0], unit [2]: entry has wrong offset
[7dc25:0(NAME):135335f43796265:72746f702d6d6965:b20dc6112b27f52]. Should be
[7dc25:0(NAME):135335f43796265:72746f702d6d6965:ccfc58ed8054c342].
FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319243], item [0], unit [4]: entry has wrong offset
[7dc25:0(NAME):135355f4b696d6d:6f5f6a6f6e676cf6:74232d69e18ad511]. Should be
[7dc25:0(NAME):135355f4b696d6d:6f5f6a6f6e676cf6:6de148b3d7414451].
FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319243], item [0], unit [5]: entry has wrong offset
[7dc25:0(NAME):135365f746f696e:656e5f6c61686a61:4aa9262d28f]. Should be [7dc25:0(NAME):135365f746f696e:656e5f6c61686a61:3dd30c60acf].
FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319243], item [0], unit [9]: entry has wrong offset
[7dc25:0(NAME):136305f73756c68:6173656e5f7279f6:920d173e51c09120]. Should be
[7dc25:0(NAME):136305f73756c68:6173656e5f7279f6:123bb47cc8f6ecb0].
FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319243], item [0], unit [10]: entry has wrong offset
[7dc25:0(NAME):136315f726f7376:6f6a6f756b6f6e5f:10a171aa582999fd]. Should be
[7dc25:0(NAME):136315f726f7376:6f6a6f756b6f6e5f:a9800daf3c0bd7bd].
FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319243], item [0], unit [12]: entry has wrong offset
[7dc25:0(NAME):136335f41737472:69645f7469656e61:6a200ab82eeb86b5]. Should be
[7dc25:0(NAME):136335f41737472:69645f7469656e61:b84c800b0213e2f5].
FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319243], item [0], unit [13]: entry has wrong offset
[7dc25:0(NAME):136345f41737472:69645f6d79796de4:64e2323fe411e0]. Should be
[7dc25:0(NAME):136345f41737472:69645f6d79796de4:d7766c3b7e1b2cd0].
FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319243], item [0], unit [21]: entry has wrong offset
[7dc25:0(NAME):138325f6e79745f:5069726a6f6e5f68:64bc351919bfc2b]. Should be
[7dc25:0(NAME):138325f6e79745f:5069726a6f6e5f68:9b6fa2f69d3a3b5b].
FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319243], item [0], unit [22]: entry has wrong offset
[7dc25:0(NAME):138335f74616e73:73696e5f7079f672:be4c8ad1d6bf024]. Should be
[7dc25:0(NAME):138335f74616e73:73696e5f7079f672:be09da7adf42944].
FSCK: Directory [7ddec:6ce4e46b000000:7ddfd] (dir40), node [4319483], item [0], unit [2]: entry has wrong offset
[7ddfd:0(NAME):132303032313232:302d796c6569736c:5ea48bc52d18]. Should be [7ddfd:0(NAME):132303032313232:302d796c6569736c:fffff4bfe92140a8].
FSCK: Directory [7f92e:526563656e7444:7f944] (dir40), node [7188029], item [11], unit [4]: entry has wrong offset
[7f944:0(NAME):14d696e756c6c61:206f6e20797374e4:bc7f7f4bc705cca]. Should be
[7f944:0(NAME):14d696e756c6c61:206f6e20797374e4:9cfa275b505291a].
FSCK: Directory [7f92e:526563656e7444:7f944] (dir40), node [7188029], item [11], unit [12]: entry has wrong offset
[7f944:0(NAME):154756c656e204a:6565737573206c75:95832fa214e08a05]. Should be
[7f944:0(NAME):154756c656e204a:6565737573206c75:ceb11f7d288b9d5].
FSCK: Directory [7fa6a:61000000000000:7fbe8] (dir40), node [7191155], item [0], unit [12]: entry has wrong offset
[7fbe8:0(NAME):17777772e616d69:63612e66695f416d:8051b6899d4702e7]. Should be
[7fbe8:0(NAME):17777772e616d69:63612e66695f416d:7a0fd1d3ba7673d7].
FSCK: Directory [699e3:62696c00000000:8105d] (dir40), node [7256456], item [1], unit [31]: entry has wrong offset
[8105d:0(NAME):c770656c695f746f:696d69695f696c6d:28df05cd90c6]. Should be [8105d:0(NAME):c770656c695f746f:696d69695f696c6d:28df057a0d96].
FSCK: Directory [699e3:6d757300000000:81549] (dir40), node [7443626], item [0], unit [7]: entry has wrong offset
[81549:0(NAME):14d61726b6f204c:696e64726f6f7320:e9d3007d6f1fe370]. Should be
[81549:0(NAME):14d61726b6f204c:696e64726f6f7320:fb729772ed747540].
FSCK: Directory [699e3:7363616e000000:7f794] (dir40), node [6994496], item [1], unit [32]: entry has wrong offset
[7f794:0(NAME):170616c76656c75:6b7365656e617374:e9cfcc19483f769a]. Should be
[7f794:0(NAME):170616c76656c75:6b7365656e617374:e595dd5f5d0656ca].
FSCK: Directory [793e6:73616b73610000:79d95] (dir40), node [4068633], item [1], unit [13]: entry has wrong offset
[79d95:0(NAME):14175665f64656d:5f5765675f7a755f:fe396dc2d9a86340]. Should be
[79d95:0(NAME):14175665f64656d:5f5765675f7a755f:3f712c128f979300].
FSCK: Directory [793e6:73616b73610000:79d95] (dir40), node [4068633], item [1], unit [15]: entry has wrong offset
[79d95:0(NAME):147657472696562:655f696e5f496e73:9759d81a5a3f407]. Should be
[79d95:0(NAME):147657472696562:655f696e5f496e73:9759d6d4b3f1547].
FSCK: Directory [7ec5d:45786974000000:7edf2] (dir40), node [4729297], item [0], unit [14]: entry has wrong offset
[7edf2:0(NAME):145786974202d20:5669696d65696e65:146826bcf51840]. Should be [7edf2:0(NAME):145786974202d20:5669696d65696e65:145f538b388300].
FSCK: Directory [7ec5d:6f676700000000:7ed07] (dir40), node [4494618], item [2], unit [11]: entry has wrong offset
[7ed07:0(NAME):1457474e45f6865:5f6b61696b6b695f:efca38f3f0afcc]. Should be [7ed07:0(NAME):1457474e45f6865:5f6b61696b6b695f:efca38f3efff1c].
FSCK: Directory [7eca2:46696e6c616e64:7eca9] (dir40), node [4416947], item [5], unit [31]: entry has wrong offset
[7eca9:0(NAME):154e4e46c6ce45f:506f686a616e5f54:142d1c7c01f117cf]. Should be
[7eca9:0(NAME):154e4e46c6ce45f:506f686a616e5f54:fe817006b055df3f].
FSCK: Directory [7eca2:50657472695f4c:7ecc9] (dir40), node [4447434], item [0], unit [10]: entry has wrong offset
[7ecc9:0(NAME):14b61696b6b695f:6f646f7475735f6a:6775041f08f4fd8f]. Should be
[7ecc9:0(NAME):14b61696b6b695f:6f646f7475735f6a:6774a31e8e0c5fff].
FSCK: Directory [7eca2:50657472695f4c:7ecc9] (dir40), node [4447434], item [0], unit [12]: entry has wrong offset
[7ecc9:0(NAME):14e6f7374616e5f:6b61747365656e5f:e5990e04b555d6]. Should be [7ecc9:0(NAME):14e6f7374616e5f:6b61747365656e5f:e598fb5c8389a6].
FSCK: Directory [7eca2:506f686a616e5f:7ece4] (dir40), node [4486474], item [0], unit [19]: entry has wrong offset
[7ece4:0(NAME):14d696c6c6f696e:5f506f686f6c616e:638c310b1f019ea9]. Should be
[7ece4:0(NAME):14d696c6c6f696e:5f506f686f6c616e:61937a8b9cadcd69].
FSCK: Directory [7ec5d:168616e64656c2d:7eddc] (dir40), node [4710749], item [0], unit [7]: entry has wrong offset
[7eddc:0(NAME):142616368202d20:496368206c696562:983d3c1400f94d73]. Should be
[7eddc:0(NAME):142616368202d20:496368206c696562:d5fe2a670525a993].
FSCK: Directory [7ec5d:168616e64656c2d:7eddc] (dir40), node [4710749], item [0], unit [8]: entry has wrong offset
[7eddc:0(NAME):142616368202d20:4963682073746568:8735774f54413df8]. Should be
[7eddc:0(NAME):142616368202d20:4963682073746568:7189cada02a60568].
FSCK: Directory [7ef25:6ce4e46b000000:7ef39] (dir40), node [4766650], item [2], unit [2]: entry has wrong offset
[7ef39:0(NAME):132303032313232:302d796c6569736c:5ea48bc52d18]. Should be [7ef39:0(NAME):132303032313232:302d796c6569736c:fffff4bfe92140a8].
FSCK: Directory [8221a:7575732d6f6767:82270] (dir40), node [7690347], item [1], unit [21]: entry has wrong offset
[82270:0(NAME):154756c656e204a:6565737573206c75:b3b9cc5f603a3ef0]. Should be
[82270:0(NAME):154756c656e204a:6565737573206c75:c5596354de8ed0c0].
FSCK: Directory [6815d:76656e616a6100:681b8] (dir40), node [3079481], item [0], unit [29]: entry has wrong offset
[681b8:0(NAME):154756c656e204a:6565737573206c75:b3b9cc5f603a3ef0]. Should be
[681b8:0(NAME):154756c656e204a:6565737573206c75:c5596354de8ed0c0].
        Found 519392 objects.
        Time interval: Fri Nov 19 10:17:11 2004 - Fri Nov 19 10:21:12 2004
***** fsck.reiser4 finished at Fri Nov 19 10:21:12 2004
Closing fs...done

19 fatal corruptions were detected in FileSystem. Run with --build-fs option to fix them.
------------------------------------------------------------

Re: reiser4 crash

[Vladimir Saveliev]

Hello

On Fri, 2004-11-19 at 11:47, Sami Liedes wrote:
> Attached are the oops and fsck.reiser4 output.
> 
> This happened after using reiser4 for only 1,5 days.
> 

Which kernel do you use?

> 	Sami
> 
> 
> --- oops ---------------------------------------------------
> kernel BUG at fs/reiser4/plugin/file/tail_conversion.c:32!
> invalid operand: 0000 [#1]
> PREEMPT
> Modules linked in: ide_cd cdrom ipt_MASQUERADE ipt_REJECT ipt_state iptable_filter i2c_viapro ehci_hcd uhci_hcd usbcore via_agp evdev dm_mod i2c_isa i2c_core snd_via82xx snd_ac97_codec snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore radeon agpgart 8139too mii crc32 ip_nat_irc ip_nat_ftp iptable_nat ip_tables ip_conntrack_irc ip_conntrack_ftp ip_conntrack 3c59x lp parport af_packet
> CPU:    0
> EIP:    0060:[<c01c92f2>]    Not tainted VLI
> EFLAGS: 00210286   (2.6.10-rc1)
> EIP is at get_exclusive_access+0x32/0x40
> eax: ce4dfc60   ebx: c5a64a84   ecx: c5a64a78   edx: 00000000
> esi: 00000000   edi: c5a64a78   ebp: d9b97dec   esp: d9b97dec
> ds: 007b   es: 007b   ss: 0068
> Process aptitude (pid: 7704, threadinfo=d9b96000 task=c4bf6a00)
> Stack: d9b97ed8 c01c855c 00000001 d9b97e44 d9b97dfc d9b97dfc d9b97e00 dea45ba0
>        00000014 d9b96000 00000aa9 d9b96000 d9b96000 00000001 00000001 008a1470
>        00000000 00000000 00000008 c5a64ad0 b6f19000 ddc5fba0 00008000 008a1470
> Call Trace:
>  [<c0104e7a>] show_stack+0x7a/0x90
>  [<c0104ffd>] show_registers+0x14d/0x1b0
>  [<c01051e4>] die+0xe4/0x170
>  [<c0105674>] do_invalid_op+0xe4/0xf0
>  [<c0104ab9>] error_code+0x2d/0x38
>  [<c01c855c>] write_unix_file+0x1fc/0x4c0
>  [<c01a0bbd>] reiser4_write+0x6d/0xb0
>  [<c014c59f>] vfs_write+0xbf/0x110
>  [<c014c6a1>] sys_write+0x41/0x70
>  [<c01040af>] syscall_call+0x7/0xb
> Code: ff 21 e0 89 e5 8b 00 8b 80 b8 04 00 00 8b 40 3c 8b 40 08 85 c0 75 14 ba 01 00 ff ff 89 c8 0f c1 10 85 d2 0f 85 ce 0f 00 00 c9 c3 <0f> 0b 20 00 40 90 2b c0 eb e2 8d 74 26 00 55 89 e5 ba ff ff 00
> ------------------------------------------------------------
> 
> --- fsck.reiser4 -------------------------------------------
> # fsck.reiser4 /dev/hdd3
> *******************************************************************
> This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
> *******************************************************************
> 
> Fscking the /dev/hdd3 block device.
> Will check the consistency of the Reiser4 SuperBlock.
> Will check the consistency of the Reiser4 FileSystem.
> Continue?
> (Yes/No): y
> ***** fsck.reiser4 started at Fri Nov 19 10:13:55 2004
> Reiser4 journal (journal40) on /dev/hdd3: 0 transactions replayed of the total 0 blocks.
> Reiser4 fs was detected on /dev/hdd3.
> Master super block (16):
> magic:          ReIsEr4
> blksize:        4096
> format:         0x0 (format40)
> uuid:           bff15455-f079-4543-abff-da68ef05fcbe
> label:          <none>
> 
> Format super block (17):
> plugin:         format40
> description:    Disk-format for reiser4, ver. 1.0.0
> magic:          ReIsEr40FoRmAt
> flushes:        0
> mkfs id:        0x4a43a302
> blocks:         49596671
> free blocks:    34064528
> root block:     15337898
> tail policy:    0x2 (smart)
> next oid:       0x98aa0
> file count:     518379
> tree height:    4
> key policy:     LARGE
> 
> 
> CHECKING STORAGE TREE
>         Read nodes 357991
>         Nodes left in the tree 357991
>                 Leaves of them 352551, Twigs of them 5356
>         Time interval: Fri Nov 19 10:14:09 2004 - Fri Nov 19 10:16:42 2004
> CHECKING EXTENT REGIONS.
>         Read twigs 5356
>         Time interval: Fri Nov 19 10:16:42 2004 - Fri Nov 19 10:17:11 2004
> CHECKING SEMANTIC TREE
> FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316682], item [1], unit [37]: entry has wrong offset
> [7d8ff:0(NAME):130365f62657374:6d616e5f6c756b65:226514768dc110cd]. Should be
> [7d8ff:0(NAME):130365f62657374:6d616e5f6c756b65:2265147666480f1d].
> FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316682], item [1], unit [44]: entry has wrong offset
> [7d8ff:0(NAME):132365f68e4e470:6172695f6d616c6a:92d8f19d65d95be]. Should be
> [7d8ff:0(NAME):132365f68e4e470:6172695f6d616c6a:92d2e1933fbf67e].
> FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316682], item [1], unit [47]: entry has wrong offset
> [7d8ff:0(NAME):133305f53757669:5f6c61756c61615f:bd25b6a72855fe86]. Should be
> [7d8ff:0(NAME):133305f53757669:5f6c61756c61615f:bd2555a4d3c14cb6].
> FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316682], item [1], unit [51]: entry has wrong offset
> [7d8ff:0(NAME):133365f41737472:69645f6ae46e6e69:16db1dfa6f08ba]. Should be [7d8ff:0(NAME):133365f41737472:69645f6ae46e6e69:16db1dd2f6070a].
> FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316682], item [1], unit [52]: entry has wrong offset
> [7d8ff:0(NAME):133375f69686d65:656c6c6973656e5f:9b778ff47749f37e]. Should be
> [7d8ff:0(NAME):133375f69686d65:656c6c6973656e5f:d80e781b2fea179e].
> FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316682], item [1], unit [55]: entry has wrong offset
> [7d8ff:0(NAME):134305f796c6ce4:7479736d756e6961:40640ac5d13ba022]. Should be
> [7d8ff:0(NAME):134305f796c6ce4:7479736d756e6961:4063a8f81c2f3c82].
> FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316682], item [1], unit [56]: entry has wrong offset
> [7d8ff:0(NAME):134315f796c6ce4:74796b73657373e4:1bd83c4b92407]. Should be [7d8ff:0(NAME):134315f796c6ce4:74796b73657373e4:1b4b2452fa157].
> FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316682], item [1], unit [57]: entry has wrong offset
> [7d8ff:0(NAME):134325f41737472:69645f6a616b6161:d15a16be63d261bd]. Should be
> [7d8ff:0(NAME):134325f41737472:69645f6a616b6161:a86ba0c7a2097cad].
> FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316682], item [1], unit [58]: entry has wrong offset
> [7d8ff:0(NAME):134335f41737472:69645f6a616b6161:f394bffd7800956b]. Should be
> [7d8ff:0(NAME):134335f41737472:69645f6a616b6161:9adefe5be00c50db].
> FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [1]: entry has wrong offset
> [7d8ff:0(NAME):134375f52697374:6f5f7475746b6969:f9c07c6a924c893]. Should be
> [7d8ff:0(NAME):134375f52697374:6f5f7475746b6969:da3b247a1b994e3].
> FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [3]: entry has wrong offset
> [7d8ff:0(NAME):134395f796c6569:736b7576615f68e4:3eb28bdf41f7c]. Should be [7d8ff:0(NAME):134395f796c6569:736b7576615f68e4:ffffb751cef2d5ec].
> FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [4]: entry has wrong offset
> [7d8ff:0(NAME):135305f796c6569:736b7576615f68e4:1da264211f344b2]. Should be
> [7d8ff:0(NAME):135305f796c6569:736b7576615f68e4:ffdda5ab1a577fa2].
> FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [6]: entry has wrong offset
> [7d8ff:0(NAME):135335f43796265:72746f702d6d6965:b20dc6112b27f52]. Should be
> [7d8ff:0(NAME):135335f43796265:72746f702d6d6965:ccfc58ed8054c342].
> FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [8]: entry has wrong offset
> [7d8ff:0(NAME):135355f4b696d6d:6f5f6a6f6e676cf6:74232d69e18ad511]. Should be
> [7d8ff:0(NAME):135355f4b696d6d:6f5f6a6f6e676cf6:6de148b3d7414451].
> FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [9]: entry has wrong offset
> [7d8ff:0(NAME):135365f746f696e:656e5f6c61686a61:4aa9262d28f]. Should be [7d8ff:0(NAME):135365f746f696e:656e5f6c61686a61:3dd30c60acf].
> FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [13]: entry has wrong offset
> [7d8ff:0(NAME):136305f73756c68:6173656e5f7279f6:920d173e51c09120]. Should be
> [7d8ff:0(NAME):136305f73756c68:6173656e5f7279f6:123bb47cc8f6ecb0].
> FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [14]: entry has wrong offset
> [7d8ff:0(NAME):136315f726f7376:6f6a6f756b6f6e5f:10a171aa582999fd]. Should be
> [7d8ff:0(NAME):136315f726f7376:6f6a6f756b6f6e5f:a9800daf3c0bd7bd].
> FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [16]: entry has wrong offset
> [7d8ff:0(NAME):136335f41737472:69645f7469656e61:6a200ab82eeb86b5]. Should be
> [7d8ff:0(NAME):136335f41737472:69645f7469656e61:b84c800b0213e2f5].
> FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [17]: entry has wrong offset
> [7d8ff:0(NAME):136345f41737472:69645f6d79796de4:64e2323fe411e0]. Should be
> [7d8ff:0(NAME):136345f41737472:69645f6d79796de4:d7766c3b7e1b2cd0].
> FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [25]: entry has wrong offset
> [7d8ff:0(NAME):138325f6e79745f:5069726a6f6e5f68:64bc351919bfc2b]. Should be
> [7d8ff:0(NAME):138325f6e79745f:5069726a6f6e5f68:9b6fa2f69d3a3b5b].
> FSCK: Directory [7d8e0:6173747269645f:7d8ff] (dir40), node [4316683], item [0], unit [26]: entry has wrong offset
> [7d8ff:0(NAME):138335f74616e73:73696e5f7079f672:be4c8ad1d6bf024]. Should be
> [7d8ff:0(NAME):138335f74616e73:73696e5f7079f672:be09da7adf42944].
> FSCK: Directory [7da90:6ce4e46b000000:7daa0] (dir40), node [4318266], item [1], unit [2]: entry has wrong offset
> [7daa0:0(NAME):132303032313232:302d796c6569736c:5ea48bc52d18]. Should be [7daa0:0(NAME):132303032313232:302d796c6569736c:fffff4bfe92140a8].
> FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319242], item [0], unit [34]: entry has wrong offset
> [7dc25:0(NAME):130365f62657374:6d616e5f6c756b65:226514768dc110cd]. Should be
> [7dc25:0(NAME):130365f62657374:6d616e5f6c756b65:2265147666480f1d].
> FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319242], item [0], unit [41]: entry has wrong offset
> [7dc25:0(NAME):132365f68e4e470:6172695f6d616c6a:92d8f19d65d95be]. Should be
> [7dc25:0(NAME):132365f68e4e470:6172695f6d616c6a:92d2e1933fbf67e].
> FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319242], item [0], unit [44]: entry has wrong offset
> [7dc25:0(NAME):133305f53757669:5f6c61756c61615f:bd25b6a72855fe86]. Should be
> [7dc25:0(NAME):133305f53757669:5f6c61756c61615f:bd2555a4d3c14cb6].
> FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319242], item [0], unit [48]: entry has wrong offset
> [7dc25:0(NAME):133365f41737472:69645f6ae46e6e69:16db1dfa6f08ba]. Should be [7dc25:0(NAME):133365f41737472:69645f6ae46e6e69:16db1dd2f6070a].
> FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319242], item [0], unit [49]: entry has wrong offset
> [7dc25:0(NAME):133375f69686d65:656c6c6973656e5f:9b778ff47749f37e]. Should be
> [7dc25:0(NAME):133375f69686d65:656c6c6973656e5f:d80e781b2fea179e].
> FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319242], item [0], unit [52]: entry has wrong offset
> [7dc25:0(NAME):134305f796c6ce4:7479736d756e6961:40640ac5d13ba022]. Should be
> [7dc25:0(NAME):134305f796c6ce4:7479736d756e6961:4063a8f81c2f3c82].
> FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319242], item [0], unit [53]: entry has wrong offset
> [7dc25:0(NAME):134315f796c6ce4:74796b73657373e4:1bd83c4b92407]. Should be [7dc25:0(NAME):134315f796c6ce4:74796b73657373e4:1b4b2452fa157].
> FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319242], item [0], unit [54]: entry has wrong offset
> [7dc25:0(NAME):134325f41737472:69645f6a616b6161:d15a16be63d261bd]. Should be
> [7dc25:0(NAME):134325f41737472:69645f6a616b6161:a86ba0c7a2097cad].
> FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319242], item [0], unit [55]: entry has wrong offset
> [7dc25:0(NAME):134335f41737472:69645f6a616b6161:f394bffd7800956b]. Should be
> [7dc25:0(NAME):134335f41737472:69645f6a616b6161:9adefe5be00c50db].
> FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319242], item [0], unit [58]: entry has wrong offset
> [7dc25:0(NAME):134375f52697374:6f5f7475746b6969:f9c07c6a924c893]. Should be
> [7dc25:0(NAME):134375f52697374:6f5f7475746b6969:da3b247a1b994e3].
> FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319242], item [0], unit [60]: entry has wrong offset
> [7dc25:0(NAME):134395f796c6569:736b7576615f68e4:3eb28bdf41f7c]. Should be [7dc25:0(NAME):134395f796c6569:736b7576615f68e4:ffffb751cef2d5ec].
> FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319243], item [0], unit [0]: entry has wrong offset
> [7dc25:0(NAME):135305f796c6569:736b7576615f68e4:1da264211f344b2]. Should be
> [7dc25:0(NAME):135305f796c6569:736b7576615f68e4:ffdda5ab1a577fa2].
> FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319243], item [0], unit [2]: entry has wrong offset
> [7dc25:0(NAME):135335f43796265:72746f702d6d6965:b20dc6112b27f52]. Should be
> [7dc25:0(NAME):135335f43796265:72746f702d6d6965:ccfc58ed8054c342].
> FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319243], item [0], unit [4]: entry has wrong offset
> [7dc25:0(NAME):135355f4b696d6d:6f5f6a6f6e676cf6:74232d69e18ad511]. Should be
> [7dc25:0(NAME):135355f4b696d6d:6f5f6a6f6e676cf6:6de148b3d7414451].
> FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319243], item [0], unit [5]: entry has wrong offset
> [7dc25:0(NAME):135365f746f696e:656e5f6c61686a61:4aa9262d28f]. Should be [7dc25:0(NAME):135365f746f696e:656e5f6c61686a61:3dd30c60acf].
> FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319243], item [0], unit [9]: entry has wrong offset
> [7dc25:0(NAME):136305f73756c68:6173656e5f7279f6:920d173e51c09120]. Should be
> [7dc25:0(NAME):136305f73756c68:6173656e5f7279f6:123bb47cc8f6ecb0].
> FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319243], item [0], unit [10]: entry has wrong offset
> [7dc25:0(NAME):136315f726f7376:6f6a6f756b6f6e5f:10a171aa582999fd]. Should be
> [7dc25:0(NAME):136315f726f7376:6f6a6f756b6f6e5f:a9800daf3c0bd7bd].
> FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319243], item [0], unit [12]: entry has wrong offset
> [7dc25:0(NAME):136335f41737472:69645f7469656e61:6a200ab82eeb86b5]. Should be
> [7dc25:0(NAME):136335f41737472:69645f7469656e61:b84c800b0213e2f5].
> FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319243], item [0], unit [13]: entry has wrong offset
> [7dc25:0(NAME):136345f41737472:69645f6d79796de4:64e2323fe411e0]. Should be
> [7dc25:0(NAME):136345f41737472:69645f6d79796de4:d7766c3b7e1b2cd0].
> FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319243], item [0], unit [21]: entry has wrong offset
> [7dc25:0(NAME):138325f6e79745f:5069726a6f6e5f68:64bc351919bfc2b]. Should be
> [7dc25:0(NAME):138325f6e79745f:5069726a6f6e5f68:9b6fa2f69d3a3b5b].
> FSCK: Directory [7dbf9:6173747269645f:7dc25] (dir40), node [4319243], item [0], unit [22]: entry has wrong offset
> [7dc25:0(NAME):138335f74616e73:73696e5f7079f672:be4c8ad1d6bf024]. Should be
> [7dc25:0(NAME):138335f74616e73:73696e5f7079f672:be09da7adf42944].
> FSCK: Directory [7ddec:6ce4e46b000000:7ddfd] (dir40), node [4319483], item [0], unit [2]: entry has wrong offset
> [7ddfd:0(NAME):132303032313232:302d796c6569736c:5ea48bc52d18]. Should be [7ddfd:0(NAME):132303032313232:302d796c6569736c:fffff4bfe92140a8].
> FSCK: Directory [7f92e:526563656e7444:7f944] (dir40), node [7188029], item [11], unit [4]: entry has wrong offset
> [7f944:0(NAME):14d696e756c6c61:206f6e20797374e4:bc7f7f4bc705cca]. Should be
> [7f944:0(NAME):14d696e756c6c61:206f6e20797374e4:9cfa275b505291a].
> FSCK: Directory [7f92e:526563656e7444:7f944] (dir40), node [7188029], item [11], unit [12]: entry has wrong offset
> [7f944:0(NAME):154756c656e204a:6565737573206c75:95832fa214e08a05]. Should be
> [7f944:0(NAME):154756c656e204a:6565737573206c75:ceb11f7d288b9d5].
> FSCK: Directory [7fa6a:61000000000000:7fbe8] (dir40), node [7191155], item [0], unit [12]: entry has wrong offset
> [7fbe8:0(NAME):17777772e616d69:63612e66695f416d:8051b6899d4702e7]. Should be
> [7fbe8:0(NAME):17777772e616d69:63612e66695f416d:7a0fd1d3ba7673d7].
> FSCK: Directory [699e3:62696c00000000:8105d] (dir40), node [7256456], item [1], unit [31]: entry has wrong offset
> [8105d:0(NAME):c770656c695f746f:696d69695f696c6d:28df05cd90c6]. Should be [8105d:0(NAME):c770656c695f746f:696d69695f696c6d:28df057a0d96].
> FSCK: Directory [699e3:6d757300000000:81549] (dir40), node [7443626], item [0], unit [7]: entry has wrong offset
> [81549:0(NAME):14d61726b6f204c:696e64726f6f7320:e9d3007d6f1fe370]. Should be
> [81549:0(NAME):14d61726b6f204c:696e64726f6f7320:fb729772ed747540].
> FSCK: Directory [699e3:7363616e000000:7f794] (dir40), node [6994496], item [1], unit [32]: entry has wrong offset
> [7f794:0(NAME):170616c76656c75:6b7365656e617374:e9cfcc19483f769a]. Should be
> [7f794:0(NAME):170616c76656c75:6b7365656e617374:e595dd5f5d0656ca].
> FSCK: Directory [793e6:73616b73610000:79d95] (dir40), node [4068633], item [1], unit [13]: entry has wrong offset
> [79d95:0(NAME):14175665f64656d:5f5765675f7a755f:fe396dc2d9a86340]. Should be
> [79d95:0(NAME):14175665f64656d:5f5765675f7a755f:3f712c128f979300].
> FSCK: Directory [793e6:73616b73610000:79d95] (dir40), node [4068633], item [1], unit [15]: entry has wrong offset
> [79d95:0(NAME):147657472696562:655f696e5f496e73:9759d81a5a3f407]. Should be
> [79d95:0(NAME):147657472696562:655f696e5f496e73:9759d6d4b3f1547].
> FSCK: Directory [7ec5d:45786974000000:7edf2] (dir40), node [4729297], item [0], unit [14]: entry has wrong offset
> [7edf2:0(NAME):145786974202d20:5669696d65696e65:146826bcf51840]. Should be [7edf2:0(NAME):145786974202d20:5669696d65696e65:145f538b388300].
> FSCK: Directory [7ec5d:6f676700000000:7ed07] (dir40), node [4494618], item [2], unit [11]: entry has wrong offset
> [7ed07:0(NAME):1457474e45f6865:5f6b61696b6b695f:efca38f3f0afcc]. Should be [7ed07:0(NAME):1457474e45f6865:5f6b61696b6b695f:efca38f3efff1c].
> FSCK: Directory [7eca2:46696e6c616e64:7eca9] (dir40), node [4416947], item [5], unit [31]: entry has wrong offset
> [7eca9:0(NAME):154e4e46c6ce45f:506f686a616e5f54:142d1c7c01f117cf]. Should be
> [7eca9:0(NAME):154e4e46c6ce45f:506f686a616e5f54:fe817006b055df3f].
> FSCK: Directory [7eca2:50657472695f4c:7ecc9] (dir40), node [4447434], item [0], unit [10]: entry has wrong offset
> [7ecc9:0(NAME):14b61696b6b695f:6f646f7475735f6a:6775041f08f4fd8f]. Should be
> [7ecc9:0(NAME):14b61696b6b695f:6f646f7475735f6a:6774a31e8e0c5fff].
> FSCK: Directory [7eca2:50657472695f4c:7ecc9] (dir40), node [4447434], item [0], unit [12]: entry has wrong offset
> [7ecc9:0(NAME):14e6f7374616e5f:6b61747365656e5f:e5990e04b555d6]. Should be [7ecc9:0(NAME):14e6f7374616e5f:6b61747365656e5f:e598fb5c8389a6].
> FSCK: Directory [7eca2:506f686a616e5f:7ece4] (dir40), node [4486474], item [0], unit [19]: entry has wrong offset
> [7ece4:0(NAME):14d696c6c6f696e:5f506f686f6c616e:638c310b1f019ea9]. Should be
> [7ece4:0(NAME):14d696c6c6f696e:5f506f686f6c616e:61937a8b9cadcd69].
> FSCK: Directory [7ec5d:168616e64656c2d:7eddc] (dir40), node [4710749], item [0], unit [7]: entry has wrong offset
> [7eddc:0(NAME):142616368202d20:496368206c696562:983d3c1400f94d73]. Should be
> [7eddc:0(NAME):142616368202d20:496368206c696562:d5fe2a670525a993].
> FSCK: Directory [7ec5d:168616e64656c2d:7eddc] (dir40), node [4710749], item [0], unit [8]: entry has wrong offset
> [7eddc:0(NAME):142616368202d20:4963682073746568:8735774f54413df8]. Should be
> [7eddc:0(NAME):142616368202d20:4963682073746568:7189cada02a60568].
> FSCK: Directory [7ef25:6ce4e46b000000:7ef39] (dir40), node [4766650], item [2], unit [2]: entry has wrong offset
> [7ef39:0(NAME):132303032313232:302d796c6569736c:5ea48bc52d18]. Should be [7ef39:0(NAME):132303032313232:302d796c6569736c:fffff4bfe92140a8].
> FSCK: Directory [8221a:7575732d6f6767:82270] (dir40), node [7690347], item [1], unit [21]: entry has wrong offset
> [82270:0(NAME):154756c656e204a:6565737573206c75:b3b9cc5f603a3ef0]. Should be
> [82270:0(NAME):154756c656e204a:6565737573206c75:c5596354de8ed0c0].
> FSCK: Directory [6815d:76656e616a6100:681b8] (dir40), node [3079481], item [0], unit [29]: entry has wrong offset
> [681b8:0(NAME):154756c656e204a:6565737573206c75:b3b9cc5f603a3ef0]. Should be
> [681b8:0(NAME):154756c656e204a:6565737573206c75:c5596354de8ed0c0].
>         Found 519392 objects.
>         Time interval: Fri Nov 19 10:17:11 2004 - Fri Nov 19 10:21:12 2004
> ***** fsck.reiser4 finished at Fri Nov 19 10:21:12 2004
> Closing fs...done
> 
> 19 fatal corruptions were detected in FileSystem. Run with --build-fs option to fix them.
> ------------------------------------------------------------
> 

Re: reiser4 crash

[Sami Liedes]

On Thu, Nov 25, 2004 at 10:54:10AM +0300, Vladimir Saveliev wrote:

> On Fri, 2004-11-19 at 11:47, Sami Liedes wrote:
> > Attached are the oops and fsck.reiser4 output.
> > 
> > This happened after using reiser4 for only 1,5 days.
> > 
> 
> Which kernel do you use?

2.6.10-rc1.

	Sami

Re: reiser4 crash

[Cal]

----------
and then at Thu, 25 Nov 2004 10:54:10 +0300, it was written ...
  >
 >Which kernel do you use?
 >
 >> 	Sami
...
 >> kernel BUG at fs/reiser4/plugin/file/tail_conversion.c:32!
 >> invalid operand: 0000 [#1]
 >> PREEMPT
...
 >> EFLAGS: 00210286   (2.6.10-rc1)
 >> EIP is at get_exclusive_access+0x32/0x40

This occurs with 2.6.10-rc2-mm2, 2.6.10-rc2-mm3.  It's nastier than
you might think.  After the BUG, the system slowly sinks into fatal
decline, losing  screen i/o, keyboard response, eventually just
locking up completely.

cheers, Cal

Re: reiser4 crash

[mjt]

On Thu, Nov 25, 2004 at 10:19:19PM +1100, Cal wrote:
>This occurs with 2.6.10-rc2-mm2, 2.6.10-rc2-mm3.  It's nastier than
>you might think.  After the BUG, the system slowly sinks into fatal
>decline, losing  screen i/o, keyboard response, eventually just
>locking up completely.

Did you try vs's patches?

I don't remember if I mentioned it, but there were two patches
from Piotr Neuman's -cko that were required by Reiser4 (according
to him) but seemed to patch well onto vs's patched system...

Can anyone give any info on this?
Mr. Neuman for example :)

Anyway, my box has been running a-ok now with 2.6.9, vs's reiser4-for-2.6.9
and the additional bugfix, but I have been too busy at work to test real
much.

Would it be possible for you other guys to give it a shot; I'm sure
everyone would appreciate it :)

Thanks!

-- 
mjt

Re: reiser4 crash

[Cal]

----------
and then at Thu, 25 Nov 2004 13:23:43 +0200, it was written ...
 >Did you try vs's patches?

While I search for the link to said patches, can you point me to
them?

cheers, Cal

Re: reiser4 crash

[mjt]

On Thu, Nov 25, 2004 at 10:42:12PM +1100, Cal wrote:
>
>While I search for the link to said patches, can you point me to
>them?

ftp://ftp.namesys.com/pub/reiser4-for-2.6/2.6.9/
http://marc.theaimsgroup.com/?l=reiserfs&m=110121057720746&w=2

It is possible the posted patch is included in the second patch
at namesys.

I'd still like to know about the two -cko patches though, as I can't
remember which ones they were (I'm at the office) and if they
should be included and whatever....

-- 
mjt

Re: reiser4 crash

[Cal]

----------
and then at Thu, 25 Nov 2004 14:05:45 +0200, it was written ...
 >ftp://ftp.namesys.com/pub/reiser4-for-2.6/2.6.9/
 >http://marc.theaimsgroup.com/?l=reiserfs&m=110121057720746&w=2
 >
 >It is possible the posted patch is included in the second patch
 >at namesys.
 >
 >I'd still like to know about the two -cko patches though, as I can't
 >remember which ones they were (I'm at the office) and if they
 >should be included and whatever....
 >
Cool, thanks!  I found the mailing list one, and with that applied to
2.6.10-rc2-mm3, the first run of apt-get update completed
successfully.  That's good!

I've been looking after grandkids for a couple of days, so I missed
the recent 2.6.9 updates on ftp.namesys.com.  I'm more interested in
2.6.10-rcx+, but l'll maybe take a look at the 2.6.9 stuff.

I'm a little confused about the cko reference.  I'm happily running
2.6.9-cko3 ona seconfd system, but I've not seen any breakdown of
the cko series (ie, the two particular cko patches you're
referencing). 

cheers, and thanks
Cal

Re: reiser4 crash

[Vladimir Saveliev]

Hello

On Thu, 2004-11-25 at 15:35, Cal wrote:
> ----------
> and then at Thu, 25 Nov 2004 14:05:45 +0200, it was written ...
>  >ftp://ftp.namesys.com/pub/reiser4-for-2.6/2.6.9/

There was an update today. Please make sure you got patch number 2.

>  >http://marc.theaimsgroup.com/?l=reiserfs&m=110121057720746&w=2
>  >
>  >It is possible the posted patch is included in the second patch
>  >at namesys.
>  >
>  >I'd still like to know about the two -cko patches though, as I can't
>  >remember which ones they were (I'm at the office) and if they
>  >should be included and whatever....
>  >
> Cool, thanks!  I found the mailing list one, and with that applied to
> 2.6.10-rc2-mm3, the first run of apt-get update completed
> successfully.  That's good!
> 
> I've been looking after grandkids for a couple of days, so I missed
> the recent 2.6.9 updates on ftp.namesys.com.  I'm more interested in
> 2.6.10-rcx+, but l'll maybe take a look at the 2.6.9 stuff.
> 
> I'm a little confused about the cko reference.  I'm happily running
> 2.6.9-cko3 ona seconfd system, but I've not seen any breakdown of
> the cko series (ie, the two particular cko patches you're
> referencing). 
> 
> cheers, and thanks
> Cal
> 

Re: reiser4 crash

[Cal]

----------
and then at Thu, 25 Nov 2004 19:55:16 +0300, it was written ...
 >>  >ftp://ftp.namesys.com/pub/reiser4-for-2.6/2.6.9/
 >
 >There was an update today. Please make sure you got patch number 2.
 >

The 2.6.9 patch #2 works just fine - thanks all!  

cheers, Cal

Re: reiser4 crash

[mjt]

On Thu, Nov 25, 2004 at 01:23:43PM +0200, Markus Törnqvist wrote:
>
>I don't remember if I mentioned it, but there were two patches
>from Piotr Neuman's -cko that were required by Reiser4 (according
>to him) but seemed to patch well onto vs's patched system...
>
>Can anyone give any info on this?
>Mr. Neuman for example :)

I checked the patches, from Piotr's broken-out cko3 which he kindly
gave me.

#needed by reiser4
make-tree_lock-an-rwlock.patch.bz2 
invalidate_inodes-speedup.patch.bz2 

What are those? Are they merged?

I'm gonna try the second reiser4 for 2.6.9 patch PROBABLY today,
as it seemed to contain something beyond the transaction patch
vs sent later, but so far the current setup has been working well.

Great work, guys!

-- 
mjt

Re: reiser4 crash

[Cal]

----------
and then at Thu, 25 Nov 2004 20:48:32 +0200, it was written ...
 >I checked the patches, from Piotr's broken-out cko3 which he kindly
 >gave me.
 >
 >#needed by reiser4
 >make-tree_lock-an-rwlock.patch.bz2 
 >invalidate_inodes-speedup.patch.bz2 
 >
 >What are those? Are they merged?

Both of those patches appear to be from the mm series.  They're in
2.6.10-rc2-mm2 and 2.6.10-rc2-mm3 (at least), and have generous
comments at their head regarding their purpose.

cheers, Cal
 

Re: reiser4 crash

[mjt]

On Fri, Nov 26, 2004 at 07:00:59AM +1100, Cal wrote:
>
>Both of those patches appear to be from the mm series.  They're in
>2.6.10-rc2-mm2 and 2.6.10-rc2-mm3 (at least), and have generous
>comments at their head regarding their purpose.

OK, I admit I didn't read through them :)

But they don't seem to be in Reiser4-for-2.6.9? 

bzcat /usr/src/kernel_stuff/cko/2.6.9-cko3/make-tree_lock-an-rwlock.patch.bz2 | patch -p1 --dry-run
patching file fs/buffer.c
Hunk #1 succeeded at 992 (offset 50 lines).
Hunk #2 succeeded at 1000 (offset 50 lines).
patching file fs/inode.c
Hunk #1 succeeded at 201 (offset 5 lines).

Anyway, my compile just failed:

fs/built-in.o(.text+0x9da81): In function `mask_ok_common':
: undefined reference to `vfs_permission'
make[1]: *** [.tmp_vmlinux1] Error 1
make[1]: Leaving directory `/usr/src/linux-2.6.9-cko4a'
make: *** [stamp-build] Error 2

Yeah, I tried to merge that to -cko before trying the vanilla one,
because of obvious performance-related reasons...[1]

I don't think -cko caused that, though, all went afaict well through..

I think I'll boot -cko3 again and just avoid apt-get or something,
this is starting to suck pretty bad :)

[1]
Merge Con's code into mainline, this current one is next to unusable,
damnit :P

-- 
mjt

Re: reiser4 crash

[Cal]

----------
and then at Thu, 25 Nov 2004 22:21:19 +0200, it was written ...
...
 >Anyway, my compile just failed:
 >
 >fs/built-in.o(.text+0x9da81): In function `mask_ok_common':
 >: undefined reference to `vfs_permission'
 >make[1]: *** [.tmp_vmlinux1] Error 1
 >make[1]: Leaving directory `/usr/src/linux-2.6.9-cko4a'
 >make: *** [stamp-build] Error 2
 >
Have a look at 
  2.6.10-rc1-mm3/broken-out/reiser4-generic_acl-fix.patch.  
Around line 16 of fs/reiser4/plugin/security/perm.c,   return
vfs_permission(inode, mask); replaces 
  return generic_permission(inode, mask, NULL);
Or vice versa, I can't remember.

>Yeah,
I tried to merge that to -cko before trying the vanilla one, >because
of obvious performance-related reasons...[1] >
 >I don't think -cko caused that, though, all went afaict well
through.. >
 >I think I'll boot -cko3 again and just avoid apt-get or something,
 >this is starting to suck pretty bad :)
 >
As yet I haven't tried to merge the new 2.6.9
reiser4 code (reiser4-for-2.6.9-2.gz) with 2.6.9-ckx, but  on vanilla
2.6.9 + reiser4-for-2.6.9-2.gz, the apt-get update problem didn't
occur.  I suspect that adding the new r4 code to ck should go ok. 
I'll see if I can find time to give it a go.

cheers, Cal

Re: reiser4 crash

[mjt]

On Fri, Nov 26, 2004 at 08:14:44AM +1100, Cal wrote:
> >fs/built-in.o(.text+0x9da81): In function `mask_ok_common':
> >: undefined reference to `vfs_permission'
> >make[1]: *** [.tmp_vmlinux1] Error 1
> >make[1]: Leaving directory `/usr/src/linux-2.6.9-cko4a'
> >make: *** [stamp-build] Error 2

>Have a look at 
>  2.6.10-rc1-mm3/broken-out/reiser4-generic_acl-fix.patch.  
>Around line 16 of fs/reiser4/plugin/security/perm.c,   return
>vfs_permission(inode, mask); replaces 
>  return generic_permission(inode, mask, NULL);
>Or vice versa, I can't remember.

Uhhuh, you edited that?

In my code it is
return vfs_permission(inode, mask);
so I'll just replace with return generic_permission(inode, mask, NULL);

>As yet I haven't tried to merge the new 2.6.9
>reiser4 code (reiser4-for-2.6.9-2.gz) with 2.6.9-ckx, but  on vanilla
>2.6.9 + reiser4-for-2.6.9-2.gz, the apt-get update problem didn't
>occur.  I suspect that adding the new r4 code to ck should go ok. 
>I'll see if I can find time to give it a go.

I'm compiling such a beast right now.

I also edited as said above and kicked in a new compile...

Shouldn't this warrant a -3 then, because this seems to me like something
that should break for everyone and not just me ;)

Hope I didn't misunderstand anything, I don't have any -mm sources now
at hand nor will I have time for quite a while to start playing around..

-- 
mjt

Re: reiser4 crash

[Cal]

----------
and then at Thu, 25 Nov 2004 23:28:26 +0200, it was written ...
 >>Have a look at 
 >>  2.6.10-rc1-mm3/broken-out/reiser4-generic_acl-fix.patch.  
 >>Around line 16 of fs/reiser4/plugin/security/perm.c,   return
 >>vfs_permission(inode, mask); replaces 
 >>  return generic_permission(inode, mask, NULL);
 >>Or vice versa, I can't remember.
 >
 >Uhhuh, you edited that?

Yep.

 >I'm compiling such a beast right now.
 >
 >I also edited as said above and kicked in a new compile...

Yeah, me too.

 >
 >Shouldn't this warrant a -3 then, because this seems to me like
something >that should break for everyone and not just me ;)

With the amount of work these guys are putting into it all, I wouldn't
dare to suggest what's warranted.  I'm content to fiddle about, learn
what I can, and wait for the guys who really know what they're doing
to pull it all together.  They always do.
 >
 >Hope I didn't misunderstand anything, I don't have any -mm sources
now >at hand nor will I have time for quite a while to start playing
around.. >
Sounds like it's sleep time ... I've just woken up.

cheers, Cal

Re: reiser4 crash

[mjt]

On Fri, Nov 26, 2004 at 08:42:25AM +1100, Cal wrote:

> >I also edited as said above and kicked in a new compile...
>Yeah, me too.

Which I'm still waiting for ;)

>With the amount of work these guys are putting into it all, I wouldn't
>dare to suggest what's warranted.  I'm content to fiddle about, learn
>what I can, and wait for the guys who really know what they're doing
>to pull it all together.  They always do.

Well, yeah, but it wasn't (meant as) a daring and audacious and improper
suggestion, just a suggestion :)

Anyway, I just prefer to try have things working but cut down on the
fiddling, rather just report when something breaks :)

>Sounds like it's sleep time ... I've just woken up.

soon midnight...

-- 
mjt

Re: reiser4 crash

[Cal]

----------
and then at Thu, 25 Nov 2004 23:47:51 +0200, it was written ...
 >Anyway, I just prefer to try have things working but cut down on the
 >fiddling, rather just report when something breaks :)

Vanilla 2.6.9 + 2.6.9-ck3 + latest 2.6.9 reiser4 (#2) patches, builds
and boots clean and easy, no fiddling required.  And, "apt-get update"
didn't explode.  All too cool.

Hope your's turned out the same!

cheers, Cal

reiser4 crash

[Francesco Biscani]

Hi,

I had reiser4 crash pretty badly. Here's the story.

My distribution is Gentoo. As you probably know it uses as packaging system a 
tool called "emerge" which basically installs applications following 
installation scripts called "ebuilds". Usually packages are compiled from 
sources, but not necessarily, since ebuilds can contain totally arbitrary 
instructions.

I decided to install the pre-compiled binary version of Openoffice 1.1.2, 
which under Gentoo is known as "openoffice-bin". The installation went on 
regularly, but near the end everything seemed to hang in the "Registering 
components" phase. No CPU or HD activity. After a while, suspecting a bug in 
the ebuild, I went over the Gentoo forums and I found these posts:

http://forums.gentoo.org/viewtopic.php?t=201410&highlight=openofficebin
http://forums.gentoo.org/viewtopic.php?t=184798&highlight=openofficebin+reiser4

These people also report problems installing openoffice on reiser4. In the 
meanwhile the installation process of openoffice-bin was still hanging, but 
suddenly the CPU went 100%. It was "system" activity, no "user" activity. Top 
revealed that it was the installation process that was eating all my CPU. The 
system was still working, but "sync" was not working (it hung). Pretty much 
worried, CPU still 100%, I tried to reboot, but the system was not able to do 
that. I tried to kill the offending process, with no luck. I had no choice 
but to push the power button.

fsck 0.5.6 revealed these errors:

FSCK: Directory [ccb2c:6d703300000000:10b195] (dir40), node [790184], item 
[0], unit [55]: entry has wrong offset
[10b195:0(NAME):14d69636861656c:2e4275626ce92e4d:14942a136fe7bf]. Should be
[10b195:0(NAME):14d69636861656c:2e4275626ce92e4d:14942a136f370f].
FSCK: Directory [209045:1536f6e6e792052:2e987a] (dir40), node [3593262], item 
[0], unit [5]: entry has wrong offset
[2e987a:0(NAME):1536f6e6e792052:6f6c6c696e73202d:2bd0cd03e55f727a]. Should be
[2e987a:0(NAME):1536f6e6e792052:6f6c6c696e73202d:2bd0cd03bde670ca].

I had to issue a --build-fs, which lead to:

FSCK: No 'lost+found' entry found. Building a new object with the key 
2a:0:ffff.
FSCK: Failed to recognize the plugin for the directory [2a:0:ffff].
FSCK: Trying to recover the directory [2a:0:ffff] with the default 
plugin--dir40.
FSCK: The file [2a:0:ffff] does not have a StatData item. Creating a new one. 
Plugin dir40.
FSCK: Directory [2a:0:ffff]: The entry "." is not found. Insert a new one. 
Plugin (dir40).
FSCK: Node (460152), item (2), [2a:0:ffff] (stat40): wrong size (0), Fixed to 
(1).
FSCK: Node (460152), item (2), [2a:0:ffff] (stat40): wrong bytes (0), Fixed to 
(50).
FSCK: Directory [ccb2c:6d703300000000:10b195] (dir40), node [790184], item 
[0], unit [55]: entry has wrong offset
[10b195:0(NAME):14d69636861656c:2e4275626ce92e4d:14942a136fe7bf]. Should be
[10b195:0(NAME):14d69636861656c:2e4275626ce92e4d:14942a136f370f]. Removed.
FSCK: Node (2917509), item (11), [ccb2c:6d703300000000:10b195] (stat40): wrong 
size (62), Fixed to (61).
FSCK: Node (2917509), item (11), [ccb2c:6d703300000000:10b195] (stat40): wrong 
bytes (4090), Fixed to (4012).
FSCK: Directory [209045:1536f6e6e792052:2e987a] (dir40), node [3593262], item 
[0], unit [5]: entry has wrong offset
[2e987a:0(NAME):1536f6e6e792052:6f6c6c696e73202d:2bd0cd03e55f727a]. Should be
[2e987a:0(NAME):1536f6e6e792052:6f6c6c696e73202d:2bd0cd03bde670ca]. Removed.
FSCK: Node (3688550), item (22), [209045:1536f6e6e792052:2e987a] (stat40): 
wrong size (13), Fixed to (12).
FSCK: Node (3688550), item (22), [209045:1536f6e6e792052:2e987a] (stat40): 
wrong bytes (1154), Fixed to (1052).

After that fs was consistent. In lost+found I found some files from the 
web-browser's cache and some temporary files from the installation of 
openoffice. So it probably stopped committing changes to the fs when the 
installation hung.

System logs did not record anything. Fortunately it seems like nothing is 
missing from my fs. Should I be worried about something? fsck does not find 
any errors.

Using auto-snapshot from 20 July agains 2.6.7-mm7.

Hope this is useful. I'll be glad to give more details is asked to. 
Regards,

  Francesco

Re: reiser4 crash

[mjt]

On Sat, Jul 24, 2004 at 06:27:54PM +0200, Francesco Biscani wrote:
>
>Hope this is useful. I'll be glad to give more details is asked to. 
>Regards,

Try patching in
http://mjt.nysv.org/reiser/log-write-readpage-releasepage-2.diff.gz

Then recompile the kernel with debugging and assertions (printing was iirc
not required) turned on and try to reproduce it.

Note, that this may cause your system to oops and go haywire big time, so
if you have a netconsole or something to log, it's great.
One other method is cat /proc/kmsg > foo and scping foo elsewhere before
the computer goes down.

The patch above is from Namesys, but I don't think it's in any of the
auto-snapshots (should it be?) and it may or may not give more info
on what's going on, but if it does, the output is some 512 extra lines
of log.

-- 
mjt

Re: reiser4 crash

[Francesco Biscani]

On Sunday 25 July 2004 09:41, Markus Törnqvist wrote:
> On Sat, Jul 24, 2004 at 06:27:54PM +0200, Francesco Biscani wrote:
> >Hope this is useful. I'll be glad to give more details is asked to.
> >Regards,
>
> Try patching in
> http://mjt.nysv.org/reiser/log-write-readpage-releasepage-2.diff.gz
>
> Then recompile the kernel with debugging and assertions (printing was iirc
> not required) turned on and try to reproduce it.
>

Well, I'll try to do something but it'll be difficult. On the laptop I have 
reiser4 on /, and I cannot afford to break it. I could try on the workstation 
at home where I have a test partition for reiser4, but I'll be away until the 
next weekend. Maybe some other Gentoo user could help (Redeeman are you 
listening? :))

> Note, that this may cause your system to oops and go haywire big time, so
> if you have a netconsole or something to log, it's great.
> One other method is cat /proc/kmsg > foo and scping foo elsewhere before
> the computer goes down.
>

Ok.

An update: I have found a dir called 

"lost_name_<insert garbage here>"

I've fixed the name, which obviously was lost during --build-fs. I'm getting a 
bit psychotic about this but is there anything I can do to make sure 
everything is alright? I've searched for other lost names but I found 
nothing. The system is working as normal. Should I expect that something was 
lost at all? It is a bit strange because the dir with the garbled name was 
not open in write mode when the crash happened. Should I expect random 
corruption to be happened?

Thanks very much.

Re: reiser4 crash

[Francesco Biscani]

On Sunday 25 July 2004 21:37, Francesco Biscani wrote:
> On Sunday 25 July 2004 09:41, Markus Törnqvist wrote:
> > On Sat, Jul 24, 2004 at 06:27:54PM +0200, Francesco Biscani wrote:
> > >Hope this is useful. I'll be glad to give more details is asked to.
> > >Regards,
> >
> > Try patching in
> > http://mjt.nysv.org/reiser/log-write-readpage-releasepage-2.diff.gz
> >
> > Then recompile the kernel with debugging and assertions (printing was
> > iirc not required) turned on and try to reproduce it.
>
> Well, I'll try to do something but it'll be difficult. On the laptop I have
> reiser4 on /, and I cannot afford to break it. I could try on the
> workstation at home where I have a test partition for reiser4, but I'll be
> away until the next weekend. Maybe some other Gentoo user could help
> (Redeeman are you listening? :))
>


Mmmhh.. I was think that the bug could pop up also by just installing the 
binary version of openoffice. I did not see any strange command in the ebuild 
and I've never had problems with emerge+reiser4 before. Is anyone brave 
enough to try that?