Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Holger Kiehl <Holger.Kiehl@dwd.de>
To: Christian Balzer <chibi@gol.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID5 TRIM/DISCARD user land support (fstriim and mkfs)
Date: Mon, 10 Aug 2015 08:28:39 +0000 (UTC)	[thread overview]
Message-ID: <alpine.LRH.2.20.1508100824290.8849@diagnostix.dwd.de> (raw)
In-Reply-To: <20150810164657.75bae079@batzmaru.gol.ad.jp>

Hello,

On Mon, 10 Aug 2015, Christian Balzer wrote:

>
> Hello,
>
> Debian system, tested both Wheezy and Jessie, thus 3.16 kernel with
> backports.
>
> 8 SSD RAID5, of course with raid456.devices_handle_discard_safely set to 1.
> I can re-mount it with discard w/o a problem:
> ---
> EXT4-fs (md4): re-mounted. Opts: stripe=112,data=ordered,discard
> ---
>
> However fstrim whines about "FITRIM ioctl failed: Operation not supported"
> and mkfs.ext4 unsurprisingly doesn't discard things when invoked.
>
> The same HW/OS combo works fine with RAID10.
>
> When looking at the sysfs entries for that MD device the fact
> that /sys/class/block/md4/queue/discard_zeroes_data is 0 doesn't instill
> me with hope or confidence
>
> Now while the SSDs in question (Intel DC S3610s) don't really need TRIM
> really would have liked them to be able to start with a clean slate so to
> speak.
>
> Any insights?
>
Discard for raid456 has been disabled by default because some devices in
some cases don't do what it says on the label.

You can enable it by setting the module parameter

    raid456.devices_handle_discard_safely=Y

Ensure that your drives can handle discard safely.

Regards,
Holger

  reply	other threads:[~2015-08-10  8:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10  7:46 RAID5 TRIM/DISCARD user land support (fstriim and mkfs) Christian Balzer
2015-08-10  8:28 ` Holger Kiehl [this message]
2015-08-10  8:53   ` Christian Balzer
2015-08-10  8:59     ` Holger Kiehl
2015-08-11  5:20 ` Christian Balzer

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=alpine.LRH.2.20.1508100824290.8849@diagnostix.dwd.de \
    --to=holger.kiehl@dwd.de \
    --cc=chibi@gol.com \
    --cc=linux-raid@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