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 c
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
ubuntu-bugs@lists.
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
https://bugs.launchpad.net/b
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
ubunt
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 bec
** 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
https://lists.ubunt
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
ubuntu-bugs@lists.ubuntu.c
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"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/585092/+attach
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 receive
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 GNU/Linux
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
u
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
--
gi
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 that
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 delay
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 sin
@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 journal
** 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 not
Glad the Maverick kernel helps in your case. Though this is not the same
problems as the initially reported one which was a long wait time on
unmount. AFAIK the writeback code in 2.6.32 had another issue where an
active writer might starve other IO under certain conditions. But this
should probably
** Also affects: linux (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Lucid)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Lucid)
Status: New => In Progress
** Changed in: linux (Ubuntu Lucid)
Assignee: (unassigned) => Stefan
I've been dealing with this IO problem since a LONG time (months).
I've tried kernel 2.6.32-24.39~spcbug543617a and 2.6.32-23.38~lp585092v4. The
problem was still there.
I then installed the 2.6.35 kernel that Tim Gardner in #38 shared and now it at
last works normally
Everytime I had IO
You can also try an LTS backported 2.6.35 kernel from
http://ppa.launchpad.net/kernel-ppa/ppa/ubuntu
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Stefan Bader (stefan-bader-canonical)
--
giant IO delays
https://
Added test kernels for the latest updates. The series of patches is not
included automatically, yet as I want to get some upstream feedback on
the backport and potentially submit that to upstream stable.
--
giant IO delays
https://bugs.launchpad.net/bugs/585092
You received this bug notification
A new kernel update for Lucid has been released, 2.6.32-24.38. I have
servers using, 2.6.32-23.38~lp585092v4. Are the v4 patches in
2.6.32-24.38, or do we need a 2.6.32-24.38~lp585092v4?
--
giant IO delays
https://bugs.launchpad.net/bugs/585092
You received this bug notification because you are
Please read "2.6.32-22-generic" in comment #34.
--
giant IO delays
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
https://lists.ubuntu.com/
I tested the v4 and it works perfectly. While the 2.6.32-23-generic was
taking more than 12 seconds to accomplish an umount loop, the v4 takes
less than 100ms. Great ! Thanks.
--
giant IO delays
https://bugs.launchpad.net/bugs/585092
You received this bug notification because you are a member of
v4 works great for me so far!
--
giant IO delays
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
https://lists.ubuntu.com/mailman/listinfo/u
And so upstream gave us three more patches which have been put into v4
(plus one little fix up that was needed in NFS). I placed them to the
usual place. So if you (Kees, Brian) can play around with those and see
whether things seem better that way...
--
giant IO delays
https://bugs.launchpad.net
Yeah, an additional patch is needed. Christoph had coded up fixes which
had been scheduled for 2.6.36, and there is some talk about just taking
those for 2.6.35. Discussion is ongoing and Linus hasn't merged anything
yet; the patches in question are http://lkml.org/lkml/2010/7/6/31.
Stefan, I had
I saw Brian's mail which may require more work on that. Meanwhile I made
a v2 series of test kernel because v1 still had the work around in there
which caused some of this. While waiting for answers from Christoph,
maybe those may or may not work...
--
giant IO delays
https://bugs.launchpad.net/b
Doh! The kernels are at http://people.canonical.com/~smb/lp585092/
--
giant IO delays
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
https:
Kees, Brian,
I saw those going mainline now. To have them in Lucid, there are 4 more
patches required. Luckily only one of those looks to have a somewhat
bigger impact. But its still a bunch of 12 patches altogether. I made
some Lucid kernels with those (I tricked a bit because normally those
are
** Summary changed:
- tmpfs umount slowdown
+ giant IO delays
--
giant IO delays
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
https://li
33 matches
Mail list logo
