All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Artem B. Bityutskiy" <dedekind@yandex.ru>
To: Josh Boyer <jwboyer@gmail.com>
Cc: linux-mtd@lists.infradead.org, Adam Ward <adamward2005@yahoo.co.uk>
Subject: Re: Read only forced on jffs2 by mtd layer?
Date: Fri, 10 Mar 2006 19:05:45 +0300	[thread overview]
Message-ID: <4411A3D9.6050505@yandex.ru> (raw)
In-Reply-To: <625fc13d0603100753r33fde8b8n3b9ff39f24b37b72@mail.gmail.com>

Josh Boyer wrote:
> Sorta.  If there isn't enough physical space to write nodes out, then
> you can't really have a writeable filesystem.  It'll actually just
> return -ENOSPC for everything instead of -EROFS, but the effect is the
> same.
I mean, if I ask to mount read-write, but end-up with RO, this is bad. 
Shouldn't I explicitely request RO mount?


> Take a look at jffs2_calc_trigger_levels in build.c. 
> c->resv_blocks_deletion is the number of blocks needed to delete
> something.  c->resv_blocks_write is the number of blocks needed to
> write something.
Ok, but where is the code that switches it to RO mode in case of lack of 
eraseblocks?

-- 
Best Regards,
Artem B. Bityutskiy,
St.-Petersburg, Russia.

  reply	other threads:[~2006-03-10 16:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-10 13:54 Read only forced on jffs2 by mtd layer? Adam Ward
2006-03-10 15:29 ` Nicolas Pitre
2006-03-10 15:35   ` Josh Boyer
2006-03-10 15:43     ` Artem B. Bityutskiy
2006-03-10 15:53       ` Josh Boyer
2006-03-10 16:05         ` Artem B. Bityutskiy [this message]
2006-03-10 16:21           ` Josh Boyer
2006-03-10 16:28             ` Artem B. Bityutskiy
2006-03-10 16:40             ` Nicolas Pitre
2006-03-11  1:39     ` Adam Ward
2006-03-11  6:37       ` Todd Poynor
2006-03-15 17:47         ` Adam Ward

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=4411A3D9.6050505@yandex.ru \
    --to=dedekind@yandex.ru \
    --cc=adamward2005@yahoo.co.uk \
    --cc=jwboyer@gmail.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.