From: Chris Mason <chris.mason@oracle.com>
To: Avi Kivity <avi.kivity@gmail.com>
Cc: dave@jikos.cz, linux-btrfs@vger.kernel.org
Subject: Re: Problems with nodatacow/nodatasum
Date: Fri, 20 Apr 2012 20:15:51 -0400 [thread overview]
Message-ID: <20120421001551.GL30599@shiny> (raw)
In-Reply-To: <CAEbWaiqfh9KBM5U0QtqULHwLed854MeY=cPSxWRhoEGND9ve0A@mail.gmail.com>
On Fri, Apr 20, 2012 at 12:22:11PM +0300, Avi Kivity wrote:
> On Fri, Apr 20, 2012 at 12:12 PM, David Sterba <dave@jikos.cz> wrote:
> > On Fri, Apr 20, 2012 at 11:19:39AM +0300, Avi Kivity wrote:
> >> =A0 /dev/mapper/luks-blah / =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
=A0 btrfs
> >> subvol=3D/rootvol =A0 =A0 =A0 =A01 1
> >> =A0 /dev/mapper/luks-blah /var/lib/libvirt/images =A0 =A0 btrfs
> >> nodatasum,nodatacow,subvol=3D/images.libvirt =A0 =A0 =A0 =A01 2
> >
> > what does /proc/mounts say about the applied options? do you see
> > nodatasum and nodatacow there? afaik most (if not all) mount option=
s
> > affect the whole filesystem including any subvolume mounts. =A0havi=
ng
> > per-subvol options is possible, just not implemented.
> >
>=20
> Nothing, the options don't show up there.
>=20
> Are there plans to allow per-subvolume nodatasum/nodatacow?
It can be set on a per file basis, let me push out a commit to btrfs
progs with ioctls to set it.
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-04-21 0:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 8:19 Problems with nodatacow/nodatasum Avi Kivity
2012-04-20 9:12 ` David Sterba
2012-04-20 9:22 ` Avi Kivity
2012-04-21 0:15 ` Chris Mason [this message]
2012-05-13 17:51 ` Avi Kivity
2012-05-15 22:12 ` David Sterba
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=20120421001551.GL30599@shiny \
--to=chris.mason@oracle.com \
--cc=avi.kivity@gmail.com \
--cc=dave@jikos.cz \
--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).