All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: regression in fs/ext2.c
Date: Wed, 04 Jun 2008 18:38:58 -0400	[thread overview]
Message-ID: <1212619138.20351.32.camel@dv> (raw)
In-Reply-To: <20080604221257.GA23843@thorin>

On Thu, 2008-06-05 at 00:12 +0200, Robert Millan wrote:
> The following commit:
> 
> 2008-05-20  Bean  <bean123ch@gmail.com>
> 
> introduced a regression in fs/ext2.c.  The effect is that when attempting
> to access an ext2 filesystem from grub-emu (and AFAICT only from grub-emu),
> it will spend a lot of time (a minute or so) in a loop that calls lseek()
> repeatedly (with increasingly higher offsets).
> 
> I'm sorry, I spent a while looking into this, but haven't been able to
> find the source of the problem.

Actually I noticed that grub won't work in qemu anymore.  I would
normally do this:

qemu -hda /dev/sda

and that would show the menu.  Sometimes the menu would be old, but
running "grub-install /dev/sda" would synchronize the cache.

In the recent days, grub would simply hang or report "out of partition".
I was installing Fedora 9 around that time, so I blamed it on qemu
changes.  But now I did a bisect in git, and sure enough, it pointed
exactly to that change from May 20.

It looks like grub has problems accessing mounted filesystem.  That's a
problem because the OS can reboot suddenly, leaving the filesystem in a
state that grub cannot grok.

I'm using ext3 everywhere, so I suspect that the problem may have to do
with the journal support implemented in that commit.

-- 
Regards,
Pavel Roskin



  reply	other threads:[~2008-06-04 22:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-04 22:12 regression in fs/ext2.c Robert Millan
2008-06-04 22:38 ` Pavel Roskin [this message]
2008-06-05  5:30   ` Bean

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=1212619138.20351.32.camel@dv \
    --to=proski@gnu.org \
    --cc=grub-devel@gnu.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.