Bug 888208

Summary: can't reuse /home due to mountpoint entry being insensitive
Product: [Fedora] Fedora Reporter: Matthieu Pupat <redhat_bugzilla>
Component: anacondaAssignee: David Lehman <dlehman>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 18CC: anaconda-maint-list, g.kaviyarasu, jonathan, linuxaudio, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-16 15:03:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
requested log file: /tmp/storage.log
none
Requested log file: anaconda.log
none
Requested log file: /tmp/program.log
none
/tmp/anaconda.log
none
/tmp/program.log
none
/tmp/storage.log none

Description Matthieu Pupat 2012-12-18 09:44:57 UTC 
I have two RAID devices on my computer, a RAID0 and RAID1.

When installing Fedora 18 Beta using Manual Partitioning I can see two software RAID entries under Unknow at the very bottom of the left columns.

I cannot see the actual partitions: 1 under my RAID 0 and two under my RAID1

I cannot set mount points for them.
Comment 1 David Lehman 2012-12-18 17:38:42 UTC 
You have partitioned md arrays?

Please attach the following files from the shell on tty2 after entering the custom storage setup screen:

 /tmp/anaconda.log
 /tmp/storage.log
 /tmp/program.log
 /tmp/syslog

Please attach them individually and use text/plain for the type if possible. No archives, please.

Thanks.
Comment 2 Felix Homann 2013-01-16 17:45:06 UTC 
I'm trying to install F18 over an existing Ubuntu system. / and /home are ext4 formated RAID1 partitions, /dev/md2 is mounted on /, /dev/md3 is mounted on /home I cannot set mount points for those devices unless I mark them for reformatting. I'll attach the requested logs (when I found out how this works here).
Comment 3 Felix Homann 2013-01-16 17:46:07 UTC 
Created attachment 679727 [details]
requested log file: /tmp/storage.log
Comment 4 Felix Homann 2013-01-16 17:47:03 UTC 
Created attachment 679728 [details]
Requested log file: anaconda.log
Comment 5 Felix Homann 2013-01-16 17:47:38 UTC 
Created attachment 679729 [details]
Requested log file: /tmp/program.log
Comment 6 Felix Homann 2013-01-16 17:48:40 UTC 
Forgot to save /tmp/syslog. Will be provided later.
Comment 7 David Lehman 2013-01-16 21:18:42 UTC 
(In reply to comment #2)
> I'm trying to install F18 over an existing Ubuntu system. / and /home are
> ext4 formated RAID1 partitions, /dev/md2 is mounted on /, /dev/md3 is
> mounted on /home I cannot set mount points for those devices unless I mark
> them for reformatting. I'll attach the requested logs (when I found out how
> this works here).

What happened to your first run? It looks like something interrupted it and caused things to enter an inconsistent state.

Consider rebooting the live media and trying again, this time taking care not to kill the installer while it is running.
Comment 8 Felix Homann 2013-01-16 22:23:23 UTC 
On the first run the very same happened. That's why I interrupted anaconda. I couldn't even find a clean way to exit without being afraid of data loss. 
(Hint: It's not clear at all when changes the user makes to the disk layout will be applied - immediately,  later on, onWhateverClicked(). This keeps the user in a permanent state of fear and uncertainty if there's data he actually wants to keep.)

So when exactly do you actually want me to take the snapshots of all the logs?
Comment 9 Felix Homann 2013-01-22 10:10:18 UTC 
(In reply to comment #7)
> Consider rebooting the live media and trying again, this time taking care
> not to kill the installer while it is running.

OK, I've run it again. See the new logs. There is no /tmp/syslog btw. 

Once again for the record: Anaconda is really causing extreme fear and uncertainty when it comes to partitioning. You never know when you could possibly damage your disks and data. There's no "Abort" or "Cancel" button and no description whatsoever telling what "Done" actually means or does.
Comment 10 Felix Homann 2013-01-22 10:11:01 UTC 
Created attachment 684982 [details]
/tmp/anaconda.log
Comment 11 Felix Homann 2013-01-22 10:12:14 UTC 
Created attachment 684983 [details]
/tmp/program.log
Comment 12 Felix Homann 2013-01-22 10:12:46 UTC 
Created attachment 684991 [details]
/tmp/storage.log
Comment 13 David Lehman 2013-01-29 21:44:27 UTC 
Nothing is written to disk until you click the "Begin Installation" button on the main screen.
Comment 14 David Lehman 2013-01-29 21:49:26 UTC 
(In reply to comment #2)
> I'm trying to install F18 over an existing Ubuntu system. / and /home are
> ext4 formated RAID1 partitions, /dev/md2 is mounted on /, /dev/md3 is
> mounted on /home I cannot set mount points for those devices unless I mark
> them for reformatting. I'll attach the requested logs (when I found out how
> this works here).

You cannot use a preexisting filesystem for / -- you must create a new one. For /home you should be able to simply enter the mountpoint and click "Apply Changes".
Comment 15 Felix Homann 2013-01-29 22:26:37 UTC 
(In reply to comment #14)
> You cannot use a preexisting filesystem for / -- you must create a new one.

Sure, it wouldn't make sense to use an installer otherwise.It's /home I care for.


> For /home you should be able to simply enter the mountpoint and click "Apply
> Changes".

Exactly, I *should* be able. I filed this bug report because I am *not* able to do this. The field where I am supposed to enter the mount point is not editable unless I mark my existing /home partition for reformatting.
I definitely don't want my /home partition to be reformatted.
Comment 16 Felix Homann 2013-01-29 22:31:14 UTC 
(In reply to comment #14)
> You cannot use a preexisting filesystem for / -- you must create a new one.

Sure, it wouldn't make sense to use an installer otherwise.It's /home I care for.


> For /home you should be able to simply enter the mountpoint and click "Apply
> Changes".

Exactly, I *should* be able. I filed this bug report because I am *not* able to do this. The field where I am supposed to enter the mount point is not editable unless I mark my existing /home partition for reformatting.
I definitely don't want my /home partition to be reformatted.
Comment 17 David Lehman 2013-01-30 15:36:24 UTC 
There's a problem detecting the filesystem on /dev/md/3. As a workaround, please try deactivating all of your md devices before running liveinst. Let me know how that goes.
Comment 18 Felix Homann 2013-03-06 09:15:40 UTC 
I chose to not use my existing /home but to install without a dedicated /home partition, first. Afterwards I added my md devices in /etc/fstab. This surely works but should not be neccessary.
Comment 19 David Lehman 2013-05-16 15:03:09 UTC 
Several issues with detection of md devices have been fixed for fedora 19 beta, which should be released within a couple of weeks. If you find that this issue remains in any version of Fedora 19 please reopen this bug and attach the new logs.