fstab UUID of swap doesn't update after resizing partitions

[Umang Varma]

I resized my partitions with gParted LiveCD and after rebooting, I found that the swap UUID in fstab was wrong. So was /etc/initramfs-tools/conf.d/resume. I fixed it myself and ran sudo update-initramfs -u as it said in the forums and it was fine.

I expected this to happen automatically. A lay person would expect his/her computer to work properly once they move their partitions around a little bit, therefore I would expect that the UUID in fstab get automatically corrected once the system is rebooted after a resize of partitions.

Thank you

Umang

I'm running 8.04, up-to-date. The way I found out that the swap wasn't being used was uSplashed stopped working properly and the computer was pretty slow.

[Umang Varma (umang)]

Isn't it possible to remove UUIDs altogether? So that each partition is identified with it's address (like /dev/sda8 for my swap) instead of the UUIDs which can keep changing. What's the advantage of keeping UUIDs?

[Dariel Dato-on (odd-rationale)]

Yes, you can easily change the UUID's with the device name in your /etc/fstab file. It should work fine.

The advantage of UUID dome into play when you have multiple disks. Sometimes then name of the device might change and the file system will fail to mount.

[Umang Varma (umang)]

I see. I don't know about all this too much, so my opinion shouldn't be taken too seriously, but I have a problem and I feel that should be fixed.

The swap's UUID changes when you do some resizing (not necessarily of the swap itself). So then the swap isn't swapped on after that. Isn't that a disadvantage of having only UUIDs? Is there no way in which we can have the name of the swap partition as well as the UUID?

A not so tech savy person will have a whole lot of trouble if they change their partitions a little bit and find their computer behaving weird even though the resizing process went fine.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Neil Munro (neilmunro-deactivatedaccount)]

The Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . It contains the 2.6.27 Ubuntu kernel. It would be great if you could test and verify if this is still an issue. The status is being set to Incomplete until we receive further feedback. Thanks.

[Srivatsa Kanchi R (srivatsak)]

This is still an issue with 8.10 release. I increased by swap partition; as before, the UUID of swap is not reflecting the correct one

[Umang Varma (umang)]

This is not a problem with gParted. It simply resized the partition as it was supposed to. This is just to request for an easy way of fixing the problem of changing UUIDs for swap partitions in fstab.

[Curtis Gedak (gedakc)]

GParted 0.4.4 has just been released. It includes a fix that maintains the UUID and LABEL when a swap partition is resized.

See GParted Bug:
http://bugzilla.gnome.org/show_bug.cgi?id=575585

[Umang Varma (umang)]

I didn't expect the problem to be solved from that end, but great! It's fixed!

[Darxus (darxus)]

The version with this problem is currently in Jaunty. A version after that with the fix is in Karmic.