Bug 683574

Summary:	Logical volume resize causes corrupted filesystem
Product:	[Fedora] Fedora	Reporter:	David Lehman <dlehman>
Component:	anaconda	Assignee:	David Lehman <dlehman>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	high
Version:	15	CC:	jlaska
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:	AcceptedBlocker
Fixed In Version:	anaconda-15.26-1.fc15	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	681597	Environment:
Last Closed:	2011-04-05 21:39:13 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	657618

Description David Lehman 2011-03-09 18:28:30 UTC

+++ This bug was initially created as a clone of Bug #681597 +++

Description of problem:
An attempt to resize existing logical volume during installation can corrupt filesystem on it. See steps to reproduce, logs from the installation will be attached.

Version-Release number of selected component (if applicable):
anaconda-15.20-1

How reproducible:
probably always

Steps to Reproduce:
1. install with default LVM partitioning
2. start new installation in graphical mode
3. use custom partitioning
4. edit and resize existing logical volume holding / from previous install
   new size: 2000 MB
   mount point: /mnt/resized
5. create logical volume for new root filesystem
6. reuse /boot and swap partitions from previous installation
7. continue with the installation

Actual results:
error message:

Unable to mount filesystem
An error occurred mounting device /dev/mapper/vg_rtt7-lv_root as /mnt/resized: mount failed: (9, None). This is a fatal error and the install cannot continue.

Press <Enter> to exit the installer.


Expected results:
resized logical volume is mounted after resizing, installer continues with package selection.

Comment 1 David Lehman 2011-03-09 19:07:37 UTC

Fixed for Fedora 15 in anaconda-15.22-1.

Comment 2 James Laska 2011-03-11 19:40:38 UTC

Discussed at 2011-03-11 blocker review meeting.  This issue is fixed and available for testing in anaconda-15.22-1.  The issue has been accepted as a beta blocker.

Comment 3 Fedora Update System 2011-03-29 20:59:00 UTC

anaconda-15.26-1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/anaconda-15.26-1.fc15

Comment 4 Fedora Update System 2011-03-30 02:25:54 UTC

Package anaconda-15.26-1.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-15.26-1.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/anaconda-15.26-1.fc15
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2011-04-05 21:37:49 UTC

anaconda-15.26-1.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.