If fsck completed successfully, then o2image is not required. On 02/21/2011 08:24 AM, Werner Flamme wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Werner Flamme [21.02.2011 16:01]: > > Sunil, > > finally, fsck.ocfs2 finished. The size of the protocol is 8404218 bytes, > and in my mind I do not see "bad" errors, only "mis-allocations" as they > may turn up with any other fsck too. > > Here's the last line of log entries: > > - ---snip--- > [DIRENT_LENGTH] Directory inode 161569267 corrupted in logical block 1 > physical block 28559137 offset 0. Attempt to repair this block's > directory entries? n > o2fsck_type_from_dinode: Bad magic number in inode while reading inode > 14034875 to discover its file type > pass2: Bad magic number in inode while trying to verify the file type of > directory entry pcieaer > Pass 3: Checking directory connectivity. > [DIR_NOT_CONNECTED] Directory inode 14034904 isn't connected to the > filesystem. Move it to lost+found? n > ... > [DIR_NOT_CONNECTED] Directory inode 14034880 isn't connected to the > filesystem. Move it to lost+found? n > [DIR_DOTDOT] Directory inode 14034880 is referenced by a dirent in > directory 0 but its '..' entry points to inode 14034513. Fix the '..' > entry to reference 0? n > [DIR_NOT_CONNECTED] Directory inode 14034881 isn't connected to the > filesystem. Move it to lost+found? n > ... > [DIR_DOTDOT] Directory inode 26609174 is referenced by a dirent in > directory 0 but its '..' entry points to inode 14034876. Fix the '..' > entry to reference 0? n > Pass 4a: checking for orphaned inodes > Pass 4b: Checking inodes link counts. > pass4: Internal logic faliure fsck's thinks inode 62 has a link count of > 0 but on disk it is 1 > [INODE_COUNT] Inode 62 has a link count of 0 on disk but directory entry > references come to 1. Update the count on disk to match? n > [INODE_COUNT] Inode 14034513 has a link count of 546 on disk but > directory entry references come to 541. Update the count on disk to match? n > ... > [INODE_COUNT] Inode 111024331 has a link count of 11 on disk but > directory entry references come to 10. Update the count on disk to match? n > pass4: Internal logic faliure fsck's thinks inode 123478148 has a link > count of 0 but on disk it is 1 > [INODE_COUNT] Inode 123478148 has a link count of 0 on disk but > directory entry references come to 57. Update the count on disk to match? n > pass4: Internal logic faliure fsck's thinks inode 123484242 has a link > count of 0 but on disk it is 1 > [INODE_COUNT] Inode 123484242 has a link count of 0 on disk but > directory entry references come to 57. Update the count on disk to match? n > All passes succeeded. > - ---pins--- > > So, there may be some data loss, but in the whole, the disk will remain > useable when I use "fsck.ocfs2 -fy /dev/sdf"? With several new entries > in /lost+found, I think... > > And again, I will send an o2image, but what filesize do I have to expect > with 183,500,800 clusters (and blocks)? > > Regards, > Werner > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.15 (GNU/Linux) > Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk1ikdoACgkQk33Krq8b42OW9QCfQBoQQ1IRlevyGIuz27d4qqi3 > BhUAn0qmCG22EknD5bnDbKTaNVGmKmsh > =MX8b > -----END PGP SIGNATURE----- > > _______________________________________________ > Ocfs2-users mailing list > Ocfs2-users@oss.oracle.com > http://oss.oracle.com/mailman/listinfo/ocfs2-users
_______________________________________________ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users