[Bug 996443] Re: use UUID=0 for "this partition", e.g. in fstab

André Pirard 996443 at bugs.launchpad.net
Tue May 8 15:41:19 UTC 2012


** Description changed:

  Any version, any release and probably any distribution.
+ 
+ Update:
+ 
+ Please please please read the title of this report and see that this report is not (only) related to Gparted but to UUID=0 being an alias of the UUID of the partition in which that reference appears.
+ The Gparted side of the story turns out to be bug #737387. 
+ 
+ --- EOE ---
  
  What happens.
  
  When GParted makes a backup of a partition, two partitions with the same UUID exist, which is contrary to principle.
  This produces a lot of confusion if both are visible, such as one being mounted but the other one is locked.
  If the backup UUID is changed, you get (for example) an unbootable backup system because fstab mounts the wrong UUID.
  
  What should happen.
  
  If UUID=0 meant "the UUID of the partition in which this reference is located" there would be no need to change the fstab (mounting UUID=0).
  If GParted made a backup with a different UUID (by default, optionally same or user specified UUID such as similar to previous one), there would no longer be any UUID concern.
  
  What should result.
  
  One more easy step towards a system as or more easy to use as ... other
  ones.

** Package changed: gparted (Ubuntu) => ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gparted in Ubuntu.
https://bugs.launchpad.net/bugs/996443

Title:
  use UUID=0 for "this partition", e.g. in fstab

Status in Ubuntu:
  New

Bug description:
  Any version, any release and probably any distribution.

  Update:

  Please please please read the title of this report and see that this report is not (only) related to Gparted but to UUID=0 being an alias of the UUID of the partition in which that reference appears.
  The Gparted side of the story turns out to be bug #737387. 

  --- EOE ---

  What happens.

  When GParted makes a backup of a partition, two partitions with the same UUID exist, which is contrary to principle.
  This produces a lot of confusion if both are visible, such as one being mounted but the other one is locked.
  If the backup UUID is changed, you get (for example) an unbootable backup system because fstab mounts the wrong UUID.

  What should happen.

  If UUID=0 meant "the UUID of the partition in which this reference is located" there would be no need to change the fstab (mounting UUID=0).
  If GParted made a backup with a different UUID (by default, optionally same or user specified UUID such as similar to previous one), there would no longer be any UUID concern.

  What should result.

  One more easy step towards a system as or more easy to use as ...
  other ones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/996443/+subscriptions




More information about the foundations-bugs mailing list