mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Patrick Fritzsch <fritzsch@cip.physik.uni-muenchen.de>
To: linux-kernel@vger.kernel.org
Subject: slow sync of fat 32 hotplugged devices
Date: Thu, 15 Dec 2005 19:28:09 +0100	[thread overview]
Message-ID: <43A1B5B9.2040307@cip.physik.uni-muenchen.de> (raw)

Hallo,
I checked out suse10 lately and discovered some annoying behaviour in
hotplugging an USB Stick.

It seems that the hal daemon mounts a usbstick in fat32 mode, where
default the sync option ist on. Actually this is a nice behaviour,
because a cp to the stick should last so long until the file was
completly written.

Actually the performance is very bad. A 200 MB file needs around 10
Minutes in sync mode, while it needs around 1 Minute in not synchronous
mode + executing a sync command later.

I guess that the kernel checks after every block of the file, which is
written, if the stick has really written it, which leads to such a big
slowdown. There are already lots of comments of this in the web, where
the solution is always to disable the sync mode in the hal daemon device
files.

Wouldnt it be a nice behaviour, if you could mount a file in a new sync
mode, where it isnt synchronized during writing a file, only when a
close ioctl command was executed on a filehandle?
sync writing to hotplugged devices would be a lot faster then.

greetings,
patrick

             reply	other threads:[~2005-12-15 18:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-15 18:28 Patrick Fritzsch [this message]
2005-12-15 18:35 ` Greg KH
2005-12-17 20:38 ` Andrew Morton
     [not found] <5k61N-oO-5@gated-at.bofh.it>
2005-12-16  5:48 ` Bodo Eggert

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=43A1B5B9.2040307@cip.physik.uni-muenchen.de \
    --to=fritzsch@cip.physik.uni-muenchen.de \
    --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

all inboxes | Powered by JetHome®