From ec4b692c22730adea0fc7ce9eb3ce0a5747f3133 Mon Sep 17 00:00:00 2001 From: Axel Beckert Date: Tue, 21 Jul 2015 13:20:34 +0200 Subject: [PATCH] Remove already fixed issue from KNOWN_BUGS 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. --- KNOWN_BUGS.markdown | 17 ----------------- 1 file changed, 17 deletions(-) diff --git a/KNOWN_BUGS.markdown b/KNOWN_BUGS.markdown index ca3aae2..e00fd32 100644 --- a/KNOWN_BUGS.markdown +++ b/KNOWN_BUGS.markdown @@ -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`.