From: Joe Peterson <lavajoe@gentoo.org>
To: Chris Mason <chris.mason@oracle.com>
Cc: Josef Bacik <jbacik@redhat.com>,
Zach Brown <zach.brown@oracle.com>, Mingming <cmm@us.ibm.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] COW and checksumming ioctls
Date: Sat, 21 Jun 2008 00:07:55 -0600 [thread overview]
Message-ID: <485C9ABB.3070709@gentoo.org> (raw)
In-Reply-To: <1213979877.10187.515.camel@think.oraclecorp.com>
Chris Mason wrote:
> But, it'll be common to mix database files with files that you do want
> checksummed in the same volume. This is an admin level decision, and we
> can easily provide knobs to turn it on/off. So, I think the ioctl is
> really important and we'll just document it as best we can.
I do see now why this ability is desirable, especially if there is a way
to see a file's checksum/COW settings (or better still, to query the
filesystem for which files have certain settings). My initial concern
was that an admin or user may not realize (or forget) a file was left in
an "unprotected" state, but yes, I'm sure there are ways to mitigate
that possibility.
-Joe
next prev parent reply other threads:[~2008-06-21 6:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 0:26 [PATCH] COW and checksumming ioctls Mingming
2008-06-20 5:23 ` Zach Brown
2008-06-20 14:01 ` Joe Peterson
2008-06-20 13:58 ` Josef Bacik
2008-06-20 15:07 ` Joe Peterson
2008-06-20 16:37 ` Chris Mason
2008-06-21 6:07 ` Joe Peterson [this message]
2008-06-20 19:44 ` jim owens
2008-06-21 5:59 ` Joe Peterson
2008-06-21 7:27 ` Christoph Hellwig
2008-06-22 14:10 ` Chris Mason
2008-06-22 18:13 ` Joshua J. Berry
2008-06-30 18:38 ` Christoph Hellwig
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=485C9ABB.3070709@gentoo.org \
--to=lavajoe@gentoo.org \
--cc=chris.mason@oracle.com \
--cc=cmm@us.ibm.com \
--cc=jbacik@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=zach.brown@oracle.com \
/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