From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: Matthew Gabeler-Lee <cheetah@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: Sat, 08 Jan 2011 13:41:29 +0100 [thread overview]
Message-ID: <4D285B79.9040100@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1101072241560.25170@cheetah.fastcat.org>
[-- Attachment #1: Type: text/plain, Size: 2251 bytes --]
As was recommended I forward the remaining part to linux-raid mailing list.
In short: on his system mdraid, raid5, 4 devices, metadata (presumably)
0.90, two devices have index 0.
If such situation is valid please advice me on how such situation should
be handled.
@Matthew: could you supply mdadm -Q outputput and *last* 64K of every disk?
On 01/08/2011 05:08 AM, Matthew Gabeler-Lee wrote:
> On Fri, 7 Jan 2011, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>
>> I believe it to be a problem with raid5. Could you try the latest
>> upstream? If problem persists I would need following dumps:
>> dd if=/dev/sd[abcd]3 of=[abcd].img bs=1024 count=64
>> dd if=/dev/md2 of=2.img bs=1024 count=64
>> grub-fstest -c 4 /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3 hex -l
>> '(md2)+128' > g2.img
>
> OK, built grub from latest bzr trunk.
>
> From my past workarounds, I effectively have a list of all the
> invocations of grub-probe that grub-install/grub-setup runs on my
> system. Most of those work fine now. The only thing that isn't fine
> is that most invocations spit out a message "error: found two disks
> with the number 0" but give a correct answer and exit successfully.
>
> If I run grub-probe with enough --verbose arguments, then that message
> gets this context:
>
> grub-core/disk/raid.c:699: Scanning for RAID devices on disk hd2
> grub-core/kern/disk.c:245: Opening `hd2'...
> ./grub-probe: info: the size of hd2 is 1465149168.
> error: found two disks with the number 0.
> grub-core/kern/disk.c:330: Closing `hd2'.
>
> So, it seems maybe you're right that there's something funky with the
> raid5. The outputs you requested are attached. The grub-fstest
> invocation complained that -l is not a valid option, I hope the output
> without it is still what you want / need. I included the full output
> of one of the complaining grub-probe invocations too, on the guess
> that it might be helpful.
>
> FWIW, the raid5 array in question has had every disk swapped at least
> once in its life span, including from growing from 3 to 4 disks, and
> from smaller to larger disks, not to mention one or two disk failures
> along the way.
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next parent reply other threads:[~2011-01-08 12:41 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 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-01-08 22:53 ` Bug#597563: grub-common: grub-probe segfaults scanning lvm devices 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
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=4D285B79.9040100@gmail.com \
--to=phcoder@gmail.com \
--cc=597563@bugs.debian.org \
--cc=cheetah@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).