From: Michael Prokop <mika@grml.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: vol_id: broken linux_raid detection
Date: Fri, 02 Feb 2007 23:27:25 +0000 [thread overview]
Message-ID: <2007-02-03T00-11-50@devnull.michael-prokop.at> (raw)
In-Reply-To: <2007-02-02T22-49-07@devnull.michael-prokop.at>
* Kay Sievers <kay.sievers@vrfy.org> wrote:
> On 2/2/07, Michael Prokop <mika@grml.org> wrote:
>> whereas vol_id displayed linux_raid_member as ID_FS_TYPE for
>> partitions with filesystem type fd fine so far, I noticed a problem
>> with current versions of udev. Using vol_id now displays the
>> filesystem of the given partition (for example 'xfs') instead of
>> 'linux_raid_member'. :(
>> I've tracked down the problem using bisect to the following commit:
>> ,----
>> | aa68c048f84b95fd982cb0fb2210ea740dbebc64 is first bad commit
>> | commit aa68c048f84b95fd982cb0fb2210ea740dbebc64
>> | Author: Kay Sievers <kay.sievers@suse.de>
>> | Date: Wed Nov 15 20:41:25 2006 +0100
>> |
>> | volume_id: fix endianess bug in linux_raid detection
>> |
>> | :040000 040000 aa1a4943fea035173411b1f5a70ee967007c14d4 9a58a1edba50f7e3aa5f9c33d8aa560ebbf00aa8 M extras
> The volume is a member of a md raid set?
Yes, used to work fine under any circumstances so far. I'm testing
the different vol_id/udev versions on the same system (using my
live-cd), same setup, kernel, raid configuration,... just switching
between the udev versions.
> What does:
> /lib/udev/vol_id --probe-all /dev/...
> print?
Broken vol_id:
# /lib/udev/vol_id --probe-all /dev/hda1
xfs
Older, working vol_id:
# /lib/udev/vol_id --probe-all /dev/hda1
linux_raid_member
xfs
thx && regards,
-mika-
--
,'"`. http://www.michael-prokop.at/
( grml.org -» Linux Live-CD for texttool-users and sysadmins
`._,' http://www.grml.org/
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2007-02-02 23:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-02 22:23 vol_id: broken linux_raid detection Michael Prokop
2007-02-02 23:02 ` Kay Sievers
2007-02-02 23:27 ` Michael Prokop [this message]
2007-02-03 0:06 ` Kay Sievers
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=2007-02-03T00-11-50@devnull.michael-prokop.at \
--to=mika@grml.org \
--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).