On Thu, 1 May 2014, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > That has not been my experience. I changed /boot files to have the wrong > selinux labels, set .autorelabel, rebooted, and those files were fixed > despite /boot being a mount point for a btrfs subvolume named boot located > at the top level of the file system, and mounted with an fstab using > subvol=boot option. > > I can see how unmounted subvolumes won't be visible to any scripts or even > restorecon, so maybe that's what's being referred to? Yes I believe that the problem is anything that looks like a separate filesystem to stat() but doesn't have an entry in /proc/mounts. So if you mount the subvols separately then there's no problem. Another thing is that if the subvols aren't needed for booting (IE /home) then you can just manually label them either before or after the autorelabel boot. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/ -- 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
