linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Remi Gauvin <remi@georgianit.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Case for "datacow-forced" option
Date: Fri, 7 Jan 2022 20:30:46 -0500	[thread overview]
Message-ID: <42e747ca-faf1-ed7c-9823-4ab333c07104@georgianit.com> (raw)

I notice some software is silently creating files with +C attribute
without user input.  (Systemd journals, libvert qcow files, etc.)... I
can appreciate the goal of a performance boost, but I can only see this
as disaster for users of btrfs RAID, which will lead to inconsistent
mirrors on unclean shutdown, (and no way to fix, other than full balance.)

I think a datacow-forced option would be a good idea to prevent
accidental creation of critical files with nocow attribute.

             reply	other threads:[~2022-01-08  1:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-08  1:30 Remi Gauvin [this message]
2022-01-09 16:37 ` Case for "datacow-forced" option Chris Murphy
2022-01-11 16:02   ` David Sterba
2022-01-11 16:01 ` David Sterba
2022-01-21  0:07   ` Zygo Blaxell

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=42e747ca-faf1-ed7c-9823-4ab333c07104@georgianit.com \
    --to=remi@georgianit.com \
    --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).