On Thu, 2012-10-25 at 14:28 +0100, Hugo Mills wrote: > How about user xattrs? IIRC, that's the user.* namespace. Yes, but we still need some kind of metadata standard. For instance, I might want to put a list of packages that were changed in the metadata so that admins know why the snapshot was created. It's highly likely distros like Ubuntu won't want to do it using the same mechanism (i.e. using PackageKit) but having some shared specs is probably a good idea. > The only convention I'm aware of is Ubuntu's use of an @ > substitution, where the subvolume to be mounted at / is called @, and > the subvolume to be mounted at /home becomes @home. That could work I suppose. > Both of those > subvolumes are stored in the (otherwise empty) top-level of the > filesystem, which is not mounted in normal operation. If we do one upgrade a week, that's 52 subvolumes cluttering things up. Should the subvolumes be placed somewhere upgrade specific? Any best practice ideas on naming? e.g. @system-upgrade-20121025? Richard -- 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
