From: Brian Waite <waite@skycomputers.com>
To: munro.biswal@smartbridges.com, linux-mtd@lists.infradead.org
Subject: Re: Read only jffs2 filesystem
Date: Thu, 20 May 2004 08:33:05 -0400 [thread overview]
Message-ID: <200405200833.05829.waite@skycomputers.com> (raw)
In-Reply-To: <40AC99E1.40904@smartbridges.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I think the default mount options are ro for mtd. To change this, , you can do
2 things:
1) On the Linux cmdline root=/dev/mtdblockN rw
2) From the prompt/init scripts: mount -oremount,rw -t jffs2 /dev/mtdblockN /
Or you may have set the partitions to be read only oin the MTD map you
created. (Check the mask_flags)
Finally, depending on your FLASH chips, the chips may always powerup in the
Locked state, mine do, and you will need to unlock them before writing. I do
thins under u-boot but iy could also be done with the unlock mtd command.
Those are my suggestions.
Thanks
Brian
On Thursday 20 May 2004 07:43 am, Munro Biswal wrote:
> Iam using a 6 MTD partition structure wherein i have two jffs2
> filesystems and when i boot up, it mounts the filesystem as
> readonly.Even if i reboot my board, i get the root filesystem to be
> mounted readonly.
> I cannot write anything to the filesystem
> What could be the problem??
>
>
> Thanks in advance!
> Regards,
> Munro.
>
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQFArKWBmxLCz0u+Ko8RAkvjAKCltIjy5NZBFoe4/VsYrD46TuxQbgCfbYIX
yr3/q4S8Juq4vFXF6HOr7Co=
=2hU/
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2004-05-20 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 11:43 Read only jffs2 filesystem Munro Biswal
2004-05-20 12:33 ` Brian Waite [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=200405200833.05829.waite@skycomputers.com \
--to=waite@skycomputers.com \
--cc=linux-mtd@lists.infradead.org \
--cc=munro.biswal@smartbridges.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