|Summary:||systemd-fstab-generator doesn't understand squashfs-on-loop entries and prevents auto-mounting them|
|Product:||Red Hat Enterprise Linux 7||Reporter:||Laszlo Ersek <lersek>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:||Petr Sklenar <psklenar>|
|Version:||7.0||CC:||jscotka, lnykryn, systemd-maint-list|
|Fixed In Version:||systemd-208-4.el7||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2014-06-13 10:32:11 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Laszlo Ersek 2014-02-16 16:13:05 UTC
Description of problem: I have two squashfs files in my /etc/fstab, and they are to be auto-mounted when the system starts. It used to work with RHEL-6, and I also *think* it used to work with earlier (of course unreleased) builds of RHEL-7. Version-Release number of selected component (if applicable): systemd-208-2.el7.x86_64 Contents of /etc/fstab (the two relevant entries): /home/virt-images/tools/gcc-linaro-aarch64-linux-gnu-4.8-2013.09_linux.squashfs /mnt/arm-cross squashfs ro,loop 0 0 /home/lacos/Public/list-archives.gzip.squashfs /mnt/list-archives squashfs ro,loop 0 0 dmesg: [ 10.813629] systemd-fstab-generator: Checking was requested for "/home/virt-images/tools/gcc-linaro-aarch64-linux-gnu-4.8-2013.09_linux.squashfs", but it is not a device. [ 10.813680] systemd-fstab-generator: Checking was requested for "/home/lacos/Public/list-archives.gzip.squashfs", but it is not a device. After the system boots and I log in, I can successfully issue "mount -a", and these are mounted. They should be auto-mounted at boot time too.
Comment 2 Lukáš Nykrýn 2014-02-17 11:44:08 UTC
There is a wrongly applied patch, which caused that.
Comment 6 Ludek Smid 2014-06-13 10:32:11 UTC
This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request.