From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Raj <inguva@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Delay in unmounting a USB pen drive
Date: Wed, 24 Nov 2004 09:34:06 +0000 [thread overview]
Message-ID: <1101288846.15596.5.camel@imp.csi.cam.ac.uk> (raw)
In-Reply-To: <b2fa632f041124012543876b61@mail.gmail.com>
On Wed, 2004-11-24 at 14:55 +0530, Raj wrote:
> SuSE kernel 2.6.5:
>
> My USB pen drive has a vfat FS. When i transfer some files & try to
> unmount the drive ( umount /mnt ) , the command appears hung. CTRL+C also
> does not work. Only later did i realise that it was actually taking a
> longer time ( 10 - 15 sec )
> to unmount.
>
> My questions are:
> - Why is it taking a long time to unmount ?
> - Is it safe to remove the pen drive from it's slot when the umount is still in
> progress ?? ( I tried this the first time & maybe lucky me, the
> files copied were fine )
You are mounting with async flag (or this is the default) which means
that all the unwritten data is synced when you do umount. You can
verify this by typing "sync" waiting for that to complete and then the
umount should be immediate.
You can change this by using the "sync" option to mount which will cause
data to be written synchronously and the umount will be instantaneous.
Note that this will cause device write to be _much_ slower!
One thing is certain, do NOT unplug before the umount completes or you
will corrupt your fs on the stick for sure.
Best regards,
Anton
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/
next prev parent reply other threads:[~2004-11-24 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 9:25 Raj
2004-11-24 9:34 ` Anton Altaparmakov [this message]
2004-11-24 9:50 ` Raj
2004-11-24 9:38 ` Colin Leroy
2004-11-24 9:52 ` Raj
2004-11-24 10:06 ` Colin Leroy
2004-11-24 10:17 ` bert hubert
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=1101288846.15596.5.camel@imp.csi.cam.ac.uk \
--to=aia21@cam.ac.uk \
--cc=inguva@gmail.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®