github.com/xen-tools.xen-tools
1
0
Fork 0
mirror of synced 2026-02-01 14:02:11 +00:00
Code Releases Activity

Remove already fixed issue from KNOWN_BUGS

Browse Source 
According to the `mount(8)` man page, `-a` mounts the filesystems
_following their order in fstab_. So reproducing that does not help in
our case and the implemented workaround (sort by mountpoint length)
should be sufficient.
This commit is contained in:
Axel Beckert
2015-07-21 13:20:34 +02:00
parent d04850da83
commit ec4b692c22
1 changed files with 0 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
KNOWN_BUGS.markdown
View File

@@ -10,20 +10,3 @@ Bugs to fix rather soon
least with `--lvm`. Thanks to Antoine Benkemoun for reporting.
[Bug Report](http://xen-tools.org/pipermail/xen-tools-discuss/2010-May/000757.html)
* partitions were mounted in config file order, not in mountpoint order.
That implies that if you specified :
/boot
/
in that order, `/` was mounted _over_ `/boot`, and you would not
_see_ `/boot`. Xen-Tools would then install `boot` on your `/`
partition, and your boot device was just empty and unbootable.
Workaround for 4.2 is to write your partition file such as mounts overlap
correctly when mounted in specified order.
Current (unreleased) fix is to sort by mountpoint length.
Fix would be to reproduce what mount does with mount `-a`.