What's the status? This message gave me an idea: http://www.spinics.net/lists/linux-btrfs/msg40323.html
What about an xattr on both subvolume and the swapfile that would inhibit btrfs user space tools from either snapshotting the subvolume or the swapfile? There could be a feature in btrfs user space tool to "create a swapfile" which would do the full sequence: 1. create a subvolume at the top level 2. set a "do not snapshot" xattr on subvolume 3. fallocate a swapfile, presumably contiguous since swap can't use a file with holes or gaps 4. set a "do not snapshot/reflink" xattr on the swapfile Does this solve any usability concerns? -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
