[Bug 1269175] Re: lvresize, lvextend, and fsadm attempt to fsck a mounted filesystem

Tue Jan 14 23:24:26 UTC 2014

It looks like the above fixes were incorporated into 
v2_02_91
and 
v2_02_96 and newer.

That means I will also have to port this fix to quantal.

** Changed in: lvm2 (Ubuntu)
       Status: New => Confirmed

** Changed in: lvm2 (Ubuntu)
       Status: Confirmed => In Progress

** Description changed:

+ [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
  ProcVersionSignature: User Name 3.2.0-57.87-generic 3.2.52
  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
  Ec2AvailabilityZone: nova
  Ec2InstanceType: cpu1-ram1-disk50-ephemeral20
  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)

** Description changed:

  [Impact]

-  * Potential filesystem corruption
+  * Potential filesystem corruption

-  * The above is remedied by backporting a fix from upstream lvm2 that
+  * 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]

- [Regression Potential] 
- 
-  * There is regression potential for scripts that depend on fsadm return
+  * 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
+  * 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
+ 
+  * 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
  ProcVersionSignature: User Name 3.2.0-57.87-generic 3.2.52
  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
  Ec2AvailabilityZone: nova
  Ec2InstanceType: cpu1-ram1-disk50-ephemeral20
  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)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1269175

Title:
  lvresize,lvextend, and fsadm attempt to fsck a mounted filesystem

Status in “lvm2” package in Ubuntu:
  In Progress

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
  ProcVersionSignature: User Name 3.2.0-57.87-generic 3.2.52
  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
  Ec2AvailabilityZone: nova
  Ec2InstanceType: cpu1-ram1-disk50-ephemeral20
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1269175/+subscriptions