Dapper Flight 7 doesn't obey format or file system selections
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
On Dapper Flight 7 Live CD:
1a) Use GParted (System | Administration | Gnome Partition Editor) to setup partitions to desired file system other than ext3. Apply is successful apparently.
/dev/hde1 reiserfs or reiser4
/dev/hde2 reiserfs or reiser4
/dev/hde3 extended
/dev/hde5 linux-swap
OR
1b) Use Install to manually setup the above configuration.
2) In the installer, select the root mount point (hde1) and swap (hde5) and DO NOT format.
3) Next screen may say it WILL format even though I deselected format.
4) Same screen as step 3 intermittently reports correct file system to be formatted (or none at all). Sometimes says it will format to ext3.
5) Click Back button to confirm/edit partition layout.
6) Go back to step 3.
It would be cool to reference a reply in a bug report such as this one:
https:/
(The ubuntu forums has http://
<b>Re: espresso formats partitions it wasn't asked to</b> Posted by <u>Ublis</u> at 2006-05-02 17:09:19 UTC
I can verify it still occurs. First I saw in the overview that the swap partition was going to be formatted as swap, though I requested it not to. The other partitions which were used showed "partition <bla> is going to be formatted as" - without mentioning as what. I had no idea what this was supposed to mean: will they be formatted or not? I went back to the mounting points definition, checked I did the right thing and went forward to the overview. Now it said they'll be formatted as ext3.
Fortunately I had a new HD, so nothing was lost - except I was forced to use ext3 instead of xfs, which is what I was aiming for.
<b><u>I assume he meant Beta 2. I am reporting it still occuring in Flight Alpha 7</u></b>, if we are talking about the same bug.
The reason I am reporting this now (so late) is that sometimes the Update fails and hoses my system and I have been trying to come up with a scheme to copy partitions to use as a backup before attempting an update. As well as using more stable file systems. Please advise as to the best stable file system to recover from power outages as well as failed updates.
Thanks for your report. However, this really is just bug 35079 - the piece you're missing is that it was fixed *after* Flight CD 7! If you could, it would be appreciated if you'd try out a daily build (http:// cdimage. ubuntu. com/daily- live/current/) and make sure it's fixed there.