aufs fstab entries require ordering logic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mountall (Ubuntu) |
Fix Released
|
Medium
|
Scott James Remnant (Canonical) | ||
Karmic |
Fix Released
|
Medium
|
Scott James Remnant (Canonical) |
Bug Description
Binary package hint: mountall
The manual page of fstab says: "The order of records in fstab is important because fsck(8), mount(8), and umount(8) sequentially iterate through fstab doing their thing."
But if the contents of the /etc/fstab file are:
/dev/sda2 /.snapshot/home ext4 ro 0 0
none /.snapshot/home_ram tmpfs defaults 0 0
none /home aufs br=/.snapshot/
mountall mounts first the virtual file systems (tmpfs and aufs) and after that mounts the first one which is incorrect and leads to an undesired result.
Bug found on package mountall (dpkg -l mountall -> version=0.1.6, mountall --version -> 0.1.0), on karmic alpha-6.
Changed in mountall (Ubuntu): | |
status: | Triaged → In Progress |
assignee: | nobody → Scott James Remnant (scott) |
milestone: | none → ubuntu-9.10 |
Changed in mountall (Ubuntu Karmic): | |
status: | In Progress → Fix Committed |
This is by design of mountall, it mounts the contents of fstab in a necessary order rather than the specified order. Will fix the fstab manpage later.
We should handle aufs entries though, that's simply a bug