On Fri, Oct 10, Richard W.M. Jones wrote:> My guess is that the last one (opt/value) will be different for you.Thanks for the pointers. I will poke around. At least augtool on the host seems to behave correctly: olaf@bax:~ $ cd /dev/shm/$$ bash: cd: /dev/shm/3570: Datei oder Verzeichnis nicht gefunden olaf@bax:~ $ mkdir $_ olaf@bax:~ $ cd $_ olaf@bax:/dev/shm/3570 $ mkdir etc olaf@bax:/dev/shm/3570 $ cat > etc/fstab UUID=d538a81f-9778-424d-96cc-e48dd2d4a323 swap swap defaults 0 0 UUID=65b72f12-eccb-4cf2-a4f4-9c4bb462456f / btrfs defaults 0 0 UUID=65b72f12-eccb-4cf2-a4f4-9c4bb462456f /var/spool btrfs subvol=@/var/spool 0 0 olaf@bax:/dev/shm/3570 $ augtool -r $PWD augtool> ls /files/etc/fstab/3/vfstype augtool> get /files/etc/fstab/3/vfstype /files/etc/fstab/3/vfstype = btrfs augtool> get /files/etc/fstab/3/opt/value /files/etc/fstab/3/opt/value = @/var/spool augtool> I will poke around to see what I find. Olaf
On Friday, October 10, 2014 03:07:51 PM Olaf Hering wrote:> Thanks for the pointers. I will poke around. At least augtool on the > host seems to behave correctly:I don't think this is related to Augeas. Instead, I think it's the naming convention SUSE uses for the root btrfs subvolume (@). I encountered this same issue in virt-v2v and posted a question here: https://www.redhat.com/archives/libguestfs/2014-April/msg00071.html At the time, the problem only seemed to break v2v in SUSE environments, so I created a local patch to strip out the duplicate root in the v2v process. As other tools are running into this, we should probably deal with this in guestfs itself. -Mike
On Fri, Oct 10, Mike Latimer wrote:> On Friday, October 10, 2014 03:07:51 PM Olaf Hering wrote: > > Thanks for the pointers. I will poke around. At least augtool on the > > host seems to behave correctly: > > I don't think this is related to Augeas. Instead, I think it's the naming > convention SUSE uses for the root btrfs subvolume (@).It does not look like its the naming convention. Insteads its the fact that a given subvolume is for the entire root filesystem. So both sda2 and also the 'whatever' subvolume get ->is_root=1. I can probably add a check somewhere to catch the whatever=="@". A better fix would be to check if a given subvolume is for the entire partition. Furthermore there are appearent bugs in the subvolume parser. Will send a patch to fix one of them shortly. Olaf