On Thu, May 12, 2005 at 11:28:37AM +0900, Kenji Wakamiya wrote: > By the way, sometimes I get warnings from gfs_fsck for snapshot-LV, > even though I froze GFS before doing lvcreate -s. > For example, the followings are. Is this usual thing? > > # gfs_fsck -y /dev/vg0/lv0ss0 > Initializing fsck > Starting pass1 > Pass1 complete > Starting pass1b > Pass1b complete > Starting pass1c > Pass1c complete > Starting pass2 > Pass2 complete > Starting pass3 > Pass3 complete > Starting pass4 > Found unlinked inode at 1929233 > Adjusting freemeta block count (59 -> 60). > Adjusting used dinode block count (10 -> 9). > l+f directory at 29 > Added inode #1929233 to l+f dir > Found unlinked inode at 1800635 > Added inode #1800635 to l+f dir > Link count inconsistent for inode 25 - 5 6 > Link count updated for inode 25 > Pass4 complete > Starting pass5 > ondisk and fsck bitmaps differ at block 29 > Succeeded. > used inode count inconsistent: is 9 should be 10 > free meta count inconsistent: is 60 should be 59 > Pass5 complete > # Interesting. Have you noticed what inode gets stuck in l+f? -- AJ Lewis Voice: 612-638-0500 Red Hat Inc. E-Mail: alewis@xxxxxxxxxx 720 Washington Ave. SE, Suite 200 Minneapolis, MN 55414 Current GPG fingerprint = D9F8 EDCE 4242 855F A03D 9B63 F50C 54A8 578C 8715 Grab the key at: http://people.redhat.com/alewis/gpg.html or one of the many keyservers out there...
Attachment:
pgpBqNOiCpoP2.pgp
Description: PGP signature
-- Linux-cluster@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/linux-cluster
