All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [patch] grub incorrectly identifies ext3 as fat
Date: Fri, 30 Oct 2009 19:57:59 +0100	[thread overview]
Message-ID: <20091030185759.GA30150@thorin> (raw)
In-Reply-To: <57a6d2110910290758i23de79c1y2b87513f674023b@mail.gmail.com>

On Thu, Oct 29, 2009 at 02:58:09PM +0000, Andrew Clausen wrote:
> Hi all,
> 
> grub (both the boot loader, and grub-probe) incorrectly identifies my
> ext3 partition as containing a fat file system. This means it can't
> boot without manual tweaking.  The problem is caused by stale fat
> signatures... this is probably a common problem, as mke2fs often
> doesn't wipe old signatures.
> 
> I wrote a patch.  In order for a file system to be considered
> detected, dir() must not only succeed, it also must find at least one
> file or directory. This is pretty effective at ruling out misdetecting
> a filesystem based on a stale signature that wasn't wiped by mkfs.

We already had code for this, see:

2009-09-05  Robert Millan  <rmh.grub@aybabtu.com>

        * util/grub-probe.c (probe): Comment out buggy codepath, which  
        was unexpectedly enabled by Colin Watson's 2009-09-02 fix.  This
        should be re-enabled after 1.97.

> This shouldn't have any collateral damage, because empty file systems
> are useless to Grub.

Unlike the filesystem driver, grub-probe already knows we want to probe for
a file.  Then this assumption won't be necessary.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



  reply	other threads:[~2009-10-30 18:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-29 14:58 [patch] grub incorrectly identifies ext3 as fat Andrew Clausen
2009-10-30 18:57 ` Robert Millan [this message]
2009-10-30 19:06   ` Felix Zielcke
2009-10-30 19:19   ` Andrew Clausen
2009-10-30 22:46     ` Robert Millan
2009-10-31  6:44       ` Andrew Clausen
2009-10-31 10:04         ` Felix Zielcke
2009-10-31 15:39           ` Andrew Clausen
2009-10-31 16:06             ` Robert Millan
2009-10-31 18:43               ` Andrew Clausen
2009-10-31 18:52                 ` Vladimir 'phcoder' Serbinenko
2009-11-11 16:28                   ` Andrew Clausen
2009-10-31 19:15                 ` Robert Millan
2009-11-09 23:14                   ` Robert Millan
2009-11-11 17:24                     ` Andrew Clausen
2009-10-31 18:02           ` rubisher
2009-10-31 18:46             ` Felix Zielcke
2009-10-31 10:10         ` Robert Millan
2009-10-31 10:34           ` Felix Zielcke
2009-10-31 11:30             ` Robert Millan
2009-10-31 11:38               ` Felix Zielcke
2009-10-31 18:31                 ` Robert Millan

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=20091030185759.GA30150@thorin \
    --to=rmh@aybabtu.com \
    --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.