From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Sync option destroys flash!
Date: Fri, 13 May 2005 17:59:49 -0600 [thread overview]
Message-ID: <42853F75.8030408@shaw.ca> (raw)
In-Reply-To: <43MVz-2hL-1@gated-at.bofh.it>
Lennart Sorensen wrote:
> Well perhaps what windows does is write the hole file, then update the
> fat, then call sync immediately afterwards, or whenever a file is
> closed, it calls sync on that file's information.
Probably something like that.. Windows does default to disabling write
caching on removable drives, to prevent data loss if a device is removed
without being stopped first, but I think it's quite a bit less
aggressive about updating the FAT than the original poster's description
suggests Linux is doing with the sync option (i.e. only updating after
each user-level write call or something).
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2005-05-14 0:01 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43Ldl-NM-25@gated-at.bofh.it>
[not found] ` <43M9s-1B8-39@gated-at.bofh.it>
[not found] ` <43MCx-1UF-27@gated-at.bofh.it>
[not found] ` <43MVz-2hL-1@gated-at.bofh.it>
2005-05-13 23:59 ` Robert Hancock [this message]
2005-05-18 11:13 Sync option destroys flash! linux
2005-05-18 12:01 ` Richard B. Johnson
[not found] <43UT5-jT-3@gated-at.bofh.it>
2005-05-14 4:34 ` Robert Hancock
-- strict thread matches above, loose matches on Subject: below --
2005-05-14 2:43 linux
2005-05-17 13:36 ` Lennart Sorensen
2005-05-17 20:31 ` linux
2005-05-17 20:43 ` Richard B. Johnson
2005-05-18 13:37 ` Lennart Sorensen
2005-05-13 16:20 Michael H. Warfield
2005-05-13 17:17 ` Lennart Sorensen
2005-05-13 17:53 ` Michael H. Warfield
2005-05-13 18:09 ` Lennart Sorensen
2005-05-13 18:21 ` Michael H. Warfield
2005-05-13 18:26 ` Lennart Sorensen
2005-05-13 18:53 ` Michael H. Warfield
2005-05-13 17:58 ` Zan Lynx
2005-05-13 18:13 ` Lennart Sorensen
2005-05-13 18:40 ` Alan Cox
2005-05-13 19:10 ` Michael H. Warfield
2005-05-13 22:00 ` Alan Cox
2005-05-13 22:22 ` Måns Rullgård
2005-05-13 23:24 ` Jon Masters
2005-05-13 23:01 ` Jeffrey Hundstad
2005-05-13 23:27 ` Jon Masters
2005-05-14 10:17 ` Jörn Engel
2005-05-14 1:05 ` Michael H. Warfield
2005-05-17 13:30 ` Lennart Sorensen
2005-05-13 21:25 ` Lee Revell
2005-05-13 22:43 ` Alan Cox
2005-05-15 19:00 ` Denis Vlasenko
2005-05-16 0:23 ` Mark Lord
2005-05-16 9:29 ` David Woodhouse
2005-05-16 16:42 ` Pavel Machek
2005-05-16 13:01 ` Richard B. Johnson
2005-05-16 23:18 ` Helge Hafting
2005-05-18 7:03 ` Denis Vlasenko
2005-05-17 7:59 ` Colin Leroy
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=42853F75.8030408@shaw.ca \
--to=hancockr@shaw.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.