All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duane Griffin <duaneg@dghda.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Alexey Fisher <bug-track@fisher-privat.net>,
	Greg Freemyer <greg.freemyer@gmail.com>,
	Ted Augustine <taugustine@techpathways.com>,
	linux-ext4@vger.kernel.org
Subject: Re: xt4 - True Readonly mount [WAS - Re: [Bug 14354] Bad corruption with 2.6.32-rc1 and upwards]
Date: Fri, 30 Oct 2009 17:43:14 +0000	[thread overview]
Message-ID: <e9e943910910301043n3e5e8816y74286b0c159a8a78@mail.gmail.com> (raw)
In-Reply-To: <4AEB1E9E.9020408@redhat.com>

2009/10/30 Eric Sandeen <sandeen@redhat.com>:
> Alexey Fisher wrote:
>> Hmm... bdev. any chance to do temporary recovery and load it as external
>> journal if ro used? Anyway, you already pointed me to hdparm, so i can
>> use it too.
>
> There were patches floated to in-ram recovery for those blocks so that you
> could have a consistent fs w/o touching the disk but it didn't seem to get
> far.

Those were mine, I think. I got stuck at the point of needing to
handle escaped blocks -- I couldn't find any way of reliably and
efficiently getting hold of a buffer after it had been read from disk
but before anybody else had a chance to access it. I think if I could
have cracked that then I could have got it working. The only other
missing piece of functionality was handling the transition from
read-only (unrecovered) to read-write.

It would have needed a very thorough audit of the places where ext3
was doing ll_rw_block and such like, though.

Cheers,
Duane.

-- 
"I never could learn to drink that blood and call it wine" - Bob Dylan

  reply	other threads:[~2009-10-30 17:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-30 14:20 xt4 - True Readonly mount [WAS - Re: [Bug 14354] Bad corruption with 2.6.32-rc1 and upwards] Greg Freemyer
2009-10-30 15:14 ` Eric Sandeen
2009-10-30 15:31   ` Alexey Fisher
2009-10-30 16:14     ` Eric Sandeen
2009-10-30 16:52       ` Alexey Fisher
2009-10-30 17:13         ` Eric Sandeen
2009-10-30 17:43           ` Duane Griffin [this message]
2009-10-30 15:47 ` Alexey Fisher
2009-11-01  5:45 ` Theodore Tso
2009-11-02 21:59   ` Greg Freemyer
2009-11-02 22:53     ` Andreas Dilger
2009-11-02 23:02       ` Eric Sandeen
2009-11-04  8:05         ` Andreas Dilger
2009-11-04 16:20           ` Eric Sandeen
2009-11-03 13:52     ` Theodore Tso

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=e9e943910910301043n3e5e8816y74286b0c159a8a78@mail.gmail.com \
    --to=duaneg@dghda.com \
    --cc=bug-track@fisher-privat.net \
    --cc=greg.freemyer@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=taugustine@techpathways.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 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.