From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: How to fix/remove "csum failed ino" error
Date: Sat, 16 Nov 2013 20:54:09 +0000 (UTC) [thread overview]
Message-ID: <pan$8e6a1$4baf8046$11437360$3e14849c@cox.net> (raw)
In-Reply-To: 20131116122342.GT4315@carfax.org.uk
Hugo Mills posted on Sat, 16 Nov 2013 12:23:42 +0000 as excerpted:
> On Sat, Nov 16, 2013 at 04:06:10AM -0800, Anatol Pomozov wrote:
>> Follow-up for the issue. I stuck with this "invalid csum for free space
>> extent" error. Could anyone explain what does it mean? If this is not
>> data and just a free space, why do we care about its checksum? And if
>> we do really care then btrfs should have a way to fix this error. I can
>> "fix" a file checksum error by removing the file, but how to "fix" free
>> space extent checksum error?
>
> Probably drop the free space cache and rebuild it.
If you check the thread history (well, at least based on my
interpretation thereof, perhaps I'm wrong), he tried that. Apparently
there's a problem in the free-space cache area that appears to go away
when he drops cache, but the moment he lets it rebuild, the problem
reappears.
Almost as if there's a physical defect on the hardware itself, but the
usual automatic hardware sector relocate functionality isn't triggering
for some reason, so every time he tries to use that physical location,
which happens to be in the middle of where btrfs tries to put its space-
cache, the csum errors trigger.
I guess btrfs doesn't (yet?) work with badblocks output as ext* (and
reiserfs, which I'm personally more familiar with) does? I don't see
anything listed in the btrfs or mkfs.btrfs manpages for it, at least.
Is such support planned? One would expect it given that btrfs appears to
be the assumed successor to ext* series' default Linux filesystem title.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2013-11-16 20:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 14:42 How to fix/remove "csum failed ino" error Anatol Pomozov
2013-11-07 16:41 ` Frank Holton
2013-11-08 4:07 ` Anatol Pomozov
2013-11-08 4:55 ` Anatol Pomozov
2013-11-08 5:27 ` Frank Holton
2013-11-08 5:56 ` Chris Murphy
2013-11-08 8:13 ` Hugo Mills
2013-11-08 17:22 ` Chris Murphy
2013-11-09 2:50 ` Anatol Pomozov
2013-11-16 12:06 ` Anatol Pomozov
2013-11-16 12:23 ` Hugo Mills
2013-11-16 20:54 ` Duncan [this message]
2013-11-16 22:17 ` Chris Murphy
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='pan$8e6a1$4baf8046$11437360$3e14849c@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).