Red Hat Bugzilla – Bug 164360
During formating of partitions anaconda reports bug if you rename a Logical Volume during setup
Last modified: 2007-11-30 17:11:10 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Description of problem:
When setting up a new Fedora Core 4 system, if you use LVM and try to rename a Logical Volume to say "LogVolRoot" instead of using "LogVol00" (then continue through all the other prompts) and get to "About to Install", click Next. You get exception occurred. An unhandled exception has occured...
Traceback (most recent call list)
File "/usr/lib/anaconda/gui.py" line 1137...
File "/usr/lib/anaconda/packages.py" line 579, in turnOnFilesystems
File "/usr/lib/anaconda/partedUtils.py" line 726, in savePartitions
error: Error: Error informing the kernel about modifications to partition /dev/hda5 - Device or resource busy. This means that Linux won't know about any changes made to /dev/hda5 until you reboot...
Now, this appears to only happen if you have at least 2 Logical Volume partitions. In this case, one was called LogVolRoot and the other LogVolHome
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install FC4 using anaconda
2. During LVM setup, rename at least 2 LVMs to say "LogVolRoot" instead of LogVol00 and "LogVolHome" instead of LogVol01
3. Continue through the setup
4. When it gets to last screan, click Next to begin formatting partitions, error occurs.
Actual Results: get the error report stated above
Expected Results: format partions, and install OS. (which happens if everyone is done the same but leave the Logical Volumes names as the default. (ie, LogVol00)
*** This bug has been marked as a duplicate of 160693 ***