On Mon, 2002-02-11 at 21:36, Oki DZ wrote: > Hi, > > I had the following from dmesg: > vs-13042: reiserfs_read_inode2: [4148 16361 0x0 SD] not found > vs-13048: reiserfs_iget: bad_inode. Stat data of (4148 16361) not found > vs-13048: reiserfs_iget: bad_inode. Stat data of (4148 16361) not found > vs-13048: reiserfs_iget: bad_inode. Stat data of (4148 16361) not found > > What should I do? > reiserfsck? > badblocks and feed the output into mkreiserfs? (please, not this one) > > bdg:~# dmesg | grep reiser > reiserfs: checking transaction log (device 08:01) ... > reiserfs: using 3.5.x disk format > bdg:~# uname -a > Linux bdg 2.4.4 #6 Wed May 30 08:30:57 JAVT 2001 i686 unknown
Best advice would come from the reiserfs mailing list: http://www.namesys.com/mailinglist.html I have had good success with reiserfsck. If it's your boot partition you will need to static compile reiserfsck so you can run it from a floppy. You should not still be using 2.4.4 if you're using ReiserFS. A multitude of bugs have been fixed since then. A number of bugs are still being fixed in the 2.4.17-pre series so upgrade to 2.4.18 when it comes out. This search of the mailing list archive might also help: http://marc.theaimsgroup.com/?l=reiserfs&w=2&r=1&s=reiserfs+iget%3A+bad+inode&q=t Regards, Adam
