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] reiserfs quota patches for 2.4.17
On Thu, 13 Dec 2001 21:39, Philippe Gramoullé wrote: I just got 2.4.16 quota patches few hours ago before i saw this post so i wanted to download the new patches but right now there is no 2.4.17 directory on the suse.com ftp server. Now there is. Try again! ftp dir 500 'EPSV': command not understood. 227 Entering Passive Mode (202,58,118,12,7,93) 150 Opening ASCII mode data connection for /bin/ls. total 24 drwxr-xr-x 6 suse suse 4096 Dec 13 19:46 . drwxr-xr-x 4 suse suse 4096 Oct 16 02:57 .. drwxr-xr-x 2 suse suse 4096 Nov 6 16:23 2.4.13 drwxr-xr-x 2 suse suse 4096 Nov 8 17:50 2.4.14 drwxr-xr-x 2 suse suse 4096 Nov 29 21:55 2.4.16 drwxr-xr-x 2 suse suse 4096 Dec 13 19:47 2.4.17 226 Transfer complete. ftp -- MfG / Regards Friedrich Lobenstock
Re: [reiserfs-list] reiserfs quota patches for 2.4.17
On Thursday, December 13, 2001 09:39:54 PM +0100 Philippe Gramoullé [EMAIL PROTECTED] wrote: Hi Chris, I just got 2.4.16 quota patches few hours ago before i saw this post so i wanted to download the new patches but right now there is no 2.4.17 directory on the suse.com ftp server. The suse ftp server mirror hasn't picked them up yet. I think it updates every 3 hours, but it seems to have been faster recently. They aren't large, I can forward privately if needed. -chris
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] funny file permission after reiserfsck
On Thu, 13 Dec 2001 04:15, W. Wilson Ho 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 # From filemode.c as referenced by ls on my system, here's the list of prefix characters. No '0' character. /* Return a character indicating the type of file described by file mode BITS: 'd' for directories 'b' for block special files 'c' for character special files 'm' for multiplexor files 'M' for an off-line (regular) file 'l' for symbolic links 's' for sockets 'p' for fifos '-' for regular files '?' for any other file type. */ What distribution do you use? From my reading of the ls source I don't think it's possible to cause a leading '0' on Debian (of course I could have missed something, that source is painful to read). What happens when you run stat lk? -- http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/projects.html Projects I am working on http://www.coker.com.au/~russell/ My home page
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] reiserfs quota patches for 2.4.17
Chris Mason wrote: The suse ftp server mirror hasn't picked them up yet. I think it updates every 3 hours, but it seems to have been faster recently. Well, it looks that it has been updated :o) They aren't large, I can forward privately if needed. Thank you very much. This is not needed anymore now that the files are available. I'll try this out ASAP and bug report as usual if we find something wrong. -chris Philippe.
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
[reiserfs-list] mkreiserfs segfaults with 3.x.0k-pre13
Hi Vladimir, My setup : 4x 12 disks x72Go RAID 5 on a RAID PERC3/QC Partition size is about 1.7 To mkreiserfs segfaults when i try to make the partition. I can reproduce it every time. Here is the gdb trace: (gdb) set args --hash r5 --format 3.6 /dev/sdd1 (gdb) run Starting program: /usr/src/reiserfsprogs-3.x.0k-pre13/mkreiserfs/./mkreiserfs --hash r5 --format 3.6 /dev/sdd1 -mkreiserfs, 2001- reiserfsprogs 3.x.0k-pre13 Format 3.6 with standard journal Count of blocks on the device: 4187425469 Number of blocks consumed by mkreiserfs formatting process: 70466 Blocksize: 4096 Hash function used to sort names: r5 Journal Size 8193 blocks Journal Max transaction length 1024 ATTENTION: YOU SHOULD REBOOT AFTER FDISK! ALL DATA WILL BE LOST ON '/dev/sdd1'! Continue (y/n):y Initializing journal - 0%20%40%60%80%100% Program received signal SIGSEGV, Segmentation fault. find_buffer (dev=7, block=-107541828, size=4096) at io.c:274 274 next = tmp-b_hash_next; (gdb) bt #0 find_buffer (dev=7, block=-107541828, size=4096) at io.c:274 #1 0x0804ab01 in getblk (dev=7, block=-107541828, size=4096) at io.c:350 #2 0x0804acc6 in bread (dev=7, block=4187425468, size=4096) at io.c:439 #3 0x0805e17c in reiserfs_flush_to_ondisk_bitmap (bm=0x806c0a0, fs=0x806bfb8) at bitmap.c:276#4 0x0805ea17 in reiserfs_close_ondisk_bitmap (fs=0x806bfb8) at bitmap.c:667#5 0x0805c344 in reiserfs_close (fs=0x806bfb8) at reiserfslib.c:357#6 0x0804a4d6 in main (argc=6, argv=0xb6b4) at mkreiserfs.c:685#7 0x4003565f in __libc_start_main () from /lib/libc.so.6(gdb) full backtrace: (gdb) bt full #0 find_buffer (dev=7, block=-107541828, size=4096) at io.c:274 dev = 7 block = -107541828 size = 4096 next = (struct buffer_head *) 0x20736e61 #1 0x0804ab01 in getblk (dev=7, block=-107541828, size=4096) at io.c:350 dev = 7 size = 4096 bh = (struct buffer_head *) 0xb7f6 #2 0x0804acc6 in bread (dev=7, block=4187425468, size=4096) at io.c:439 block = 4187425468 bh = (struct buffer_head *) 0xf9970abc #3 0x0805e17c in reiserfs_flush_to_ondisk_bitmap (bm=0x806c0a0, fs=0x806bfb8) at bitmap.c:276to_copy = 0 copied = 0 i = 0 p = 0x8 Address 0x8 out of bounds last_byte_unused_bits = 134660024 block = 134609447 bh = (struct buffer_head *) 0xb5ac #4 0x0805ea17 in reiserfs_close_ondisk_bitmap (fs=0x806bfb8) at bitmap.c:667fs = (reiserfs_filsys_t *) 0x806bfb8 #5 0x0805c344 in reiserfs_close (fs=0x806bfb8) at reiserfslib.c:357 fs = (reiserfs_filsys_t *) 0x806bfb8 #6 0x0804a4d6 in main (argc=6, argv=0xb6b4) at mkreiserfs.c:685 fs = (reiserfs_filsys_t *) 0x806bfb8 force = 0 device_name = 0xb7f6 /dev/sdd1 jdevice_name = 0x0 fs_size = 4187425469 c = -1348 flag = 0 #7 0x4003565f in __libc_start_main () from /lib/libc.so.6 No symbol table info available. (gdb) The fact is that it dosn't happen with 3.x.0j: root@bigass:/usr/src/reiserfsprogs-3.x.0j/mkreiserfs# date; ./mkreiserfs -h r5 -v 2 /dev/sdd1; date Fri Dec 14 03:47:16 CET 2001 -mkreiserfs, 2001- reiserfsprogs 3.x.0j === LEAF NODE (8211) contains level=1, nr_items=2, free_space=3932 rdkey - --|###|type|ilen|f/sp| loc|fmt|fsck| key || |||e/cn|| |need| | ---| 0|1 2 0x0 SD, len 44, entry count 0, fsck need 0, format new| (NEW SD), mode drwxr-xr-x, size 48, nlink 2, mtime 12/14/2001 03:47:16 blocks 8 ---| 1|1 2 0x1 DIR, len 48, entry count 2, fsck need 0, format old| ###: Name lengthObject key Hash Gen number 0: .( 1) 1 2 01, loc 40, state 4 ?? 1: .. ( 2) 0 1 02, loc 32, state 4 ??=== Creating reiserfs of 3.6 format Block size 4096 bytes Block count 429329084 Used blocks 21314 Free blocks count 429307770 First 16 blocks skipped Super block is in 16 Bitmap blocks (13103) are : 17, 32768, 65536, 98304, 131072,..lots of numbers here 428933120, 428965888, 428998656, 429031424, 429064192, 429096960, 429129728, 429162496, 429195264, 429228032, 429260800, 429293568, 429326336 Journal size 8192 (blocks 18-8210 of file /dev/sdd1) Root block 8211 Hash function r5 ATTENTION: YOU SHOULD REBOOT AFTER FDISK! (y/n) ALL DATA WILL BE LOST ON '/dev/sdd1'! y Initializing journal -
