From: Andi Kleen <andi@firstfloor.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Yedire\, Sandeep" <syedire@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Ext2/3 Filesystem Analysis
Date: Wed, 09 Jun 2010 14:06:55 +0200 [thread overview]
Message-ID: <87wru84dgg.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20100609105802.62d2ddce@lxorguk.ukuu.org.uk> (Alan Cox's message of "Wed\, 9 Jun 2010 10\:58\:02 +0100")
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
>> With Ext3:
>> Filesystem block at Sector 0 is being updated more frequently at ratio
>> of 5.5 to 6 times that of data block.
>> Filesystem block(super block copies) are being updated at around
>> 1.5times the frequency compared to data block.
>>
>> Has anyone come across this kind of behaviour with these filesystems
>> on NAND Flash?
>
> ext2/3 are not intended to be used with flash - they do not wear level,
Or rather not intended to be used with flash that does not have
an own wear level layer.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2010-06-09 12:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 9:41 Ext2/3 Filesystem Analysis Yedire, Sandeep
2010-06-09 9:58 ` Alan Cox
2010-06-09 12:06 ` Andi Kleen [this message]
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=87wru84dgg.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=syedire@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox