From: Chris Murphy <lists@colorremedies.com>
To: Christian <cdysthe@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: trim not working and irreparable errors from btrfsck
Date: Tue, 16 Jun 2015 15:14:54 -0600 [thread overview]
Message-ID: <CAJCQCtQGzwQ=L4Vh19tsqSqPoPJuNaLyTo7q0SsbMteb2=tdMw@mail.gmail.com> (raw)
In-Reply-To: <mlpb8i$dus$1@ger.gmane.org>
I experienced the errors 400 problem on an HDD and how I fixed it is
in comment 2 in this bug:
https://bugzilla.kernel.org/show_bug.cgi?id=90071
The gist is to find out what file is affected by finding the
path/filename for the inode with the error and then deleting it.
You'll need to recover the file from backups. Once you do this the
problem is resolved, the file system itself is OK. (At least it was in
my case.)
I don't know that the source of the problem you're having has anything
to do with trim, but I recommend not using discard or fstrim at all
until you isolate what's causing it. There are some trim bugs that
have been fixed in newer kernels that sound like the problem you're
having; and there are definitely some SSDs out there with trim
problems where the wrong sectors get trimmed. It shows up as files
with 512 byte holes of zeros in them. Of course, that's when the bug
affects data. If it affects metadata it can obliterate the file system
beyond repair.
Chris Murphy
next prev parent reply other threads:[~2015-06-16 21:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 14:18 trim not working and irreparable errors from btrfsck Christian
2015-06-16 21:14 ` Chris Murphy [this message]
[not found] ` <55816E7B.5040905@gmail.com>
2015-06-17 14:22 ` Chris Murphy
2015-06-17 14:33 ` Christian
2015-06-17 15:28 ` Chris Murphy
2015-06-17 15:40 ` Christian
2015-06-17 17:17 ` Austin S Hemmelgarn
2015-06-18 5:25 ` Duncan
2015-08-14 15:11 ` Jeff Mahoney
2015-06-20 14:11 ` Lutz Euler
2015-06-21 7:21 ` Paul Jones
2015-08-13 9:23 ` Marc Joliet
2015-08-13 23:14 ` Chris Murphy
2015-08-14 8:05 ` Marc Joliet
2015-08-14 8:15 ` Marc Joliet
2015-08-14 10:51 ` Paul Jones
2015-06-18 2:20 ` Paul Jones
2015-06-18 4:15 ` Chris Murphy
2015-06-18 4:19 ` 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='CAJCQCtQGzwQ=L4Vh19tsqSqPoPJuNaLyTo7q0SsbMteb2=tdMw@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=cdysthe@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.