public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Raffaele BELARDI <raffaele.belardi@st.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64]  Re: boot Gentoo from USB key
Date: Tue, 06 May 2008 15:18:01 +0200	[thread overview]
Message-ID: <1210079881.6197.36.camel@ws2912.agr.st.com> (raw)
In-Reply-To: <1209976727.6344.16.camel@ws2912.agr.st.com>

On Mon, 2008-05-05 at 10:38 +0200, Raffaele Belardi wrote:
> On Fri, 2008-05-02 at 11:33 -0400, Drake Donahue wrote:
> > >
> > > If I'm correct you're running into the ext3 large inode issue.  Briefly,
> > > old versions used 128 byte inodes, while newer versions use 256 byte
> > > inodes by default, in ordered to be ready for the improvements coming in
> > > ext4.  The problem is that legacy grub doesn't support the larger inodes,
> > > and isn't being developed any longer so that isn't going to change, while
> > > new grub isn't even scheduled for format compatibility stability until
> > > late this year!
> > >
> 
> > An interesting find. Were the inodes for ext2 also defaulted to 256 or only 
> > those for ext3? This question relevant as Raffaele only talked about using 
> > ext2 and vfat partitions on the pen drive. In a quick search I found no 
> > indications. If ext2 inode structure was also changed much more should be 
> > heard about this.
> > 
> 
> I confirm that by default mkfs.ext2 created 256 byte inodes so I'm
> positive about Duncan's suggestion. I'll try to re-create the partition
> forcing inode size to 128. I'm using stable amd64 system, updated a
> couple of weeks ago.

I confirm that passing -I 128 to mkfs.ext2 fixes the problem, now grub
finds the stage files and installs happily on the ext2 partition.

thanks again,

raf

-- 
gentoo-amd64@lists.gentoo.org mailing list



  reply	other threads:[~2008-05-06 13:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30  6:43 [gentoo-amd64] boot Gentoo from USB key Raffaele BELARDI
2008-04-30  6:49 ` Kyle Liddell
2008-04-30  6:56 ` Branko Badrljica
2008-04-30  7:44   ` Raffaele BELARDI
2008-05-05  8:40     ` Raffaele BELARDI
2008-04-30 10:47 ` [gentoo-amd64] " Duncan
2008-04-30 12:35 ` [gentoo-amd64] " Jason
2008-04-30 14:29   ` Branko Badrljica
2008-04-30 14:47     ` Jason
2008-04-30 15:05       ` Branko Badrljica
2008-04-30 15:40         ` Jason
2008-04-30 15:55           ` Branko Badrljica
2008-05-05  8:53           ` Raffaele BELARDI
2008-04-30 17:39 ` Hernan Lopez
2008-04-30 17:58   ` Branko Badrljica
2008-05-01  7:26     ` Branko Badrljica
2008-04-30 18:03 ` Drake Donahue
2008-04-30 18:21   ` Drake Donahue
2008-05-02 11:22 ` [gentoo-amd64] " Duncan
2008-05-02 15:33   ` Drake Donahue
2008-05-05  8:38     ` Raffaele BELARDI
2008-05-06 13:18       ` Raffaele BELARDI [this message]
2008-05-06 17:08         ` Duncan

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=1210079881.6197.36.camel@ws2912.agr.st.com \
    --to=raffaele.belardi@st.com \
    --cc=gentoo-amd64@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox