[Bug] New "mount" does not recognize loop mounts
When called with "-a" the new mount command always mounts the loop mounts in /etc/fstab and does not check if they are already mounted. Because "mount -a" was called twice during init, any loop mounts in /etc/fstab are then mounted twice on startup.
This problem will be solved in the future because it is on util-linux'es todo list (see function mnt_table_is_fs_mounted in "util-linux/libmount/src/tab.c"). But the deprecated mount command already has this check and I was using this feature for years. So shall we temporarily switch back to the deprecated mount command, or just write workarounds in the init scripts? |
I don't see the problem, you did read mount.c didn't you?
|
Yes and now I find that this bug is filesystem specific. Will dig further tomorrow.
|
All times are GMT -5. The time now is 12:58 PM. |