Hugo Mills posted on Thu, 09 Jul 2015 13:54:48 +0000 as excerpted: > On Thu, Jul 09, 2015 at 01:43:53PM +0000, Duncan wrote: >> I could have sworn btrfs property -t subvolume can get/set that >> snapshot bit. I know I saw the discussion and I think patch for it go >> by, but again, as I don't use them, I haven't tracked closely enough to >> see if it ever got in. > > Are you thinking of the read-only flag? That's not the same thing > as the various UUID properties (e.g. parent) which can be used to > detemine if a subvolume was made using a snapshot. Perhaps, but I was sure there was a snapshot property too, because I remember discussion of being able to unset it in ordered to remove it from the snapshot (only) list. But maybe that's all it was, discussion, it wasn't implemented, and I ended up conflating it with the read-only bit, which /can/ be set/unset that way. Like I said I can't check as I don't have any subvolumes/ snapshots available to do a listing on and see, and the property manpage doesn't have a properties list to check on, it wants you to use the list option to get the list. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- 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
