All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gordon J Milne <gordon@bluewatersys.com>
To: linux-mtd@lists.infradead.org
Subject: Re: "Read-only file system" error while writing
Date: Wed, 21 May 2003 23:33:32 +1200	[thread overview]
Message-ID: <3ECB640C.5040305@bluewatersys.com> (raw)
In-Reply-To: <14660.1028067926@redhat.com>

Hi

David Woodhouse wrote:
 > gromit1463@mailworks.org said:
 >
 >>When I write to the chips using either cat, dd, stdout redirection, or
 >>cp, the CFI driver complains of attempting to write to a "Read-only
 >>file system", even after unlocking all blocks in the partition and
 >>erasing the partition.  I can mount /dev/mtdblock*, but mount
 >>complains and I still can't put anything into the mounted partition.
 >>do_write_buffer() in cfi_cmdset_0001.c is returning the error (EROFS).
 >
 > The only case in which do_write_buffer() should return -EROFS is if the
 > status bit is set which means that the block in question was locked. Try
 > using the MEMUNLOCK ioctl to unlock it?

I am having exactly the same problem with the same ST part (M28W320CB). I am 
running uClinux (based on Linux 2.4.20). I modified the do_write_buffer() 
code to print out the status value that was read back. The value is 0xffff. 
It seems a bit strange to me that ALL the bist should be 1s.

I have tried using "unlock" to unlock the device (/dev/mtd3) but I get the 
same result.

The device (1f:03) is the root device and it has been remounted rw. I 
verified this by checking /proc/mounts - everything was rw, as expected. My 
system successfully boots and I can execute commands. It is just the 
filesystem writes that are not working for me.

Any further ideas?

Gordon

  parent reply	other threads:[~2003-05-21 11:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-30 21:27 "Read-only file system" error while writing Stephen Hui
2002-07-30 22:25 ` David Woodhouse
2002-07-31 11:53   ` Jörn Engel
2003-05-21 11:33   ` Gordon J Milne [this message]
2003-05-21 14:18     ` Thayne Harbaugh
2003-05-22 21:57     ` Gordon J Milne
2002-07-31 15:35 ` Stuart Menefy
2002-07-31 20:24   ` Stephen Hui
2002-08-01 10:31     ` David Woodhouse
2002-08-01 18:05       ` Stuart Menefy
2002-08-01 18:26         ` Stuart Menefy
2002-08-01 19:45           ` Stephen Hui
2002-08-01 22:37             ` Stuart Menefy
2002-08-02 14:46               ` Stephen Hui
2002-08-01 10:35   ` David Woodhouse

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=3ECB640C.5040305@bluewatersys.com \
    --to=gordon@bluewatersys.com \
    --cc=linux-mtd@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.