From: "Mattias Rönnblom" <hofors@lysator.liu.se>
To: linux-kernel@vger.kernel.org
Subject: VFAT truncate performance
Date: 05 Sep 2006 15:52:46 +0200 [thread overview]
Message-ID: <m3mz9e5sk1.fsf@isengard.friendlyfire.se> (raw)
Hi,
extending files by ftruncate(2) runs very slow on VFAT file
systems. On my USB harddisk w/ VFAT, it takes 14 seconds to extend an
empty file to 1 GB. On a memory stick, it takes well over 4 minutes.
My question is: is this problem on the conceptual level (ie there is
no way of extending files on FAT that doesn't involve many disk
operations) or is the current Linux fs driver suboptimal in this
respect?
The reason for asking is that I run Samba which service files on USB
devices (w/ VFAT for portability) to Windows XP clients. When copying
files to the Samba server, Microsoft SMB clients seem to extend the
file before actually starting to copy the data. This results in
sluggishness and timeouts when copying large files to VFAT
filesystems.
Thanks,
Mattias
next reply other threads:[~2006-09-05 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 13:52 Mattias Rönnblom [this message]
2006-09-05 14:55 ` Xavier Bestel
2006-09-05 15:38 ` Mattias Rönnblom
2006-09-05 14:59 ` OGAWA Hirofumi
[not found] <6RJD8-3i0-1@gated-at.bofh.it>
2006-09-05 19:38 ` 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=m3mz9e5sk1.fsf@isengard.friendlyfire.se \
--to=hofors@lysator.liu.se \
--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
Powered by JetHome