mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mattias Rönnblom" <hofors@lysator.liu.se>
To: Xavier Bestel <xavier.bestel@free.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VFAT truncate performance
Date: 05 Sep 2006 17:38:48 +0200	[thread overview]
Message-ID: <m3fyf65nnb.fsf@isengard.friendlyfire.se> (raw)
In-Reply-To: <1157468114.1435.216.camel@capoeira>

Xavier Bestel <xavier.bestel@free.fr> writes:

> On Tue, 2006-09-05 at 15:52, Mattias Rönnblom wrote:
> > 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.
> 
> Is your USB stick mounted -o sync ? If that's the case, the truncate()
> and write() won't be merged so they will take twice as long. -o sync
> generally kills performance on USB sticks.
> 

No, 'async'.

Regards,
        Mattias


  reply	other threads:[~2006-09-05 15:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-05 13:52 Mattias Rönnblom
2006-09-05 14:55 ` Xavier Bestel
2006-09-05 15:38   ` Mattias Rönnblom [this message]
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=m3fyf65nnb.fsf@isengard.friendlyfire.se \
    --to=hofors@lysator.liu.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xavier.bestel@free.fr \
    /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