From: Eric Sandeen <sandeen@sandeen.net>
To: xfs@oss.sgi.com
Subject: Re: Metadata corruption
Date: Mon, 13 Jun 2016 10:49:02 -0500 [thread overview]
Message-ID: <eac741bb-72d4-8f73-1d7d-2db456768fe9@sandeen.net> (raw)
In-Reply-To: <20160613112738.GA4730@bfoster.bfoster>
On 6/13/16 6:27 AM, Brian Foster wrote:
> On Mon, Jun 13, 2016 at 09:27:57AM +0300, Martin Aleksov wrote:
>> HiThere,
>>
>> I'm using XFS on Arch linux.Each 2 days I'm receiving this error:
>>
>>
>> Metadata corruption detected at xfs_inode block 0x5bd20/0x8000
>>
>> while doing this:
>>
>>
>> [martin@marto ~]$ sudo xfs_db -c frag -r /dev/sda2
>
> sda2 is your root filesystem.. so I assume the filesystem is mounted
> when you run this? If so, this type of thing could be expected. Do you
> see errors in the logs otherwise? If not, I'd suggest to repeat this
> from a ramdisk or boot/recovery disk where the filesystem isn't mounted
> to confirm.
That's probably it. In addition, I would suggest not
running the frag command, as it is largely useless:
http://xfs.org/index.php/XFS_FAQ#Q:_The_xfs_db_.22frag.22_command_says_I.27m_over_50.25._Is_that_bad.3F
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-06-13 15:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 6:27 Metadata corruption Martin Aleksov
2016-06-13 6:41 ` Martin Aleksov
2016-06-13 6:45 ` Stefan Ring
2016-06-13 11:27 ` Brian Foster
2016-06-13 15:49 ` Eric Sandeen [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-25 11:33 Nickolay Novikov
2017-12-26 19:34 ` Eric Sandeen
2017-12-27 8:42 ` Nickolay Novikov
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=eac741bb-72d4-8f73-1d7d-2db456768fe9@sandeen.net \
--to=sandeen@sandeen.net \
--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