[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <52C81C33.2030300@fastmail.fm>
Date: Sat, 04 Jan 2014 15:35:31 +0100
From: Bernd Schubert <bernd.schubert@...tmail.fm>
To: Ritesh Khadgaray <khadgaray@...il.com>
CC: Theodore Ts'o <tytso@....edu>, linux-ext4@...r.kernel.org,
Andreas Dilger <adilger.kernel@...ger.ca>
Subject: Re: ext4 goes into read only mode on using discard with htree_dirblock_to_tree
... bad entry in directory
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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists