Hello all,
The fix released to address this bug's issue unfortunately leads to problem for
those who use the Lustre filesystem (see http://www.lustre.org):
- kernel hangs when attempting to mount a Lustre filesystem with the wrong
NID (which fortunately should not happen in normal operating
This bug was fixed in the package linux - 2.6.32-25.44
---
linux (2.6.32-25.44) lucid-proposed; urgency=low
[ Brad Figg ]
* SAUCE: (no-up) Modularize vesafb -- fix initialization
- LP: #611471
[ Stefan Bader ]
* Revert SAUCE: sync before umount to reduce time taken by
I tried the new proposed kernel and the problem no longer exists for me.
--
giant IO delays on unmount
https://bugs.launchpad.net/bugs/585092
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Yes, both reports are at least closely related or even duplicates. Based
on the feedback in the other bug report I would therefor go ahead and
mark this verified, too.
** Tags added: verification-done
** Tags removed: verification-needed
--
giant IO delays on unmount
Isn't this bug just a duplicate of bug 543617 which has also been fixed
and verified?
--
giant IO delays on unmount
https://bugs.launchpad.net/bugs/585092
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Could someone (the original reporter?) please test this on the proposed
kernel and report on whether it is resolved? See comment #45 for
information about how to enable the proposed kernel.
--
giant IO delays on unmount
https://bugs.launchpad.net/bugs/585092
You received this bug notification
** Branch linked: lp:ubuntu/linux-mvl-dove
--
giant IO delays on unmount
https://bugs.launchpad.net/bugs/585092
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Also look for writeback in
Bug #543617
Bug #585092
Bug #601361
Bug #620242
Bug #628047
--
giant IO delays on unmount
https://bugs.launchpad.net/bugs/585092
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
17:26
$ grep Dirty /proc/meminfo
Dirty: 464116 kB
17:27
$ grep Dirty /proc/meminfo
Dirty: 518628 kB
17:28
$ grep Dirty /proc/meminfo
Dirty: 705216 kB
gets to around 1124256 then levels off
$ uname -a
Linux zirconium 2.6.32-25-generic #43-Ubuntu SMP Wed Sep 1 09:46:13 UTC 2010
x86_64
File system is xfs not ext4. rdiff-backup finished. Dirty keeps
gradually dropping but strangely free space is increasing not dropping.
I'd expect as data gets flushed out it would take up more disk space not
less.
--
giant IO delays on unmount
https://bugs.launchpad.net/bugs/585092
You
The
INFO: task dpkg:11727 blocked for more than 120 seconds.
messages stopped but dpkg is still stuck with 0:01 sec of CPU time.
The attached file shows things back when rdiff-backup was running.
** Attachment added: procs
dpkg resumed and finished up as if nothing strange had happened.
--
giant IO delays on unmount
https://bugs.launchpad.net/bugs/585092
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Accepted linux into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
SRU Justification
Impact: The upstream process for stable tree updates is quite similar in
scope to the Ubuntu SRU process, e.g., each patch has to demonstrably
fix a bug, and each patch is vetted by upstream by originating either
directly from Linus' tree or in a minimally backported form of
Backported writeback changes now in the repo. Until proposed is ready to
upload the new kernel, it is only availble int the pre-proposed PPA
(https://launchpad.net/~kernel-ppa/+archive/pre-proposed)
** Changed in: linux (Ubuntu Lucid)
Status: In Progress = Fix Committed
--
giant IO
@Stephan Bader: from my research, the *two* bugs are related to the
cleaning of the dirty inodes. Umounting a ext4 filesystem with dirty
inodes will generate a lot of IO since the journal is mixed up. The same
dirty inodes problem exist when there is a lot of IO since jdb2 tries to
keep the
The problem with unmount which the patches address and about which the report
here was (as far as I understood it) was not so much the number of IO generated
(though it makes things worse) but the fact that the sync on unmount had changed
from being asynchronous to synchronous. That means every
** Also affects: linux (Ubuntu Maverick)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: Triaged
** Changed in: linux (Ubuntu Maverick)
Status: Triaged = Fix Released
--
giant IO delays on unmount
https://bugs.launchpad.net/bugs/585092
You received this bug
18 matches
Mail list logo
