Bug#612402: upgraded systems won't boot from UUID volumes

2013-04-09 Thread Ian Campbell
On Sun, 2013-04-07 at 17:15 +0100, Ben Hutchings wrote: So it seems that this is only going to be an issue if users take the unusual step of changing /etc/fstab to refer to LVs by UUID. But maybe there are management tools that do that as a matter of course? I vaguely recall the occasion

Bug#612402: upgraded systems won't boot from UUID volumes

2013-04-08 Thread Daniel Pocock
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/04/13 18:15, Ben Hutchings wrote: On Sun, 2013-04-07 at 16:19 +0200, Daniel Pocock wrote: On 07/04/13 15:47, Neil Williams wrote: On Sun, 07 Apr 2013 15:25:43 +0200 Daniel Pocock dan...@pocock.com.au wrote: I notice this bug was

Bug#612402: upgraded systems won't boot from UUID volumes

2013-04-07 Thread Ben Hutchings
On Sun, 2013-04-07 at 16:19 +0200, Daniel Pocock wrote: On 07/04/13 15:47, Neil Williams wrote: On Sun, 07 Apr 2013 15:25:43 +0200 Daniel Pocock dan...@pocock.com.au wrote: I notice this bug was downgraded below the RC threshold and appears to have been missed so far: It was only

Bug#612402: upgraded systems won't boot from UUID volumes

2013-04-07 Thread Steve Langasek
On Sun, Apr 07, 2013 at 04:01:25PM +0100, Roger Leigh wrote: UUIDs are used by default AFAICS when the installer creates the fstab, and should work just fine. Just looking and I don't have an example system which uses UUIDs /and/ LVM root, however--this does not appear to be the default for

Bug#612402: upgraded systems won't boot from UUID volumes

2013-04-07 Thread Henrique de Moraes Holschuh
On Sun, 07 Apr 2013, Ben Hutchings wrote: So it seems that this is only going to be an issue if users take the unusual step of changing /etc/fstab to refer to LVs by UUID. But maybe there are management tools that do that as a matter of course? One should never use UUIDs in fstab to refer to