public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Eric Sandeen <sandeen@redhat.com>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	tytso@mit.edu, jack@suse.cz, sct@redhat.com,
	akpm@linux-foundation.org, adilger@sun.com,
	linux-ext4@vger.kernel.org
Subject: Re: ext3 read only handling
Date: Tue, 27 Jan 2009 10:56:26 +0100	[thread overview]
Message-ID: <20090127095626.GB18449@elf.ucw.cz> (raw)
In-Reply-To: <48DBAB0E.3090608@redhat.com>

On Thu 2008-09-25 10:15:26, Eric Sandeen wrote:
> Pavel Machek wrote:
> > Inserting read-only ext3 SD card into a machine and trying to mount
> > ext3 volume on it is very unnice :-(.
> > 
> > Is there easy way to "fix" -oro so that it does not write to the
> > media?
> > 
> > (Machine died after I played with that SD card a bit more, but I can't
> > easily reproduce that...)
> 
> Is the block device recognized as readonly?
> 
> ext3_load_journal() does things like:
> 
>         really_read_only = bdev_read_only(sb->s_bdev);
> ...
>                         printk(KERN_INFO "EXT3-fs: INFO: recovery "
>                                         "required on readonly
> filesystem.\n");
>                         if (really_read_only) {
>                                 printk(KERN_ERR "EXT3-fs: write access "
>                                         "unavailable, cannot proceed.\n");
>                                 return -EROFS;
>                         }
> 
> so it shouldn't have tried to replay the log ...
> 
> (replaying the log & writing to the device on a read-only mount is
> another issue, but the behavior today is *supposed* to be such that if
> you cannot write to the device, then even a read-only mount with a dirty
> journal should fail gracefully, not explode ....)

Well, that card is so broken I'm afraid to insert it into machine any
more. I had hard time removing it on last attempt. But these days at
least "ro,noload" is documented, so... 

								Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      reply	other threads:[~2009-01-27  9:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-25 15:03 ext3 read only handling Pavel Machek
2008-09-25 15:15 ` Eric Sandeen
2009-01-27  9:56   ` Pavel Machek [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=20090127095626.GB18449@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=adilger@sun.com \
    --cc=akpm@linux-foundation.org \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=sct@redhat.com \
    --cc=tytso@mit.edu \
    /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