lvresize,lvextend, and fsadm attempt to fsck a mounted filesystem
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| lvm2 (Ubuntu) |
Fix Released
|
Undecided
|
reem | ||
| Precise |
Fix Released
|
Medium
|
Dave Chiluk | ||
Bug Description
[Impact]
* Potential filesystem corruption
* The above is remedied by backporting a fix from upstream lvm2 that allows fsadm to return 3 on attempts to check a mounted filesystem. This allows lvextend and lvresize to proceed without a fsck when the filesystem is mounted.
[Test Case]
1. Run lvextend -L +...G -r <LV block device>
2. Obtain a message saying:
WARNING!!! The filesystem is mounted. If you continue you ***WILL***
cause ***SEVERE*** filesystem damage.
Do you really want to continue<n>?
3. Reply no, and lvextend or lvresize proceed anyway, freaking out any user who does not recognize the above message as having come from fsck.
4. Reply yes, and possibly corrupt your filesystem.
[Regression Potential]
* There is regression potential for scripts that depend on fsadm return values. I did search for other references to "fsadm" within the lvm2 package, but found none.
* Possible regressions may manifest themselves as other filesystem or lvm2 tools failing.
[Other Info]
* All 4 patches that were backported for this fix exist upstreams
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
-------
Steps to Reproduce:
1. Run lvextend -L +...G -r <LV block device>
2. Obtain a message saying:
WARNING!!! The filesystem is mounted. If you continue you ***WILL***
cause ***SEVERE*** filesystem damage.
Do you really want to continue<n>?
3. Reply no, and lvextend or lvresize proceed anyway, freaking out any user who does not recognize the above message as having come from fsck.
4. Reply yes, and possibly corrupt your filesystem.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: lvm2 2.02.66-4ubuntu7.3
ProcVersionSign
Uname: Linux 3.2.0-57-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
Date: Tue Jan 14 22:33:52 2014
Ec2AMI: ami-000005c2
Ec2AMIManifest: FIXME
Ec2Availability
Ec2InstanceType: cpu1-ram1-
Ec2Kernel: aki-00000548
Ec2Ramdisk: ari-00000548
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: lvm2
UpgradeStatus: No upgrade log present (probably fresh install)
Related branches
| Dave Chiluk (chiluk) wrote | #1 |
| Dave Chiluk (chiluk) wrote | #2 |
| description: | updated |
| tags: | removed: ec2-images |
| Changed in lvm2 (Ubuntu): | |
| assignee: | nobody → Dave Chiluk (chiluk) |
| Dave Chiluk (chiluk) wrote | #3 |
| Changed in lvm2 (Ubuntu): | |
| status: | New → Confirmed |
| status: | Confirmed → In Progress |
| description: | updated |
| description: | updated |
| Ubuntu Foundations Team Bug Bot (crichton) wrote | #4 |
| tags: | added: patch |
| Dave Chiluk (chiluk) wrote | #5 |
| Changed in lvm2 (Ubuntu Precise): | |
| assignee: | nobody → Dave Chiluk (chiluk) |
| importance: | Undecided → Medium |
| status: | New → In Progress |
| Changed in lvm2 (Ubuntu): | |
| assignee: | Dave Chiluk (chiluk) → nobody |
| status: | In Progress → Fix Released |
| Chris J Arges (arges) wrote | #6 |
| Brian Murray (brian-murray) wrote Please test proposed package | #7 |
| Changed in lvm2 (Ubuntu Precise): | |
| status: | In Progress → Fix Committed |
| tags: | added: verification-needed |
| Dave Chiluk (chiluk) wrote | #8 |
| tags: |
added: verification-done removed: verification-needed |
| Launchpad Janitor (janitor) wrote | #9 |
| Changed in lvm2 (Ubuntu Precise): | |
| status: | Fix Committed → Fix Released |
| Colin Watson (cjwatson) wrote Update Released | #10 |
| Changed in lvm2 (Ubuntu): | |
| assignee: | nobody → reem (reemhassan333) |
The above is remedied by backporting a fix from upstream lvm that allows fsadm.sh to return 3 on attempts to check a mounted filesystem. This allows lvextend and lvresize to not error out when the filesystem is mounted.