From: Stephen Hemminger <shemminger@vyatta.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Mount -o sync regression in 2.6.31
Date: Wed, 11 Nov 2009 12:33:40 -0800 [thread overview]
Message-ID: <20091111123340.703f5c86@nehalam> (raw)
One of the configurations supported in our specialized distribution is using
floppy to store configuration information (and live cd for everything else).
The floppy is mounted with '-o sync' so that if floppy is removed the files
are still updated. The floppy is formatted with ext2 filesystem.
This broke somewhere between 2.6.30 and 2.6.31-rc1, and was caught by our
release regression system (with VMware pseudo-floppys) but it is easily
reproducible with real hardware.
The following sequence demonstrates this:
# mount /dev/fd0 /mnt -o sync,noatime,noexec,nosuid
# cp /etc/motd /mnt/motd.$$
(Manually eject floppy)
# umount /mnt
(I/O errors occur)
With -o sync, all I/O should have been completed when the copy was done.
This may also effect people using -o sync on USB thumb drives as well.
I tried the obvious bisection, but git bisect seems to wonder off into the
weeds now. There is no reason that bisecting between v2.6.30 and v2.6.31-rc1
should go off into v2.6.30-rc2
next reply other threads:[~2009-11-11 20:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 20:33 Stephen Hemminger [this message]
2009-11-11 21:34 ` Mount -o sync regression in 2.6.31 Frans Pop
2009-11-11 22:20 ` Stephen Hemminger
2009-11-13 22:47 ` Stephen Hemminger
2009-11-13 23:07 ` Andrew Morton
2009-11-13 23:28 ` Stephen Hemminger
2009-11-17 0:04 ` [PATCH] ext2: clear uptodate flag on super block I/O error Stephen Hemminger
2009-11-17 2:08 ` Nick Piggin
2009-11-17 17:16 ` Stephen Hemminger
2009-11-14 13:18 ` Mount -o sync regression in 2.6.31 Frederic Weisbecker
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=20091111123340.703f5c86@nehalam \
--to=shemminger@vyatta.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox