From: Bodo Eggert <harvested.in.lkml@7eggert.dyndns.org>
To: Patrick Fritzsch <fritzsch@cip.physik.uni-muenchen.de>,
Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org
Subject: Re: slow sync of fat 32 hotplugged devices
Date: Fri, 16 Dec 2005 06:48:04 +0100 [thread overview]
Message-ID: <E1En8Rp-00050N-Gk@be1.lrz> (raw)
In-Reply-To: <5k61N-oO-5@gated-at.bofh.it>
Patrick Fritzsch <fritzsch@cip.physik.uni-muenchen.de> wrote:
> 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.
[...]
> 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.
The situation is worse: It will update the FAT each time a block is written.
Therefore the FAT area will wear out very quickly.
> 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.
IMO it should sync on committed dentry updates, too.
--
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.
next parent reply other threads:[~2005-12-16 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5k61N-oO-5@gated-at.bofh.it>
2005-12-16 5:48 ` Bodo Eggert [this message]
2005-12-15 18:28 Patrick Fritzsch
2005-12-15 18:35 ` Greg KH
2005-12-17 20:38 ` Andrew Morton
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=E1En8Rp-00050N-Gk@be1.lrz \
--to=harvested.in.lkml@7eggert.dyndns.org \
--cc=7eggert@gmx.de \
--cc=fritzsch@cip.physik.uni-muenchen.de \
--cc=greg@kroah.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
all inboxes | Powered by JetHome®