public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
* XFS failure
@ 2006-07-17  0:15 Michel
  2006-07-17  8:41 ` Martin Steigerwald
  0 siblings, 1 reply; 2+ messages in thread
From: Michel @ 2006-07-17  0:15 UTC (permalink / raw)
  To: xfs

Hello dear developer,

almost every week on checking my fs i get
*
livecd root # xfs_check /dev/sda3
bad free block nused 2 should be 8 for dir ino 220115 block 16777216
bad free block nused 0 should be 6 for dir ino 34171444 block 16777216
bad free block nvalid/nused 5/-1 for dir ino 35644249 block 16777216
missing free index for data block 0 in dir ino 35644249
missing free index for data block 1 in dir ino 35644249
missing free index for data block 2 in dir ino 35644249
missing free index for data block 3 in dir ino 35644249
missing free index for data block 4 in dir ino 35644249*


when i run xfs_repair ... here is the output

*livecd / # xfs_repair /dev/sda3
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan and clear agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - clear lost+found (if it exists) ...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
Phase 5 - rebuild AG headers and trees...
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - ensuring existence of lost+found directory
        - traversing filesystem starting at / ...
free block 16777216 for directory inode 35644249 bad nused
rebuilding directory inode 35644249
free block 16777216 for directory inode 34171444 bad nused
rebuilding directory inode 34171444
free block 16777216 for directory inode 220115 bad nused
rebuilding directory inode 220115
        - traversal finished ...
        - traversing all unattached subtrees ...
        - traversals finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...
done*


After repairing, xfs_check reports no more errors. I always unmounting
my devices cleanly ... and i never had any power failure! But every week
i get the same errors. My HDD is 1 month old and i already tested it for
bad sectors.

Regards

Michel


[[HTML alternate version deleted]]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: XFS failure
  2006-07-17  0:15 XFS failure Michel
@ 2006-07-17  8:41 ` Martin Steigerwald
  0 siblings, 0 replies; 2+ messages in thread
From: Martin Steigerwald @ 2006-07-17  8:41 UTC (permalink / raw)
  To: linux-xfs

Am Montag 17 Juli 2006 02:15 schrieb Michel:
> Hello dear developer,
>
> almost every week on checking my fs i get

Hello,

known and already fixed bug, see:

http://bugzilla.kernel.org/show_bug.cgi?id=6757

You need to apply this patch to get it fixed:

http://bugzilla.kernel.org/show_bug.cgi?id=6757#c8

Regards,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2006-07-17  8:41 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-07-17  0:15 XFS failure Michel
2006-07-17  8:41 ` Martin Steigerwald

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox