[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081011092932.31618741@infradead.org>
Date: Sat, 11 Oct 2008 09:29:32 -0700
From: Arjan van de Ven <arjan@...radead.org>
To: Pavel Machek <pavel@...e.cz>
Cc: Chris Snook <csnook@...hat.com>,
Stefan Monnier <monnier@....umontreal.ca>,
linux-kernel@...r.kernel.org
Subject: Re: Filesystem for block devices using flash storage?
> > Writes to magnetic disks are functionally atomic at the sector
> > level. With SSDs, writing requires an erase followed by rewriting
> > the sectors that aren't changing. This means that an ill-timed
> > power loss can corrupt an entire erase block, which could be up to
> > 256k on some MLC flash. Unless you have a RAID card with a
> > battery-backed write cache, your best bet is probably data
> > journaling. On ext3, you can enable this with the data=journal
> > mount option or the rootflags=data=journal kernel parameter for
> > your root filesystem. It's entirely possible that doing
>
> I don't think ext3 is safe w.r.t. whole eraseblocks disappearing. So
> if you write data 'nearby' root directory and power fails, bye bye
> filesystem, and journal will not help.
>
> Actually ext2 will at least detect damage...
SSDs generally (and ones that are even remotely worth their money for
sure) erase blocks that have no data in them.
They keep empty blocks around, and when they want to erase a block with
"half data", they first move that data to an empty block before erasing
the old block.
This moving around is just a natural part of wear leveling..
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
--
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/
Powered by blists - more mailing lists