From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] Use real FS block size in fallocate05
Date: Wed, 18 Dec 2019 05:07:35 -0500 (EST) [thread overview]
Message-ID: <461386048.17251961.1576663655809.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <4f49ce5f-188e-2e68-d99c-5fb89acc30db@suse.cz>
----- Original Message -----
> On 12/18/19 10:09 AM, Martin Doucha wrote:
> > On 12/17/19 10:02 PM, Jan Stancek wrote:
> >> Is there an upstream thread link for that btrfs bug?
> >
> > Not yet. I've reported the bug to SUSE Bugzilla for now so that our
> > kernel devs can take a closer look. But they may still decide that this
> > is expected behavior.
>
> Update: Our kernel devs just said that this is expected behavior. Btrfs
> will only release disk space when you deallocate a whole file extent
> that can be up to 128MB in size. I'll have to add an exception for Btrfs
> to fallocate05 then. Or would you guys prefer to always deallocate the
> whole file before the last write() check?
Since it's expected to work on other file systems, I'd add exception
only for btrfs.
next prev parent reply other threads:[~2019-12-18 10:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 9:36 [LTP] [PATCH 0/1] Use real FS block size in fallocate05 Martin Doucha
2019-11-28 9:36 ` [LTP] [PATCH 1/1] " Martin Doucha
2019-11-28 17:47 ` Petr Vorel
2019-11-29 9:54 ` Martin Doucha
2019-11-29 12:01 ` Jan Stancek
2019-11-29 15:25 ` Martin Doucha
2019-11-29 16:17 ` Jan Stancek
2019-12-04 10:38 ` Martin Doucha
2019-12-13 13:40 ` Cyril Hrubis
2019-12-17 13:17 ` [LTP] [PATCH v2] " Martin Doucha
2019-12-17 21:02 ` Jan Stancek
2019-12-18 9:09 ` Martin Doucha
2019-12-18 10:01 ` Martin Doucha
2019-12-18 10:07 ` Jan Stancek [this message]
2019-12-18 13:15 ` [LTP] [PATCH v3] " Martin Doucha
2020-01-02 10:01 ` Jan Stancek
2020-01-07 15:21 ` Cyril Hrubis
2020-01-07 15:50 ` Martin Doucha
2020-01-13 12:16 ` Martin Doucha
2020-01-13 13:16 ` Qu WenRuo
2020-01-13 13:25 ` Martin Doucha
2020-01-13 13:30 ` Qu WenRuo
2020-01-07 16:09 ` Martin Doucha
2020-01-07 16:29 ` Cyril Hrubis
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=461386048.17251961.1576663655809.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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