Package: bilibop-lockfs Version: 0.5.5 Severity: important Tags: upstream A user reported me that:
> After installing the package and configuring the wanted behavior over > the configuration file I have restarted my system but it ran into a > mount error. > My analysis revealed that one of my filesystems couldn't be mounted > because of the fact that the underlying tmpfs filesystem has been > mounted read-only and so the needed subdirectories ro,rw and.rw > couldn't be created to mount the different branches. The reason why > the tmpfs filesystem has been mounted read-only was the fact that the > original filesystem was marked as read-only in the fstab either. > So I have looked into the mount-helper script and I have noticed that > you apply the mount options of the original filesystem to the writable > branch and so you apply the read-only option either but this prevents > the creation of the needed subdirectories. This is reproducible. A 'ro' mount option in fstab that is applied without error when bilibop-lockfs is disabled, breaks the boot sequence (to recovery mode) when bilibop-lockfs is enabled. -- no system information -- no debconf information
