From: Christoph Hellwig <hch@infradead.org>
To: Adam Borowski <kilobyte@angband.pl>
Cc: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>,
Marat Khalili <mkh@rqc.ru>, Duncan <1i5t5.duncan@cox.net>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: qemu-kvm VM died during partial raid1 problems of btrfs
Date: Tue, 12 Sep 2017 11:47:49 -0700 [thread overview]
Message-ID: <20170912184749.GA4359@infradead.org> (raw)
In-Reply-To: <20170912184359.hovirdaj55isvwwg@angband.pl>
On Tue, Sep 12, 2017 at 08:43:59PM +0200, Adam Borowski wrote:
> For now, though, I wonder -- should we send fine folks at util-linux a patch
> to make fallocate -d restore mtime, either always or on an option?
Don't do that. Please just add a new ioctl or fallocate command
that punches a hole if the range is zeroed, similar to what dedup
does. It can probably even reuse a few helpers.
next prev parent reply other threads:[~2017-09-12 18:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 8:02 qemu-kvm VM died during partial raid1 problems of btrfs Marat Khalili
2017-09-12 8:25 ` Timofey Titovets
2017-09-12 8:42 ` Marat Khalili
2017-09-12 9:21 ` Timofey Titovets
2017-09-12 9:29 ` Marat Khalili
2017-09-12 9:35 ` Timofey Titovets
2017-09-12 10:01 ` Duncan
2017-09-12 10:32 ` Adam Borowski
2017-09-12 10:39 ` Marat Khalili
2017-09-12 11:01 ` Timofey Titovets
2017-09-12 11:12 ` Adam Borowski
2017-09-12 11:17 ` Timofey Titovets
2017-09-12 11:26 ` Marat Khalili
2017-09-12 17:21 ` Adam Borowski
2017-09-12 17:36 ` Austin S. Hemmelgarn
2017-09-12 18:43 ` Adam Borowski
2017-09-12 18:47 ` Christoph Hellwig [this message]
2017-09-12 19:12 ` Austin S. Hemmelgarn
2017-09-12 19:11 ` Austin S. Hemmelgarn
2017-09-12 20:00 ` Adam Borowski
2017-09-12 20:12 ` Austin S. Hemmelgarn
2017-09-12 21:13 ` Adam Borowski
2017-09-13 0:52 ` Timofey Titovets
2017-09-13 12:55 ` Austin S. Hemmelgarn
2017-09-13 12:21 ` Austin S. Hemmelgarn
2017-09-18 11:53 ` Adam Borowski
2017-09-13 14:47 ` Martin Raiber
2017-09-13 15:25 ` Austin S. Hemmelgarn
2017-09-12 11:09 ` Roman Mamedov
2017-09-13 13:23 ` Chris Murphy
2017-09-13 14:15 ` Marat Khalili
2017-09-13 17:52 ` Goffredo Baroncelli
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=20170912184749.GA4359@infradead.org \
--to=hch@infradead.org \
--cc=1i5t5.duncan@cox.net \
--cc=ahferroin7@gmail.com \
--cc=kilobyte@angband.pl \
--cc=linux-btrfs@vger.kernel.org \
--cc=mkh@rqc.ru \
/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).