From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Mason Subject: Re: Problems with nodatacow/nodatasum Date: Fri, 20 Apr 2012 20:15:51 -0400 Message-ID: <20120421001551.GL30599@shiny> References: <20120420091250.GK20982@twin.jikos.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Cc: dave@jikos.cz, linux-btrfs@vger.kernel.org To: Avi Kivity Return-path: In-Reply-To: List-ID: On Fri, Apr 20, 2012 at 12:22:11PM +0300, Avi Kivity wrote: > On Fri, Apr 20, 2012 at 12:12 PM, David Sterba 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