From: "Jörn Engel" <joern@logfs.org>
To: srimugunthan dhandapani <srimugunthan.dhandapani@gmail.com>
Cc: linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org
Subject: Re: logfs: max 4K writepage size
Date: Wed, 7 Sep 2011 21:17:41 +0200 [thread overview]
Message-ID: <20110907191741.GO32018@logfs.org> (raw)
In-Reply-To: <CAMjNe_fd8S08SG45kOASDkUFPMuT0WoOHZ1cGnTqk5pKj7DxgA@mail.gmail.com>
On Wed, 7 September 2011 23:00:30 +0530, srimugunthan dhandapani wrote:
>
> I was able to do basic mount-copy-unmount once.
> Let me test more with multiple mount unmount cycles and see if there
> are problems.
I'm always happy when I can fix bugs. Though not always happy to
discover that the d*ckhead who created them was me.
> I think we have to give mklogfs /dev/mtdblock0 instead of /dev/mtd0
You can use mtd0 instead of /dev/mtd0, similar to jffs2. Any /dev/foo
gets interpreted by some common code in the kernel. As it's not a
block device, mount fails. mtd0 doesn't start with /dev/, so it must
be special somehow and gets passed to the filesystem. Jffs2 and logfs
are can then do something with this string.
And yes, this sounds really stupid. Having /dev/mtd0 do the right
thing would certainly be less confusing than the current state.
> I updated wikipedia with steps to use logfs
> http://en.wikipedia.org/wiki/LogFS
Cool! Thanks!
Jörn
--
Schrödinger's cat is <BLINK>not</BLINK> dead.
-- Illiad
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-09-07 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-04 10:20 logfs: max 4K writepage size srimugunthan dhandapani
2011-09-07 6:56 ` Jörn Engel
2011-09-07 17:30 ` srimugunthan dhandapani
2011-09-07 19:17 ` Jörn Engel [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=20110907191741.GO32018@logfs.org \
--to=joern@logfs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=srimugunthan.dhandapani@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;
as well as URLs for NNTP newsgroup(s).