Re: [Cooker] !File system corruption!

2001-03-20 Thread Chmouel Boudjnah

Con Kolivas [EMAIL PROTECTED] writes:

 Youch!
 
 While copying the latest RPMS from cooker the machine hung. And I mean
 really hung - raw key input was the only way to reboot. Since then I
 have had strange responses from the RPMS directory. The partition is
 reiserfs with notail and the first time I access the directory with ls
 I get:
 
 is_tree_node: node level 50293 does not match the expected one 1
 vs-5150: search_by_key: invalid format found in block 558586: Fsck?
 vs-13070: reiserfs_read_inode2: i/o failure occured trying to find
 stat data of [6615 21746 0x0 SD] 

what /sbin/reiserfsck say ?

-- 
MandrakeSoft Inc http://www.chmouel.org
  --Chmouel




Re: Re: [Cooker] !File system corruption!

2001-03-20 Thread Con Kolivas

Original message from: Chmouel Boudjnah [EMAIL PROTECTED]
 is_tree_node: node level 50293 does not match the expected one 1
 vs-5150: search_by_key: invalid format found in block 558586: Fsck?
 vs-13070: reiserfs_read_inode2: i/o failure occured trying to find
 stat data of [6615 21746 0x0 SD] 

what /sbin/reiserfsck say ?

It went through a normal log recovery and then lists a number of bad
inodes and seems to be correcting them then segfaults when it gets to
558586.

A tree rebuild fixed the corruption as you'll see in another post.

Where would reiserfsck have put it's log? I'll post it here if I can
find it.


__
Get your free Australian email account at http://www.start.com.au





Re: [Cooker] !File system corruption!

2001-03-20 Thread Chmouel Boudjnah

Con Kolivas [EMAIL PROTECTED] writes:

 Original message from: Chmouel Boudjnah [EMAIL PROTECTED]
  is_tree_node: node level 50293 does not match the expected one 1
  vs-5150: search_by_key: invalid format found in block 558586: Fsck?
  vs-13070: reiserfs_read_inode2: i/o failure occured trying to find
  stat data of [6615 21746 0x0 SD] 
 
 what /sbin/reiserfsck say ?
 
 It went through a normal log recovery and then lists a number of bad
 inodes and seems to be correcting them then segfaults when it gets to
 558586.
 
 A tree rebuild fixed the corruption as you'll see in another post.
 
 Where would reiserfsck have put it's log? I'll post it here if I can
 find it.

i have forwarded to the reiserfs mailing list and let you know the
state of this issue...

-- 
MandrakeSoft Inc http://www.chmouel.org
  --Chmouel