Release upgrade converts /dev/mapper entries in /etc/fstab to UUID

Bug #563117 reported by Alvin on 2010-04-14
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: mountall

When installed from CD, ubuntu will create /dev/mapper/... entries in /etc/fstab for lvm volumes.

During a release upgrade, these are converted to UUID entries.
- This is not a good idea. Snapshots have the same UUID values as their parent. On Lucid beta2, I noticed that sometimes these snapshots are mounted instead of their parent!
- This is not consistent with 'fresh' installs.
- /dev/mapper/vg0-home is more readable than UUID="daec601e-736d-43b3-bdce-5e4138a4033c" and will not change on switching disks.

Emmet Hikory (persia) wrote :

I replicated this behaviour on a recent karmic->lucid powerpc upgrade (although I've now trimmed fstab back to sane values).

Changed in mountall (Ubuntu):
status: New → Confirmed
Colin Watson (cjwatson) wrote :

mountall never writes to fstab and has no maintainer scripts, so some other package is at fault. That said, from a quick look at the maintainer scripts in /var/lib/dpkg/info/ on my system, I can't find any of them writing to /etc/fstab. What's going on?

I'm pretty sure this is deliberate. It allows you to move a filesystem from a /dev/mapper device to a raw device later on (which is the kind of thing we want to support)

This is not a mountall bug (there is no postinst!)

affects: mountall (Ubuntu) → ubuntu

Maybe update-manager should handle this?

affects: ubuntu → update-manager (Ubuntu)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers