Re: Problems with nodatacow/nodatasum

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxx> wrote:
> > On Fri, Apr 20, 2012 at 11:19:39AM +0300, Avi Kivity wrote:
> >>   /dev/mapper/luks-blah /                       btrfs
> >> subvol=/rootvol        1 1
> >>   /dev/mapper/luks-blah /var/lib/libvirt/images     btrfs
> >> nodatasum,nodatacow,subvol=/images.libvirt        1 2
> >
> > what does /proc/mounts say about the applied options? do you see
> > nodatasum and nodatacow there? afaik most (if not all) mount options
> > affect the whole filesystem including any subvolume mounts.  having
> > per-subvol options is possible, just not implemented.
> >
> 
> Nothing, the options don't show up there.
> 
> 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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux