Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
IOException: Partition(s) 2 on /dev/sda have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further
DescriptionAlexander Todorov
2012-04-05 08:13:26 UTC
libreport version: 2.0.7
executable: /usr/bin/python
hashmarkername: anaconda
kernel: 3.2.1-0.9.el7.x86_64
product: Red Hat Enterprise Linux
reason: IOException: Partition(s) 2 on /dev/sda have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.
time: Thu 05 Apr 2012 04:12:57 AM EDT
version: 7.0
anaconda-tb-C3M01a: Text file, 344305 bytes
description:
:The following was filed automatically by anaconda:
:anaconda 16.25.4 exception report
:Traceback (most recent call first):
: File "/usr/lib64/python2.7/site-packages/parted/disk.py", line 213, in commit
: return self.__disk.commit()
: File "/usr/lib64/python2.7/site-packages/parted/decorators.py", line 32, in new
: ret = fn(*args, **kwds)
: File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/disklabel.py", line 263, in commit
: self.partedDisk.commit()
: File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/disklabel.py", line 242, in create
: self.commit()
: File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/deviceaction.py", line 433, in execute
: options=self.device.formatArgs)
: File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 316, in processActions
: action.execute(intf=self.intf)
: File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 385, in doIt
: self.devicetree.processActions()
: File "/usr/lib64/python2.7/site-packages/pyanaconda/packages.py", line 122, in turnOnFilesystems
: anaconda.storage.doIt()
: File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 373, in dispatch
: self.dir = self.steps[self.step].target(self.anaconda)
: File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 88, in return_false
: func(*args, **kwargs)
:IOException: Partition(s) 2 on /dev/sda have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.
Comment 1Alexander Todorov
2012-04-05 08:13:30 UTC
Comment 2Alexander Todorov
2012-04-05 08:15:20 UTC
My ks.cfg is:
clearpart --all --initlabel
# Disk partitioning information
part biosboot --fstype="biosboot" --size=1
part /boot --asprimary --fstype="ext3" --size=200 --label=BOOT
part swap --fstype="swap" --recommended --label=SWAP
part /multi-stage --fstype="ext3" --size=100 --label=MULTISTAGE
part raid.01 --grow --size=2048
part raid.02 --grow --size=2048
raid / --device=0 --fstype="ext3" --level=RAID0 raid.01 raid.02
Notice the --grow for RAID members. I wanted to check if RHEL7 will allow it (I think not). The bug however doesn't seem related to this.