From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: Thanasis <thanasis@asyr.hopto.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: jffs2 and kernel config for SDHC Memory Cards
Date: Fri, 6 Mar 2009 22:57:46 +0000 [thread overview]
Message-ID: <20090306225746.GB25593@silver.sucs.org> (raw)
In-Reply-To: <49B18679.4030504@asyr.hopto.org>
On Fri, Mar 06, 2009 at 10:24:25PM +0200, Thanasis wrote:
> on 03/06/2009 08:24 PM Sitsofe Wheeler wrote the following:
> > On Fri, Mar 06, 2009 at 03:56:01PM +0200, Thanasis wrote:
> >> on 03/06/2009 03:39 PM Thanasis wrote the following:
> >>> I want to use two of these Transcend’s Class 6 SDHC (SD High-Capacity)
> >>> Memory Cards,
> >>> http://www.transcendusa.com/Products/ModDetail.asp?ModNo=147&LangNo=0&Func1No=1&Func2No=13
> >>> as part of the filesystem in a netbook (Acer A110L), will mount /home on
> >>> one, and /tmp and /var on the other.
> >
> >> Let me rephrase my questions in order to be clearer:
> >> Q1: In order to achieve wear leveling should I format them as jffs2?
> >
> > This probably won't be very effective as you are already past the
> OK. I believe I should stick to ext2, right?
If you mean compared to jffs2 then probably yes, better to stick with
ext2. If you mean is ext2 the best choice over anything else... well
that's an open question (or so I'm told). You would need to ask a
filesystem expert really but it apparently depends on the workload, the
characteristics of the "disks" and whether you need journaling.
--
Sitsofe | http://sucs.org/~sits/
next prev parent reply other threads:[~2009-03-06 22:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 13:39 Thanasis
2009-03-06 13:56 ` Thanasis
2009-03-06 18:24 ` Sitsofe Wheeler
2009-03-06 20:24 ` Thanasis
2009-03-06 22:57 ` Sitsofe Wheeler [this message]
2009-03-07 16:59 ` Thanasis
2009-03-10 11:23 ` Pavel Machek
2009-03-10 22:05 ` Thanasis
2009-03-15 21:18 ` Pavel Machek
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=20090306225746.GB25593@silver.sucs.org \
--to=sitsofe@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thanasis@asyr.hopto.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
all inboxes | Powered by JetHome®