From: Goffredo Baroncelli <kreijack@inwind.it>
To: Konstantinos Skarlatos <k.skarlatos@gmail.com>,
Lennart Poettering <lennart@poettering.net>,
Josef Bacik <jbacik@fb.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: price to pay for nocow file bit?
Date: Thu, 08 Jan 2015 19:48:33 +0100 [thread overview]
Message-ID: <54AED101.6060701@inwind.it> (raw)
In-Reply-To: <54AECB72.9@gmail.com>
On 2015-01-08 19:24, Konstantinos Skarlatos wrote:
>> Anyway, given the pros and cons I have now changed journald to set
>> the nocow bit on newly created journal files. When files are
>> rotated (and we hence know we will never ever write again to them)
>> the bit is tried to be unset again, and a defrag ioctl will be
>> invoked right after. btrfs currently silently ignores that we unset
>> the bit, and leaves it set, but I figure i should try to unset it
>> anyway, in case it learns that one day. After all, after rotating
>> the files there's no reason to treat the files special anymore...
> Can this behaviour be optional? I dont mind some fragmentation if i
> can keep having checksums and the ability for raid 1 to repair those
> files.
I agree with Konstantinos's request: please let this behavior optional.
BR
G.Baroncelli
--
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2015-01-08 18:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 17:43 price to pay for nocow file bit? Lennart Poettering
2015-01-07 20:10 ` Josef Bacik
2015-01-07 21:05 ` Goffredo Baroncelli
2015-01-07 22:06 ` Josef Bacik
2015-01-08 6:30 ` Duncan
2015-01-10 12:00 ` Martin Steigerwald
2015-01-10 12:23 ` Martin Steigerwald
2015-01-08 8:24 ` Chris Murphy
2015-01-08 8:35 ` Koen Kooi
2015-01-08 13:30 ` Lennart Poettering
2015-01-08 18:24 ` Konstantinos Skarlatos
2015-01-08 18:48 ` Goffredo Baroncelli [this message]
2015-01-09 15:52 ` David Sterba
2015-01-10 10:30 ` Martin Steigerwald
2015-01-11 20:39 ` Chris Murphy
2015-01-08 15:56 ` Zygo Blaxell
2015-01-08 16:53 ` Lennart Poettering
2015-01-08 18:36 ` Zygo Blaxell
2015-01-09 15:41 ` David Sterba
2015-01-09 16:14 ` Zygo Blaxell
2015-01-08 20:42 ` Roger Binns
2015-01-15 19:06 ` Chris Mason
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=54AED101.6060701@inwind.it \
--to=kreijack@inwind.it \
--cc=jbacik@fb.com \
--cc=k.skarlatos@gmail.com \
--cc=lennart@poettering.net \
--cc=linux-btrfs@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).