linux-kernel - Re: ext2 on flash memory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070615163625.GC7747@lazybastard.org>
Date:	Fri, 15 Jun 2007 18:36:25 +0200
From:	Jörn Engel <joern@...fs.org>
To:	Jörn Engel <joern@...fs.org>,
	Linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: ext2 on flash memory

On Fri, 15 June 2007 18:16:44 +0200, DervishD wrote:
> 
>     Yes, I understand. That's worse than I thought. I was right now
> thinking about "PortableApps", a set of free software applications that
> are a little bit modified to work from a pendrive in Windows. Very
> useful, because you can carry your OpenOffice (or AbiWord) and Firefox,
> for example, to any Windows you're doomed to use. This applications
> write repeteadly to the pendrive (specially Firefox...), and I think
> they may wear the drive prematurely if used extensively.

Possibly, yes.  Estimates based on unknown numbers are hard, though.

>     So you have a zone which is unusable. Decent filesystems allow you
> to mark some blocks as "dontuse" (ext2, for example). Does FAT allow
> this?

I don't know.  If things get bad enough that you experience
uncorrectable errors, I'd just trash the stick and get a new one
instead.  Trouble is - with a controller chip doing the error
correction, you have no means of knowing when this happens.

>     I think I will be writing the pendrive, almost fully, once a week
> (enough for an image of my home directory). That means less than 1GiB
> written each week. That means 50-100 (in the worst case, making two
> backups a week instead of one) writings each year in each block.

Writing everything once a week is harmless.  Filling the whole device is
best-case behaviour.  Local hot spots are the problem.

Jörn

-- 
Anything that can go wrong, will.
-- Finagle's Law
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/