From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: vol_id and RAID1 members
Date: Fri, 27 Jan 2006 13:06:15 +0000 [thread overview]
Message-ID: <20060127130615.GD8175@wonderland.linux.it> (raw)
In-Reply-To: <20060124223036.GA16374@wonderland.linux.it>
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
On Jan 25, Kay Sievers <kay.sievers@vrfy.org> wrote:
> Sure, vol_id does look at the raid signature and ignores it, that's the
> reason your raid did not show up in the past. Does the degration of the
> device means that the raid signature is no longer valid?
Yes. Indeed, vol_id gets EIO when trying to read the superblock.
I think that in this case it should report the error and exit, because
as I showed if the partition really is an array member then it will
report wrong information which if used will cause data loss.
vol_id[8597]: main: BLKGETSIZE64=1999839744
vol_id[8597]: volume_id_probe_linux_raid: probing at offset 0x0, size 0x77332200
vol_id[8597]: volume_id_get_buffer: get buffer off 0x77320000(1999765504), len 0x800
vol_id[8597]: volume_id_get_buffer: read seekbuf off:0x77320000 len:0x800
vol_id[8597]: volume_id_get_buffer: read failed (Input/output error)
vol_id[8597]: volume_id_probe_intel_software_raid: probing at offset 0x0, size 0x77332200
vol_id[8597]: volume_id_get_buffer: get buffer off 0x77331e00(1999838720), len 0x200
vol_id[8597]: volume_id_get_buffer: read seekbuf off:0x77331e00 len:0x200
vol_id[8597]: volume_id_get_buffer: got 0x200 (512) bytes
[...]
--
ciao,
Marco
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-01-27 13:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 22:30 vol_id and RAID1 members Marco d'Itri
2006-01-24 23:55 ` Kay Sievers
2006-01-27 13:06 ` Marco d'Itri [this message]
2006-01-27 16:02 ` Kay Sievers
2006-01-27 16:35 ` Marco d'Itri
2006-01-27 16:48 ` Kay Sievers
2006-01-27 16:56 ` Marco d'Itri
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=20060127130615.GD8175@wonderland.linux.it \
--to=md@linux.it \
--cc=linux-hotplug@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).