[Bug 1124034] [NEW] Cancelling resize operation leaves resize2fs running

Alan Jenkins alan.christopher.jenkins at googlemail.com
Wed Feb 13 11:53:46 UTC 2013


Public bug reported:

I used GParted to shrink a 400G partition on an external USB3 HD, to
200G.  The filesystem was ext4.

I got bored and annoyed by the lack of a progress indicator.  I clicked
cancel, disregarding the warning that this was a REALLY BAD IDEA :).  I
then closed GParted.

When I tried to fsck the partition, I found that something had an
exclusive lock on the partition.  It turns out that resize2fs was still
running, using CPU and performing IO.  (There are no IO errors in the
kernel log / dmesg).

I can understand if GParted was reluctant to kill resize2fs :).  However
in that case it should have warned that the operation was not actually
cancelled.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gparted 0.11.0-2
ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35
Uname: Linux 3.2.0-37-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
Date: Wed Feb 13 11:46:00 2013
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gparted
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gparted (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug precise

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

Title:
  Cancelling resize operation leaves resize2fs running

Status in “gparted” package in Ubuntu:
  New

Bug description:
  I used GParted to shrink a 400G partition on an external USB3 HD, to
  200G.  The filesystem was ext4.

  I got bored and annoyed by the lack of a progress indicator.  I
  clicked cancel, disregarding the warning that this was a REALLY BAD
  IDEA :).  I then closed GParted.

  When I tried to fsck the partition, I found that something had an
  exclusive lock on the partition.  It turns out that resize2fs was
  still running, using CPU and performing IO.  (There are no IO errors
  in the kernel log / dmesg).

  I can understand if GParted was reluctant to kill resize2fs :).
  However in that case it should have warned that the operation was not
  actually cancelled.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gparted 0.11.0-2
  ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35
  Uname: Linux 3.2.0-37-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  Date: Wed Feb 13 11:46:00 2013
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gparted
  UpgradeStatus: No upgrade log present (probably fresh install)

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




More information about the foundations-bugs mailing list