On Thu, Jan 16, 2020 at 04:44:18PM -0800, Michael Ruiz wrote: > My solution was to boot into an arch live usb, unlock my dmcrypt partition and > mount the btrfs partition to /mnt. After that I created a subvolume on the @ > directory (top level 5) instead of a subvolume of my root (/) partition. > So now my subvolume layout is like this: > > ID 256 gen 45343 top level 5 path @ > ID 257 gen 45346 top level 5 path @home > ID 258 gen 45346 top level 5 path @log > ID 259 gen 44303 top level 5 path @srv > ID 260 gen 44650 top level 5 path @pkg > ID 261 gen 45346 top level 5 path @tmp > ID 1607 gen 43963 top level 5 path @swap > > The strange thing to me is that I didn't ask for snapshots of this subvolume, > although I do keep snapshots of my / directory, I was under the impression > that snapshots would not be recursive and go into the /swap subvolume. No, snapshots are not recursive. > I can > also confirm I had the +C attribute while getting this error. So now I am able > to mount this subvolume with it's own options, whereas before I guess it > inherited options from the root dir which has CoW enabled. The problem is now > resolved by doing this. Thanks for the responses. The file attribute has precedence over the mount options, so it should not matter if you had nodatacow or not when creating the file (assuming you set the +C flag manually).
