On Mon, 2006-08-07 at 19:51 +0300, Lasse Hynninen wrote: > jfs_fsck -d -v /dev/md0: > > jfs_fsck version 1.1.11, 05-Jun-2006 > processing started: 8/7/2006 22:44:43 > ... > ... > **Phase 0 - Replay Journal Log [xchkdsk.c:1864] > LOGREDO: Log already redone! [logredo.c:555] > logredo returned rc = 0 [xchkdsk.c:1896] > **Phase 1 - Check Blocks, Files/Directories, and Directory Entries > [xchkdsk.c:1989] > processing terminated: 8/7/2006 22:44:43 with return code: 10053 > exit code: 8. [xchkdsk.c:468] > > Well.. return code changed from 10052 to 10053 :)
Can't read the root directory inode. There still seems to be some major damage to this file system. I'm not sure that anything can be done to get fsck to fix it from the current state. -- David Kleikamp IBM Linux Technology Center ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Jfs-discussion mailing list Jfs-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jfs-discussion
