From: Paul van Gool <paul.vangool@rinconnetworks.com>
To: Vikram Mehta <vm6580@hotmail.com>
Cc: mtd <linux-mtd@lists.infradead.org>
Cc: "Uclinux-Dev@Uclinux.Org" <uclinux-dev@uclinux.org>
Subject: Re: JFFs2 usage questions
Date: Fri, 27 Jun 2003 06:18:48 -0700 [thread overview]
Message-ID: <20030627131848.GA3947@rinconnetworks.com> (raw)
In-Reply-To: <Law14-OE23bdHd2V4MT00030545@hotmail.com>
On Thu, Jun 26, 2003 at 01:31:10AM -0700, Vikram Mehta wrote:
> 1.) I cannot mkdir into the folder. I mount dev/mtdblock2 on /mnt.
> If I do mkdir , the message comes
> no space left on device
I had a similar problem earlier this week and asked the list. In my case
the reason was that I didn't have enough erase blocks available for the GC
algorithm to be able to do its job. Make sure you have at least 5 erase
blocks available when you create the JFFS2 image.
> 2.) if I reboot the system /mnt is left as empty.
Did you verify the mount command gets executed during boot? Just add an
echo to the rc script and verify you see its output while rebooting.
Hope this helps.
Paul
> 3.) How can I provide that 1or 2 of my partions are readonly. That is they
> are not erased
>
> 4.) I want that after booting, one partition is created as Jffs2. ( I can
> add the commands in rc) and I can write on it like on do on /var which is
> mounted on RAM
>
> Regards
> Vikram
>
>
>
>
>
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
--
Paul van Gool Rincon Networks
paul.vangool@rinconnetworks.com (805)-705-1442
next prev parent reply other threads:[~2003-06-27 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-26 8:31 JFFs2 usage questions Vikram Mehta
2003-06-27 13:18 ` Paul van Gool [this message]
2003-06-27 14:49 ` yong_guo@scomcenter.com
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=20030627131848.GA3947@rinconnetworks.com \
--to=paul.vangool@rinconnetworks.com \
--cc=linux-mtd@lists.infradead.org \
--cc=vm6580@hotmail.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