From: Just Marc <marc@corky.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: file system for solid state disks
Date: Thu, 30 Aug 2007 19:26:47 +0100 [thread overview]
Message-ID: <46D70BE7.2020503@corky.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0708302024320.24730@fbirervta.pbzchgretzou.qr>
One must consult the documentation of that device. This wear leveling
is low level and most devices do not export any information about it.
Recent SSDs start to export some values through SMART that let you
monitor the state.
Some companies think that hiding is better than exposing...
Jan Engelhardt wrote:
> On Aug 25 2007 09:41, Just Marc wrote:
>
>> On SSDs which contain built in wear leveling, pretty much any file
>> system can be used. For SSDs that lack such low level housekeeping,
>> use stuff like JFFS2.
>>
>
> The question is, how can you find out whether it does automatic
> wear-leveling? (Perhaps when a CF is advertised as "holds 10 years!"?)
>
>
> Jan
>
next prev parent reply other threads:[~2007-08-30 18:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-25 8:41 file system for solid state disks Just Marc
2007-08-30 18:25 ` Jan Engelhardt
2007-08-30 18:26 ` Just Marc [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-23 8:55 Daniel J Blueman
2007-08-23 12:45 ` James Courtier-Dutton
2007-08-23 12:56 ` Daniel J Blueman
[not found] ` <20070823134359.GB5576@mail.ustc.edu.cn>
2007-08-23 13:43 ` Fengguang Wu
2007-08-23 15:09 ` Daniel J Blueman
2007-09-05 12:34 ` Denys Vlasenko
2007-09-05 12:56 ` linux-os (Dick Johnson)
2007-09-05 13:04 ` Manu Abraham
2007-08-23 5:01 Richard Ballantyne
2007-08-23 5:52 ` Jan Engelhardt
2007-08-23 10:26 ` Theodore Tso
2007-08-23 11:25 ` Jens Axboe
2007-08-29 17:36 ` Bill Davidsen
2007-08-29 17:57 ` Jens Axboe
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=46D70BE7.2020503@corky.net \
--to=marc@corky.net \
--cc=jengelh@computergmbh.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox