All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Helge Deller <deller@gmx.de>, Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: Do NOT upgrade to palo v2.10
Date: Wed, 31 Jul 2019 07:45:28 -0700	[thread overview]
Message-ID: <1564584328.3319.5.camel@HansenPartnership.com> (raw)
In-Reply-To: <a9b20c26-d334-5626-5c59-8942879e374c@gmx.de>

On Tue, 2019-07-30 at 23:54 +0200, Helge Deller wrote:
[...]
> Thanks for the patch below, I'll test tomorrow...

It passed my test bed.  Just FYI, the code in question is never
exercised unless you see the message:

load extent tree[%d] block at %d

Somewhere in the boot.  The reason is that if you keep a separate /boot
partition, the chances are it has very few files, so those files it has
are very contiguous and ext4 doesn't need to build an extent tree so
our IPL code handles everything in ext3_extent_leaf_find().  The way to
build a fragmented /boot is (starting with an empty /boot):

mkdir /boot/tmp
a=0; while dd if=/dev/zero of=/boot/tmp/block.${a} bs=16k count=1; do a=$[$a+1]; done
a=0 while rm /boot/tmp/block.${a}; do a=$[$a+2]; done

And then copy the kernels in.

James


  reply	other threads:[~2019-07-31 14:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-30 20:58 Do NOT upgrade to palo v2.10 Helge Deller
2019-07-30 21:30 ` James Bottomley
2019-07-30 21:47   ` James Bottomley
2019-07-30 21:54     ` Helge Deller
2019-07-31 14:45       ` James Bottomley [this message]
2019-07-31 14:49         ` Helge Deller
2019-07-31  8:04 ` Helge Deller

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=1564584328.3319.5.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=deller@gmx.de \
    --cc=linux-parisc@vger.kernel.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.