From: Christoph Hellwig <hch@infradead.org>
To: Bill McDuck <billmcdave@gmail.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Significantly longer fallocate times with Flag Unwritten Extents disabled
Date: Wed, 8 Mar 2017 07:56:02 -0800 [thread overview]
Message-ID: <20170308155602.GE4353@infradead.org> (raw)
In-Reply-To: <CAEOfVRnuTD0AWNSE+_-3KVL_xTcgrq5Q8+mm0mEQYua7gaGQiQ@mail.gmail.com>
On Mon, Mar 06, 2017 at 12:02:01PM +0000, Bill McDuck wrote:
> Hello.
>
> I have been testing the performance of XFS with "Flag Unwritten
> Extents" enabled and disabled.
Why do you disable it? It's been part of the defauly on feature
set for a decade, and manually disabling it will make you run into
completely untested code. There is a reason it's mandatory for v5
file systems.
>
> For security reasons I know XFS flags all unwritten extents by
> default, so that uninitialized disk space cannot be read by the user.
> In my application I actually want to have access to this uninitialized
> disk space. I have been modifying the superblocks using xfs_repair to
> enable this functionality.
Don't do that, it's not supported for a reason.
next prev parent reply other threads:[~2017-03-08 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 12:02 Significantly longer fallocate times with Flag Unwritten Extents disabled Bill McDuck
2017-03-06 13:05 ` Brian Foster
2017-03-08 15:56 ` Christoph Hellwig [this message]
2017-03-08 16:48 ` Bill
2017-03-08 21:50 ` Dave Chinner
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=20170308155602.GE4353@infradead.org \
--to=hch@infradead.org \
--cc=billmcdave@gmail.com \
--cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).