public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan@linuxholdings.co.za>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] udev and usb stick/hdd
Date: Mon, 23 Jul 2007 20:58:53 +0200	[thread overview]
Message-ID: <200707232058.53523.alan@linuxholdings.co.za> (raw)
In-Reply-To: <106573.2621.qm@web31704.mail.mud.yahoo.com>

On Monday 23 July 2007, maxim wexler wrote:
> > Which will destroy your flash device in as little as
> > a couple of months
> > (voice of experience here), and it probably the
> > reason the option was
> > removed.
>
> Ulp! Here's my line from fstab:
>
> /dev/sdb1       /usb    auto
> noauto,user,rw,exec,sync        0 0
>
> Copied from a forum somewhere. For use of my mp3
> player and digi-camera, both formatted vfat. Does
> 'noauto' cancel 'sync'? This way un/mounting must be
> done manually. Does that spare me?

No. read 'man mount'

In a nutshell, noauto means the device will not be automativcally 
mounted at boot time when the init script runs.
sync is a different beast - it means that "All I/O to the file system 
should be done synchronously." That means that when the kernel say to 
write to the device, it does get written, and not cached somewhere. 
Caching it and returning the correct result to indicate that the write 
was completed would be of course 'async'

> I haven't noticed any problems yet. Are you saying
> that the damage is incremental, that it accumulates
> until a certain point is reached and the device is
> kaput?

It's only a matter of time and relates to how flash devices work. After 
many many writes to the same storage cell, it degrades. The good ones 
are rated to about 100,000 writes per cell. The cheap and nasty ones 
can be as low as 10,000 writes. You would be amazed how quickly 50,000 
writes can happen to the same cell when used as swap for example

This is a known issue with flash devices. The correct solution is to 
ONLY write to the device once you are ready to unmount it. Treat it 
much like a CD and you'll be OK

alan

-- 
Optimists say the glass is half full,
Pessimists say the glass is half empty,
Developers say wtf is the glass twice as big as it needs to be?

Alan McKinnon
alan at linuxholdings dot co dot za
+27 82, double three seven, one nine three five
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-07-23 18:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-21 13:19 [gentoo-user] udev and usb stick/hdd Aleksey V. Kunitskiy
2007-07-21 14:15 ` Dirk Heinrichs
2007-07-21 15:16   ` Aleksey V. Kunitskiy
2007-07-22  7:20     ` Dirk Heinrichs
2007-07-22 14:27       ` Crayon Shin Chan
2007-07-22 20:10     ` Neil Bothwick
2007-07-23 18:12       ` maxim wexler
2007-07-23 18:58         ` Alan McKinnon [this message]
2007-07-23 20:21           ` Neil Bothwick
2007-07-24 13:03             ` Crayon Shin Chan
2007-07-24 14:48               ` Neil Bothwick

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=200707232058.53523.alan@linuxholdings.co.za \
    --to=alan@linuxholdings.co.za \
    --cc=gentoo-user@lists.gentoo.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