From: Eric Sandeen <sandeen@sandeen.net>
To: RUMI Szabolcs <rumi_ml@rtfm.hu>
Cc: xfs@oss.sgi.com
Subject: Re: Structure needs cleaning? (take #2)
Date: Wed, 02 Sep 2009 14:53:04 -0500 [thread overview]
Message-ID: <4A9ECD20.9090201@sandeen.net> (raw)
In-Reply-To: <20090902213441.470b439c.rumi_ml@rtfm.hu>
RUMI Szabolcs wrote:
> Hi!
>
> Well, what could be the reason? I mean, there was no hardware failure,
> no crash, no reboot, no errors in the disk's SMART error log, no nothing.
> What I did was that I've extracted and deleted the rather huge OpenOffice
> source tree several times (sometimes with overwriting) and finally it
> ended up with these undeletable files and xfs errors. Is it considered
> normal for xfs to get messed up like that under such load?
No, not normal.
It found the text "0xAAAA0000,6,0x" on disk in an area where it expected
to find valid filesystem metadata.
Corruption could come from anywhere - an xfs bug, some other bug, bad
memory, bad cables, neon death rays from space, writing directly to the
disk, who knows. Awfully hard to track down a one-off occurrence like
this, I'm afraid.
> Thanks,
> Sab
>
>
>
> The xfs_repair output and xfs_info output is included below:
>
> # xfs_repair -v /dev/sda10
...
> Phase 6 - check inode connectivity...
> - resetting contents of realtime bitmap and summary inodes
> - traversing filesystem ...
> - agno = 0
> - agno = 1
> - agno = 2
> - agno = 3
> - agno = 4
> - agno = 5
> - agno = 6
> - agno = 7
> leaf block 8388608 for directory inode 4051737 bad header
> rebuilding directory inode 4051737
> leaf block 8388608 for directory inode 4053318 bad header
> rebuilding directory inode 4053318
...
above is the problem, properly found & repaired.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-09-02 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 13:22 Structure needs cleaning? (take #2) RUMI Szabolcs
2009-09-02 14:31 ` Eric Sandeen
2009-09-02 19:34 ` RUMI Szabolcs
2009-09-02 19:53 ` Eric Sandeen [this message]
2009-09-02 21:02 ` Justin Piszcz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A9ECD20.9090201@sandeen.net \
--to=sandeen@sandeen.net \
--cc=rumi_ml@rtfm.hu \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox