Re: reiser4 corruption on initial copy
On Fri, 01 Sep 2006 17:35:29 -0500, David Masover wrote: Peter wrote: 2) I did run badblocks on the dest, and it was clean. 3) I am using the patch from 2.6.17.3 and in my kernel, I have full preempt and cfq scheduling. What about the kernel on the livecd? Anticipatory Voluntary Plus, it is smp, so there are some additional options checked. Should I have preempt=none with reiser4? -- Peter + Do not reply to this email, it is a spam trap and not monitored. I can be reached via this list, or via jabber: pete4abw at jabber.org ICQ: 73676357
Re: Need help retrieving data
On 2 September 2006 13:32, Alex Efros wrote:
Hi!
So, I did everything correctly to fix it? --rebuild-tree doesn't
broke anything?
usually not.
but reiserfsck --rebuild-tree is a complex operation. It has a possibility to
insert wrong blocks into the tree if your fs was used to store another
reiserfs image. and you have a chance to hit new reiserfsck bug.
unfortunately no fix for fsck is available yet.
If you provide fixed reiserfsck version, I can run it on my image to
test it and confirm image become mountabe after --rebuild-sb. But I
can't leave this 3GB image on my drive for months, so if you wish
to make the partition mountable again it is enough to change
one byte in the super block from 0 (hash is not set) to 3 (r5 hash).
It can be done by a hex editor.
hexdump -C of block #16 (reiserfs uses 4k-size blocks, numbers start with 0):
...
0030 06 00 01 00 52 65 49 73 45 72 32 46 73 00 00 00 |ReIsEr2Fs...|
0040 03 00 00 00 05 00 c6 04 02 00 00 00 89 28 00 00 |..ф.┴(..|
^^
this byte.
...
according with:
struct reiserfs_super_block_v1 {
...
char s_magic[10]; /* reiserfs magic string indicates that
* file system is reiserfs:
* ReIsErFs or ReIsEr2Fs or ReIsEr3Fs */
__le16 s_fs_state; /* it is set to used by fsck to mark which
* phase of rebuilding is done */
__le32 s_hash_function_code;/* indicate, what hash function is
being use
...
this testing from me - please provide fixed version in about 7-10
days or at least notify me when it will be ready - if your need more
time I probably move it to DVD-RW.
I already have a broken fs to experiment with.
--
Alex.
quota problem with 2.6.15.7
Hi,
I just wanted to enable quotas on one of our server systems and got an oops.
This is an opteron system with a kernel in 64bit mode.
As you can see, the filesystem is reiserfs.
[8278222.836924] Unable to handle kernel paging request at 0fd7 RIP:
[8278222.842655] 80394699{__down_read+101}
[8278222.851260] PGD f3509067 PUD adf61067 PMD 0
[8278222.856596] Oops: 0002 [1] SMP
[8278222.860597] CPU 1
[8278222.863231] Modules linked in: ipt_MASQUERADE ipt_state iptable_filter
nfsd exportfs iptable_nat ip_nat ip_conntrack ip_tables i2c_
amd8111 pl2303 usbserial ohci_hcd usbcore bluesmoke_k8 bluesmoke_mc w83627hf
i2c_isa lm85 adm1026 hwmon_vid i2c_amd756 i2c_core bcm5700
[8278222.891808] Pid: 16212, comm: quotaon Not tainted 2.6.15.7 #1
[8278222.898891] RIP: 0010:[80394699]
80394699{__down_read+101}
[8278222.907557] RSP: 0018:81003b987b50 EFLAGS: 00010206
[8278222.914370] RAX: 8100f81b1408 RBX: 810043336180 RCX:
8100f81b1530
[8278222.923148] RDX: 0fd7 RSI: RDI:
81003b987bc8
[8278222.931931] RBP: 8100f81b1400 R08: R09:
810081ad9440
[8278222.940723] R10: 1000 R11: 80394646 R12:
0001
[8278222.949497] R13: R14: R15:
0001
[8278222.958273] FS: 2ae00090() GS:80515880()
knlGS:558dd2a0
[8278222.968202] CS: 0010 DS: ES: CR0: 8005003b
[8278222.975283] CR2: 0fd7 CR3: dc0aa000 CR4:
06e0
[8278222.984061] Process quotaon (pid: 16212, threadinfo 81003b986000, task
810043336180)
[8278222.994398] Stack: 8100f81b1408 810043336180
8101
[8278223.004002]8100f9fb23c0 00010001
00010001
[8278223.013841]8100
[8278223.020126] Call Trace:8017bc08{link_path_walk+194}
80394646{__down_read+18}
[8278223.030894]80229853{_atomic_dec_and_lock+43}
801bc1f1{reiserfs_quota_on+191}
[8278223.042504]8017bc08{link_path_walk+194}
80394646{__down_read+18}
[8278223.052854]8019f482{sys_quotactl+960}
8014e2c5{find_get_page+31}
[8278223.063186]8014ed81{filemap_nopage+364}
8015ec3e{__handle_mm_fault+1740}
[8278223.074364]801766ac{vfs_getattr_it+72}
80176852{vfs_fstat+108}
[8278223.084496]80176add{cp_new_stat+233}
80229853{_atomic_dec_and_lock+43}
[8278223.095483]80183702{dput+49}
80187f9b{mntput_no_expire+23}
[8278223.105218]8016dd9f{filp_close+89}
8010d852{system_call+126}
[8278223.115142]
[8278223.118114]
[8278223.118115] Code: 48 89 22 48 89 54 24 08 c7 45 04 01 00 00 00 fb 48 83 7c
24
[8278223.129157] RIP 80394699{__down_read+101} RSP 81003b987b50
[8278223.137621] CR2: 0fd7
Thanks,
Bernd
--
Bernd Schubert
PCI / Theoretische Chemie
Universität Heidelberg
INF 229
69120 Heidelberg
wrt: checking reiserfs/4 partitions on boot
On the namesys.com FAQ page, it is recommended that 0 0 be placed at the end of the fstab lines for reiserfs partitions. I have two questions: 1) does this recommendation also apply for reiser4? 2) why is this recommendation made? Is it unnecessary to routinely check reiser partitions? I understand that in the event of an abnormal shutdown, fsck will be forced, correct? Thx -- Peter + Do not reply to this email, it is a spam trap and not monitored. I can be reached via this list, or via jabber: pete4abw at jabber.org ICQ: 73676357
Re: wrt: checking reiserfs/4 partitions on boot
Peter wrote: On the namesys.com FAQ page, it is recommended that 0 0 be placed at the end of the fstab lines for reiserfs partitions. I have two questions: 1) does this recommendation also apply for reiser4? 2) why is this recommendation made? Is it unnecessary to routinely check reiser partitions? I understand that in the event of an abnormal shutdown, fsck will be forced, correct? I think the idea is that in the event of an abnormal shutdown, you simply replay the journal. With Reiser4, the likelihood of having to run fsck should be even less. Probably isn't now, but should be.
Re: reiser4 corruption on initial copy
Peter wrote: On Fri, 01 Sep 2006 17:35:29 -0500, David Masover wrote: Peter wrote: 2) I did run badblocks on the dest, and it was clean. 3) I am using the patch from 2.6.17.3 and in my kernel, I have full preempt and cfq scheduling. What about the kernel on the livecd? Anticipatory Voluntary Yes, that should be fine, but I was wondering if it's the same version, if you built it yourself, etc etc. Plus, it is smp, so there are some additional options checked. Should I have preempt=none with reiser4? I'm not sure.
