From: Eric Sandeen <sandeen@sandeen.net>
To: michael.arndt@berlin.de, linux-xfs@vger.kernel.org
Subject: Re: xfs fstrim and quota
Date: Tue, 24 Apr 2018 10:10:27 -0600 [thread overview]
Message-ID: <30bb656c-b2d8-303e-344e-a1de6698c4d1@sandeen.net> (raw)
In-Reply-To: <483b7b2c592450221bb5567e64bad84e@berlin.de>
On 4/24/18 2:28 AM, michael.arndt@berlin.de wrote:
> Hello *
>
> Will fstrim operations for a thin provisioning storage and xfs quota conflict with each other ?
>
> If i understand fstrim code correctly, in case of xfs / thin provisioning storage it tells xfs to release unused blocks.
>
> I have read indications that blocks are marked to the underlying storage as freed by zeroing them out.
Brian addressed most of this, I think, but the short answer is that no, fstrim
will in no way affect xfs quota. Everything happening as a result of fstrim
happens well below what the quota subsystem even knows about. Even if discard
happens via WRITE_SAME, that's not anything quota is aware of.
Short answer is: There is no conflict.
Thanks,
-Eric
> Is the "write zeros" correct information, or will be commands like scsi unmap or FITRIM be sent to the storage ?
>
> I found many exact references to fstrim on SSD, but no technical description on which operation is implemented for thin provisioning storages.
>
> TIA
> Micha
prev parent reply other threads:[~2018-04-24 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c3cbf69c52f0e89631c796016449bbe3@berlin.de>
2018-04-24 8:28 ` xfs fstrim and quota michael.arndt
2018-04-24 11:35 ` Brian Foster
2018-11-14 10:51 ` xfs remove / unlink extremely slow ? Michael Arndt
2018-04-24 16:10 ` Eric Sandeen [this message]
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=30bb656c-b2d8-303e-344e-a1de6698c4d1@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linux-xfs@vger.kernel.org \
--cc=michael.arndt@berlin.de \
/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).