From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: Matthew Gabeler-Lee <cheetah@fastcat.org>
Cc: 597563@bugs.debian.org, linux-raid@vger.kernel.org
Subject: Re: Bug#597563: grub-common: grub-probe segfaults scanning lvm devices
Date: Sun, 09 Jan 2011 00:55:11 +0100 [thread overview]
Message-ID: <4D28F95F.4090509@gmail.com> (raw)
In-Reply-To: <4D28F58F.7000401@fastcat.org>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
On 01/09/2011 12:38 AM, Matthew Gabeler-Lee wrote:
> On 1/8/2011 18:34, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>> Sorry, I've noticed that I've looked into the wrong place all the long.
>> md2 is fine. I suppose it's a problem with md0 (all mdraid are assembled
>> at the beginning). Since md0 is raid1, its misassembly wouldn't have any
>> influence (we don't write to devices). mdstat lists both md0 and md1 as
>> having no duplicate indices. I would need info on md0 for this (now
>> minor) remaining bug.
I have a hypothesis. Does last partition on any device span, s.t. it
leaves less than 64K after it until the end of device? If so then GRUB
sees the same metadata sector as the one at the end of device and as at
the end of partition. With 1.x metadata sector contains its own location
on the device. With 0.90 I can see no such field. Is there a way to
check for such condition with 0.90?
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2011-01-08 23:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100920202854.27101.8288.reportbug@cheetah.fastcat.org>
[not found] ` <4D274FF9.8010004@gmail.com>
[not found] ` <alpine.DEB.2.00.1101072241560.25170@cheetah.fastcat.org>
2011-01-08 12:41 ` Bug#597563: grub-common: grub-probe segfaults scanning lvm devices Vladimir 'φ-coder/phcoder' Serbinenko
2011-01-08 22:53 ` Matthew Gabeler-Lee
2011-01-08 23:34 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-01-08 23:38 ` Matthew Gabeler-Lee
2011-01-08 23:55 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-01-09 3:09 ` Matthew Gabeler-Lee
2011-01-09 20:55 ` NeilBrown
2011-01-09 21:32 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-01-09 21:57 ` NeilBrown
2011-01-09 22:13 ` Matthew Gabeler-Lee
2011-01-09 22:29 ` NeilBrown
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=4D28F95F.4090509@gmail.com \
--to=phcoder@gmail.com \
--cc=597563@bugs.debian.org \
--cc=cheetah@fastcat.org \
--cc=linux-raid@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).