From: Jeff Mahoney <jeffm@suse.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] [PATCH] Fix for hanging resize on root filesystem
Date: Fri, 10 Sep 2004 08:47:24 -0400 [thread overview]
Message-ID: <4141A25C.70701@suse.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1919 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello all -
I recently ran across a bug that was initially suspected to be a
reiserfs bug, but turned out to be (I feel) a problem with the LVM
userspace utilities.
When a user has their root filesystem on an LV and attempts to resize
the LV, the kernel will deadlock while trying to update the atime on the
device node.
The following sequence causes the lockup:
open /dev/somedisk
suspend the dm instance
~ -> *_write_super_lockfs flushes and disallows new transactions
read from /dev/somedisk
~ -> if needed, update atime
~ -> dirty inode
~ -> tries to start transaction and waits for transactions to be
~ allowed again (waits forever, unless the LV is unlocked by
~ another process, which will cease the deadlock but cause the
~ lvresize operation to occur with the dm device active)
The attach patch causes dev_open_flags to add the O_NOATIME to the
open flags, which will avoid the deadlock by not updating the atime.
Note that the resize on the root LV, when using ext3, will succeed most
of the time. This _isn't_ because of correctness, but because it manages
to perform the operations without crossing a 1-second interval. If a
delay is introduced between one of the reads, for example, it will also
deadlock.
The reason I feel this isn't a kernel bug, but rather a userspace bug,
is that the LVM code explicitly suspends the device, and then performs
operations with implicit writes associated with them. The reads/writes
from the device are totally valid, but the inode atime update isn't. The
kernel behavior is as expected.
- -Jeff
- --
Jeff Mahoney
SuSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFBQaJcLPWxlyuTD7IRAgmzAJ4h28KLAjeKopQ8/OUkVa7Xg96yTACeL5YI
Z2YrBse1UMvAJEfFMeXKAA8=
=YfD4
-----END PGP SIGNATURE-----
[-- Attachment #2: lvm2-noatime.patch --]
[-- Type: text/x-patch, Size: 515 bytes --]
diff -rup LVM2.2.00.15/lib/device/dev-io.c LVM2.2.00.15-devel/lib/device/dev-io.c
--- LVM2.2.00.15/lib/device/dev-io.c 2004-04-16 14:43:29.000000000 -0400
+++ LVM2.2.00.15-devel/lib/device/dev-io.c 2004-09-09 06:35:23.073233392 -0400
@@ -300,6 +300,11 @@ int dev_open_flags(struct device *dev, i
flags |= O_DIRECT;
#endif
+#ifndef O_NOATIME
+# define O_NOATIME 01000000
+#endif
+ flags |= O_NOATIME;
+
if ((dev->fd = open(name, flags, 0777)) < 0) {
log_sys_error("open", name);
return 0;
next reply other threads:[~2004-09-10 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 12:47 Jeff Mahoney [this message]
2004-09-11 21:13 ` [linux-lvm] [PATCH] Fix for hanging resize on root filesystem Alasdair G Kergon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4141A25C.70701@suse.com \
--to=jeffm@suse.com \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.