linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Sun, 09 Jan 2011 00:34:36 +0100	[thread overview]
Message-ID: <4D28F48C.1030806@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1101081739500.14736@cheetah.fastcat.org>

[-- Attachment #1: Type: text/plain, Size: 2273 bytes --]

On 01/08/2011 11:53 PM, Matthew Gabeler-Lee wrote:
> On Sat, 8 Jan 2011, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>
>> 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?
>
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.
> $ sudo mdadm -QD /dev/md2
> /dev/md2:
>         Version : 0.90
>   Creation Time : Mon Mar 27 14:04:18 2006
>      Raid Level : raid5
>      Array Size : 2185667136 (2084.41 GiB 2238.12 GB)
>   Used Dev Size : 728555712 (694.80 GiB 746.04 GB)
>    Raid Devices : 4
>   Total Devices : 4
> Preferred Minor : 2
>     Persistence : Superblock is persistent
>
>     Update Time : Sat Jan  8 17:40:20 2011
>           State : clean
>  Active Devices : 4
> Working Devices : 4
>  Failed Devices : 0
>   Spare Devices : 0
>
>          Layout : left-symmetric
>      Chunk Size : 64K
>
>            UUID : 01e2f978:88d1f867:34e1e46c:f3c01470
>          Events : 0.32040050
>
>     Number   Major   Minor   RaidDevice State
>        0       8       35        0      active sync   /dev/sdc3
>        1       8       19        1      active sync   /dev/sdb3
>        2       8        3        2      active sync   /dev/sda3
>        3       8       51        3      active sync   /dev/sdd3
>
> The actual last 64k of all the partitions in the array is all zeros.
> So is the 64k up to the end of the "Used Dev Size".  What has some
> data in it is the 64k after that.  I hope that has the superblock data
> I presume you're looking for.  I.e.  dd if=/dev/sdX3 bs=1024
> skip=728555712 count=64.
>


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

  reply	other threads:[~2011-01-08 23:34 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 [this message]
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=4D28F48C.1030806@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).