Re: [reiserfs-list] Re: funny file permission after reiserfsck
Hello! On Sat, Dec 15, 2001 at 04:20:15PM +0300, Hans Reiser wrote: mount -conv all the workstations. mount -o conv does not work if you do 'mount -o remount,conv' (ie for root fs) (But if course booting from rescue CD is still possible ;) ) Bye, Oleg
Re: [reiserfs-list] Re: funny file permission after reiserfsck
Vitaly Fertman wrote: Hi, Hans Reiser wrote: Is there a way to fix the file system after it gets into this state? Thanks! Wilson vitaly will help you with this. Hans Is there any reason why running reiserfsck multiple times have different result? I did a rebuild tree, and then ran reiserfsck 3 times. Only after the 3rd time were all the funny file permission completely corrected. Wilson It should not happen, rebuild-tree should fix all problems. I will fix it just as get a partition with such corruptions. BTW, what do you mean I did a rebuild tree, and then ran reiserfsck 3 times? You run reiserfsck --rebuild-tree3 times or what? First time, I did reiserfsck --rebuild_tree. And then I did 3 times with reiserfsck -x -o Wilson
Re: [reiserfs-list] Re: funny file permission after reiserfsck
Hello! On Fri, Dec 14, 2001 at 05:39:32AM +0100, Dieter Nützel wrote: I have found the culprit. The _BAD_ guy is _P_ P-reiser_stats_fix.patch. This is very strange, I can say. Because P-reiser_stats_fix.patch does not touch any critical stuff. While I was reviewing it again today, I noticed a little mistake (I uploaded updated version to ftp), but this one cannot lead to filesystem corruptions and only can be seen as -o conv option not working on v3.5 format filesystems. Bye, Oleg
Re: [reiserfs-list] Re: funny file permission after reiserfsck
Hi, if you have a broken partition which cannot be recovered by fsck I would like to have a look at it. extract metadata of your partition please with reiserfsprogs-3.x.0j/debugreiserfs -p .bitmap /dev/broken_device | bzip2 -c xxx.bz2 and send me xxx.bz2 file please. Could you point to broken files (with 0 attribute, unrecovered links, etc). Old logs would be not bad also. Am Donnerstag, 13. Dezember 2001 10:26 schrieben Sie: Dieter Nützel wrote: On Thursday, 13. December 2001 03:15 you wrote: Hi all, After I've run reiserfsck on my disk, I have a file with 0 permission: # ls -l 0- 1 root root 238 Dec 11 22:52 lk This file is not readable. Adding rw permission to it does not make it readable again: # chmod a+rw lk # ls -l 0rw-rw-rw- 1 root root 238 Dec 11 22:52 lk # cat lk # You are running ReiserFS on 2.4.16 + some ReiserFS patches including inode-attrs, right? More details, please. I had a lot of trouble with 2.4.17-pre4 and -pre7 + 2.4.16.pending K-P and expanding-truncate-4.diff. O-inode-attrs.patch was the culprit. Even the extended file attribute tools didn't helped/solved all of my problems. Have you tried chattr -R = /your-mount points to clear all permissions? I did but got some bad ones ever and ever again in /bin (vi) :-( /etc (termcap, localtime, init.d) /dev (mouse, /dev/cciss/*) /lib (libpam.so was currupted) :-( /lib/modules/current-kernel :-( /usr/src/kernel after reboot. I have several reiserfsck-pre13 /dev/sd** logs, if anybody wants them? After reiserfsck several links were broken (pointing to nowhere). The same files as with broken attributes? Only solution was to revert from O-inode-attrs.patch. Now I am happly running Linux 2.4.17-pre8 preempt-kernel-rml-2.4.17-pre8-1 lock-break-rml-2.4.17-pre8-1 bootmem-2.4.17-pre6 00_nanosleep-5 2.4.16.pending K-P except of O-inode-attrs.patch expanding-truncate-4.diff -Dieter we will pull O off of our website. Thanks Dieter. Yes, Hans that would be better for now. But I need badly advice. It seems that I chocked my / root partition (sda3) plus my root-backup (sdb8)!!! After that I've tried to build a second root-backup on sdb7 (with random parts taken from both others) which failed under 2.4.17-pre8-preempt (without O, see above). So I reverted to 2.4.17-pre4-preempt (all patches are the same, yes without O) created a new ReiserFS partition on sdb7 and had luck. --- Pu :-) Now, I am running / root from /dev/sdb7 under 2.4.17-pre4-preempt and think about to create a new sda3 partition (mkreiserfs /dev/sda3) and rebuild it from sdb7. What do you think? I ran reiserfsck over and over again on sda3, sdb8 and sdb7 (the old one) with 2.4.17-pre4-preempt and -pre8-preempt without success. Do you mean you run rebuild-tree and it does not fix bad ( 0 ) attributes? So I am not 100% sure if the O patch is the culprit. But it could be that the disk format was so much brocken after my O patch runs that the kernel version was not related. The only solution was a recreation of my corrupted partition. Luckily only on was broken and I have some spare disks around...;-) To Wilson: I think you should rebuild your system ;-( Anyone want some reiserfsck logs??? -Dieter -- Thanks, Vitaly Fertman
Re: [reiserfs-list] Re: funny file permission after reiserfsck
Dieter Nützel wrote: Am Donnerstag, 13. Dezember 2001 10:26 schrieben Sie: Dieter Nützel wrote: On Thursday, 13. December 2001 03:15 you wrote: Hi all, After I've run reiserfsck on my disk, I have a file with 0 permission: # ls -l 0- 1 root root 238 Dec 11 22:52 lk This file is not readable. Adding rw permission to it does not make it readable again: # chmod a+rw lk # ls -l 0rw-rw-rw- 1 root root 238 Dec 11 22:52 lk # cat lk # You are running ReiserFS on 2.4.16 + some ReiserFS patches including inode-attrs, right? More details, please. I had a lot of trouble with 2.4.17-pre4 and -pre7 + 2.4.16.pending K-P and expanding-truncate-4.diff. O-inode-attrs.patch was the culprit. Even the extended file attribute tools didn't helped/solved all of my problems. Have you tried chattr -R = /your-mount points to clear all permissions? I did but got some bad ones ever and ever again in /bin (vi) :-( /etc (termcap, localtime, init.d) /dev (mouse, /dev/cciss/*) /lib (libpam.so was currupted) :-( /lib/modules/current-kernel :-( /usr/src/kernel after reboot. I have several reiserfsck-pre13 /dev/sd** logs, if anybody wants them? After reiserfsck several links were broken (pointing to nowhere). Only solution was to revert from O-inode-attrs.patch. Now I am happly running Linux 2.4.17-pre8 preempt-kernel-rml-2.4.17-pre8-1 lock-break-rml-2.4.17-pre8-1 bootmem-2.4.17-pre6 00_nanosleep-5 2.4.16.pending K-P except of O-inode-attrs.patch expanding-truncate-4.diff -Dieter we will pull O off of our website. Thanks Dieter. Yes, Hans that would be better for now. But I need badly advice. It seems that I chocked my / root partition (sda3) plus my root-backup (sdb8)!!! After that I've tried to build a second root-backup on sdb7 (with random parts taken from both others) which failed under 2.4.17-pre8-preempt (without O, see above). So I reverted to 2.4.17-pre4-preempt (all patches are the same, yes without O) created a new ReiserFS partition on sdb7 and had luck. --- Pu :-) Now, I am running / root from /dev/sdb7 under 2.4.17-pre4-preempt and think about to create a new sda3 partition (mkreiserfs /dev/sda3) and rebuild it from sdb7. What do you think? I ran reiserfsck over and over again on sda3, sdb8 and sdb7 (the old one) with 2.4.17-pre4-preempt and -pre8-preempt without success. So I am not 100% sure if the O patch is the culprit. But it could be that the disk format was so much brocken after my O patch runs that the kernel version was not related. The only solution was a recreation of my corrupted partition. Luckily only on was broken and I have some spare disks around...;-) To Wilson: I think you should rebuild your system ;-( Anyone want some reiserfsck logs??? -Dieter Forgive me, but I think you have figured out what to do. Vitaly can help you further in the morning, and he will be more familiar with such issues. Hans
Re: [reiserfs-list] Re: funny file permission after reiserfsck
On 12/13/2001 09:28 PM, Dieter Nützel wrote: Am Donnerstag, 13. Dezember 2001 20:44 schrieb Manuel Krause: On 12/13/2001 07:53 PM, Dieter Nützel wrote: Am Donnerstag, 13. Dezember 2001 10:26 schrieben Sie: Dieter Nützel wrote: On Thursday, 13. December 2001 03:15 you wrote: [...] [-] I compiled Dieters patch combination this morning except for bootmem and nanosleep. They shouldn't harm. Even Preempt + lock-break (including the latest ReiserFS lock-break ;-) You mean lock-break-rml-2.4.17-pre8-1.patch or something very special? ;-) After some minutes uptime I got disappearing files with this behaviour rm: cannot remove `/dev/parport16': No such file or directory mknod: `/dev/parport16': File exists and many lines vs-15011: reiserfs_release_objectid: tried to free free object id (.) Yes, had such messages, too. Of course, I was not able to set (or get) permissions for those files... reiserfsck --check said --fix-fixable would solve the problems but it didn't catch all. For now, I can say --rebuild-tree completely recovered the filesystem. (reiserfsprogs 3.x.0k-pre13) Have you rebooted after that? I had your feeling, too but after reboot. --- Bang all problems were there, again... First I rebooted after --rebuild-tree to the same kernel and some minutes later the problems came up again. Yes. I repeated --rebuild-tree and booted to my old kernel (2.4.16 + reiserfs A..N + Andrew Mortons low-latency patch). Everything was restored o.k. then. Until... This patch combination didn't seem to affect my ext2 partition at all. As I never had the inode-attrs patch running but patches A..P You mean 2.4.16 + A-P except O and 2.4.17-pre4 and above + K-P except O, right? Had you applied Chris's expanding-truncate-4.diff. ...I then combined 2.4.16 + A..N + P + Chris's expanding-truncate-4.diff + low-latency. I got these disappearing files again afterwards. So again --rebuild-tree and so on. Now I have 2.4.17-pre8, K..N+P + preempt-1 + lock-break-1 running. (I didn't try 2.4.17-pre4) Except for these many vs-15011 lines I didn't see a problem so far. work well with 2.4.16 there's something incompatible within the others. Maybe someone wanted this additional information. Thanks, so didn't have to go back, only drop O...;-) It's very clear now that the expanding-truncate-4 patch needs to be excluded and/or adjusted, too. :-) I hope that works for you after your inode-attrs experiment! Manuel
Re: [reiserfs-list] Re: funny file permission after reiserfsck
On 12/13/2001 10:45 PM, Chris Mason wrote: On Thursday, December 13, 2001 10:41:13 PM +0100 Manuel Krause [EMAIL PROTECTED] wrote: It's very clear now that the expanding-truncate-4 patch needs to be excluded and/or adjusted, too. :-) I hope that works for you after your inode-attrs experiment! Odd, which low latency patches were you running? -chris With 2.4.16 +reiserfs-patches: Andrew Mortons low-latency patch http://www.zip.com.au/~akpm/linux/2.4.16-low-latency.patch.gz (from page http://www.zip.com.au/~akpm/linux/schedlat.html ) and with 2.4.17-pre8 +reiserfs-patches: the preemptible kernel lock-break patches from Robert M. Love http://www.kernel.org/pub/linux/kernel/people/rml/preempt-kernel/v2.4/preempt-kernel-rml-2.4.17-pre8-1.patch http://www.kernel.org/pub/linux/kernel/people/rml/lock-break/v2.4/lock-break-rml-2.4.17-pre8-1.patch (from page http://www.tech9.net/rml/linux/ ) Thanks, Manuel
Re: [reiserfs-list] Re: funny file permission after reiserfsck
On Thursday, December 13, 2001 11:17:12 PM +0100 Manuel Krause [EMAIL PROTECTED] wrote: On 12/13/2001 10:45 PM, Chris Mason wrote: On Thursday, December 13, 2001 10:41:13 PM +0100 Manuel Krause [EMAIL PROTECTED] wrote: It's very clear now that the expanding-truncate-4 patch needs to be excluded and/or adjusted, too. :-) I hope that works for you after your inode-attrs experiment! Odd, which low latency patches were you running? -chris With 2.4.16 +reiserfs-patches: Andrew Mortons low-latency patch http://www.zip.com.au/~akpm/linux/2.4.16-low-latency.patch.gz (from page http://www.zip.com.au/~akpm/linux/schedlat.html ) This should be safe. Any chance I could talk you into testing 2.4.17-pre8 + andrew's patch? -chris
Re: [reiserfs-list] Re: funny file permission after reiserfsck
On 12/13/2001 11:16 PM, Chris Mason wrote: On Thursday, December 13, 2001 11:17:12 PM +0100 Manuel Krause [EMAIL PROTECTED] wrote: On 12/13/2001 10:45 PM, Chris Mason wrote: On Thursday, December 13, 2001 10:41:13 PM +0100 Manuel Krause [EMAIL PROTECTED] wrote: It's very clear now that the expanding-truncate-4 patch needs to be excluded and/or adjusted, too. :-) I hope that works for you after your inode-attrs experiment! Odd, which low latency patches were you running? -chris With 2.4.16 +reiserfs-patches: Andrew Mortons low-latency patch http://www.zip.com.au/~akpm/linux/2.4.16-low-latency.patch.gz (from page http://www.zip.com.au/~akpm/linux/schedlat.html ) This should be safe. Any chance I could talk you into testing 2.4.17-pre8 + andrew's patch? -chris Andrew has another one for 2.4.17-pre2. Maybe that's better? Have you had a look on it, too? With patches A..N+P should I really apply expanding-truncate-4 ? Manuel
Re: [reiserfs-list] Re: funny file permission after reiserfsck
Am Donnerstag, 13. Dezember 2001 23:16 schrieb Chris Mason: On Thursday, December 13, 2001 11:17:12 PM +0100 Manuel Krause [EMAIL PROTECTED] wrote: On 12/13/2001 10:45 PM, Chris Mason wrote: On Thursday, December 13, 2001 10:41:13 PM +0100 Manuel Krause [EMAIL PROTECTED] wrote: It's very clear now that the expanding-truncate-4 patch needs to be excluded and/or adjusted, too. :-) I hope that works for you after your inode-attrs experiment! Odd, which low latency patches were you running? -chris With 2.4.16 +reiserfs-patches: Andrew Mortons low-latency patch http://www.zip.com.au/~akpm/linux/2.4.16-low-latency.patch.gz (from page http://www.zip.com.au/~akpm/linux/schedlat.html ) This should be safe. Any chance I could talk you into testing 2.4.17-pre8 + andrew's patch? Maybe Manuel will...;-) The latest lock-break-rml-2.4.17-pre8-1.patch from Robert is based on Andrew's patch and include some (small) lock-breaks for ReiserFS. Any comments Chris? Has Robert something overlooked? Maybe only when expanding-truncate-4.patch comes into play? -Dieter BTW I am going after Manuel and try 2.4.17-pre8-preempt + lock-break + K-N+P witchout Chris's one.
Re: [reiserfs-list] Re: funny file permission after reiserfsck
On Thursday, December 13, 2001 11:51:13 PM +0100 Dieter Nützel [EMAIL PROTECTED] wrote: With 2.4.16 +reiserfs-patches: Andrew Mortons low-latency patch http://www.zip.com.au/~akpm/linux/2.4.16-low-latency.patch.gz (from page http://www.zip.com.au/~akpm/linux/schedlat.html ) This should be safe. Any chance I could talk you into testing 2.4.17-pre8 + andrew's patch? Maybe Manuel will...;-) The latest lock-break-rml-2.4.17-pre8-1.patch from Robert is based on Andrew's patch and include some (small) lock-breaks for ReiserFS. Any comments Chris? Has Robert something overlooked? Maybe only when expanding-truncate-4.patch comes into play? The lock break or the low latency patch probably break a scheduling rule in the reiserfs code that makes holes in the file, which gets exercised by the expanding truncate patch. I'll take a closer look at Robert's patch. If I'm right, than without the expanding-truncate patch you should be able to trigger corruptions with dd if=/dev/zero of=foo seek=2000 bs=1MB count=1 with other stuff running in the background. -chris
Re: [reiserfs-list] Re: funny file permission after reiserfsck
On 12/13/2001 11:51 PM, Dieter Nützel wrote: Am Donnerstag, 13. Dezember 2001 23:16 schrieb Chris Mason: On Thursday, December 13, 2001 11:17:12 PM +0100 Manuel Krause [EMAIL PROTECTED] wrote: On 12/13/2001 10:45 PM, Chris Mason wrote: On Thursday, December 13, 2001 10:41:13 PM +0100 Manuel Krause [EMAIL PROTECTED] wrote: It's very clear now that the expanding-truncate-4 patch needs to be excluded and/or adjusted, too. :-) I hope that works for you after your inode-attrs experiment! Odd, which low latency patches were you running? -chris With 2.4.16 +reiserfs-patches: Andrew Mortons low-latency patch http://www.zip.com.au/~akpm/linux/2.4.16-low-latency.patch.gz (from page http://www.zip.com.au/~akpm/linux/schedlat.html ) This should be safe. Any chance I could talk you into testing 2.4.17-pre8 + andrew's patch? Maybe Manuel will...;-) The latest lock-break-rml-2.4.17-pre8-1.patch from Robert is based on Andrew's patch and include some (small) lock-breaks for ReiserFS. Any comments Chris? Has Robert something overlooked? Maybe only when expanding-truncate-4.patch comes into play? -Dieter BTW I am going after Manuel and try 2.4.17-pre8-preempt + lock-break + K-N+P witchout Chris's one. That might be no good idea. I've now double checked that I really applied the mentioned patches but still get corruptions in the old way. A --rebuild-tree fixes them, I reboot and reboot *again* some minutes later: Then I find wrong permissions and some disappearing files. Mmh. Dangerous. Best wishes, Manuel
Re: [reiserfs-list] Re: funny file permission after reiserfsck
On Friday, December 14, 2001 12:52:19 AM +0100 Manuel Krause [EMAIL PROTECTED] wrote: That might be no good idea. I've now double checked that I really applied the mentioned patches but still get corruptions in the old way. A --rebuild-tree fixes them, I reboot and reboot *again* some minutes later: Then I find wrong permissions and some disappearing files. Mmh. Dangerous. Ok, this makes more sense than the expanding truncate patch breaking things. Could you please run a pure 2.4.17-pre8 kernel for a bit, lets make sure the base kernel is working for you. I'll read more in the preempt patches after dinner ;-) -chris
