From: Bernd Schubert <bernd.schubert@fastmail.fm>
To: Ritesh Khadgaray <khadgaray@gmail.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
linux-ext4@vger.kernel.org,
Andreas Dilger <adilger.kernel@dilger.ca>
Subject: Re: ext4 goes into read only mode on using discard with htree_dirblock_to_tree ... bad entry in directory
Date: Sat, 04 Jan 2014 15:35:31 +0100 [thread overview]
Message-ID: <52C81C33.2030300@fastmail.fm> (raw)
In-Reply-To: <20140102185507.GD10870@thunk.org>
On 01/02/2014 07:55 PM, Theodore Ts'o wrote:
> On Thu, Jan 02, 2014 at 10:49:56AM +0530, Ritesh Khadgaray wrote:
>
> However, in your case, if discard commands are causing on-disk
> corruption, I'm not sure I can even in good conscience recommend using
> fstrim.
>
>> Device Model: Crucial_CT960M500SSD1
>> Serial Number: 1335094BE7CA
>> LU WWN Device Id: 5 00a075 1094be7ca
>> Firmware Version: MU03
>
If this is not a production system you can try to switch to another
provisioning mode. I.e. Intel510 drives cause data corruption with
write-same-10, but unmap works fine.
cat /sys/class/scsi_disk/H\:C\:I\:L/provisioning_mode
and
echo -n {writesame_16,unmap} > /sys/class/scsi_disk/H\:C\:I\:L/provisioning_mode
(lsscsi can provide the H:C:I:L tuplet)
Cheers,
Bernd
next prev parent reply other threads:[~2014-01-04 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHy4Ox1fjTbOxiTqcqyhihYkRs2po7Xs4EWxsFVP+HHyJWpSfg@mail.gmail.com>
2014-01-02 18:55 ` ext4 goes into read only mode on using discard with htree_dirblock_to_tree ... bad entry in directory Theodore Ts'o
2014-01-04 14:35 ` Bernd Schubert [this message]
2014-01-02 5:23 Ritesh Khadgaray
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=52C81C33.2030300@fastmail.fm \
--to=bernd.schubert@fastmail.fm \
--cc=adilger.kernel@dilger.ca \
--cc=khadgaray@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).