On Wed, 2007-07-11 at 16:21 -0700, Taran Lewis wrote: > Thank you guys for the quick response: > > looks like no dice with the read only option, same error as before > > mount -oro /dev/md1 /files > mount: wrong fs type, bad option, bad superblock on /dev/md1, > missing codepage or other error > In some cases useful info is found in syslog - try > dmesg | tail or so > > Throw away the inodes? Does that mean it will get toss the problem data out > and recover the rest?
Yes, assuming that it doesn't find further errors. Since fsck.jfs aborted after reporting the bad inodes, we don't know what further damage it will come across. > > What units is the error message in, blocks or sectors of the drive? > Bytes of data? If I can do my math right, there are 31 bad ones which > makes like 0.0000043% so maybe I wouldn't even lose that much? It was > a 500 GB partition with about 300 GB on it. I think it's inodes, so you'd lose 32 inodes. Not too bad, IF that's all that it finds. > > The jfsrec sounds pretty promising too. I'm thinking that I should > run that first and then the fsck -f? I'm planning on making a dd image > and mount -o loop 'ing it so I don't mess up my original partition. I'm not familiar with jfsrec, but I would give it a try if I were you. > Thanks again for your help. > > P.S. I wasn't sure how to reply to the same thread, so I apologize if this > starts a new one. Shaggy -- David Kleikamp IBM Linux Technology Center ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
