public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Peterson <lavajoe@gentoo.org>
To: jim owens <jowens@hp.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] COW and checksumming ioctls
Date: Fri, 20 Jun 2008 23:59:03 -0600	[thread overview]
Message-ID: <485C98A7.6090608@gentoo.org> (raw)
In-Reply-To: <485C0899.1080203@hp.com>

jim owens wrote:
> As I think someone already said (or hinted), a feature-lockout
> can be designed so the admnin can do that on some "set" for
> those who are paranoid.

That would be a nice feature.  Maybe even a mount option could be
available to "disable the disabling" of checksumming/COW for cases in
which the admin decides users should not be changing these attributes
for a particular filesystem.

> Again for those who are paranoid, making these auditable events
> (I'm probably not using the right linux term) solves the need
> to know something like checksum-off has occured.

Yes, that reminds me of ZFS's logging facility, in which case an admin
can check to see all operations ever done to the filesystem.  When
someone is managing a bunch of computers and/or filesystems (making it
easy to get forgetful), it is always nice to be able to go back and ask
the system what admin options were used as a sanity check.  I think
that's a cool idea.

						-Joe

  reply	other threads:[~2008-06-21  5:59 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
2008-06-20 19:44         ` jim owens
2008-06-21  5:59           ` Joe Peterson [this message]
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=485C98A7.6090608@gentoo.org \
    --to=lavajoe@gentoo.org \
    --cc=jowens@hp.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