From: Lee Revell <rlrevell@joe-job.com>
To: mhw@wittsend.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Sync option destroys flash!
Date: Fri, 13 May 2005 17:25:00 -0400 [thread overview]
Message-ID: <1116019500.6380.33.camel@mindpipe> (raw)
In-Reply-To: <1116001207.5239.38.camel@localhost.localdomain>
On Fri, 2005-05-13 at 12:20 -0400, Michael H. Warfield wrote:
> Under the right circumstances, even copying a single file to a flash
> drive mounted with the "sync" option can destroy the entire drive!
>
> Now that I have your attention!
>
> I found this out the hard way. (Kissed one brand new $70 USD 1GB flash
> drive good-bye.) According to the man pages for mount, FAT and VFAT
> file systems ignore the "sync" option. It lies.
I guess you found out the hard way that the vast majority of Linux docs
are 2-3 years out of date...
> On a real hard
> drive, this will cause "head resonances" as the heads go through
> constant high speed seeks between the cylinder with the FAT tables and
> the data cylinders. That can't be good, on a continuous basis, for
> drive life. But it's really a disaster for flash memory.
I have seen a clueless sysadmin destroy several 15,000 RPM SCSI drives
this way by putting the syslog partition and mail spool at opposite ends
of the drive. I think Alan Cox said something like "these days you can
no longer assume that buggy software won't destroy your hardware".
Lee
next prev parent reply other threads:[~2005-05-13 21:25 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 16:20 Sync option destroys flash! 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:52 ` Flash device types Mark Rustad
2005-05-13 18:53 ` Sync option destroys flash! 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 [this message]
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
[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
-- 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
[not found] <43UT5-jT-3@gated-at.bofh.it>
2005-05-14 4:34 ` Robert Hancock
2005-05-18 11:13 linux
2005-05-18 12:01 ` Richard B. Johnson
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=1116019500.6380.33.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhw@wittsend.com \
/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.