linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: John Robinson <john.robinson@anonymous.org.uk>
Cc: linux-raid@vger.kernel.org
Subject: Re: Storage device enumeration script
Date: Fri, 27 May 2011 07:23:03 -0400	[thread overview]
Message-ID: <4DDF8997.5090109@turmel.org> (raw)
In-Reply-To: <4DDF7296.6050706@anonymous.org.uk>

On 05/27/2011 05:44 AM, John Robinson wrote:
> On 27/05/2011 10:15, John Robinson wrote:
> [...]
>> I'm not entirely sure where dev.ID_ etc are supposed to be coming
>> from, but if it's that `blkid -p -o udev /dev/block/8:0` then I'm
>> afraid CentOS 5's blkid doesn't understand the -p or -o udev options,
>> it doesn't produce any output for whole drives with partition tables,
>> and there isn't a /dev/block directory. It's blkid 1.0.0 from
>> e2fsprogs 1.39-23.el5_5.1.
>>
>> If that knocks CentOS 5 support on the head then so be it...
> 
> Hmm, udevinfo might be of some use. Still doesn't say it's found a DOS
> partition table, but it does get you e.g. ID_FS_TYPE=linux_raid_member and perhaps `file -s` will tell you there's DOS partition table (sort of).

I'll look into this when I have a new CentOS 5 VM installed on my laptop.  I do want lsdrv to work with all of the CentOS 5 releases.

Phil

  reply	other threads:[~2011-05-27 11:23 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26  3:03 Storage device enumeration script Phil Turmel
2011-05-26  3:10 ` Mathias Burén
2011-05-26  3:21   ` Phil Turmel
2011-05-26  3:25     ` Mathias Burén
2011-05-26  5:25     ` Roman Mamedov
2011-05-26  8:24     ` CoolCold
2011-05-26 12:00       ` Phil Turmel
2011-05-31 18:51         ` Simon McNair
2011-05-31 21:21           ` CoolCold
2011-06-01  3:58             ` Phil Turmel
2011-05-26  6:14 ` Leslie Rhorer
2011-05-26  6:16   ` Mathias Burén
2011-05-26 11:41     ` Phil Turmel
2011-05-27  0:13       ` Leslie Rhorer
2011-05-27  0:16         ` Brad Campbell
2011-05-27  3:58           ` Roman Mamedov
2011-05-27 10:45             ` Gordon Henderson
2011-05-27 11:26               ` Torbjørn Skagestad
2011-05-27 11:42                 ` Gordon Henderson
2011-05-27 12:06             ` Phil Turmel
2011-05-26  8:11 ` CoolCold
2011-05-26  9:27 ` John Robinson
2011-05-26  9:45 ` Torbjørn Skagestad
2011-05-26  9:59   ` John Robinson
2011-05-26 11:49     ` Phil Turmel
2011-05-26 12:05       ` Torbjørn Skagestad
2011-05-27  9:15     ` John Robinson
2011-05-27  9:44       ` John Robinson
2011-05-27 11:23         ` Phil Turmel [this message]
2011-06-01  3:43           ` Phil Turmel
2011-05-26 11:39   ` Phil Turmel
2011-05-26 11:52     ` Torbjørn Skagestad
2011-05-26 17:46     ` Phil Turmel
2011-05-26 17:51       ` Mathias Burén
2011-05-26 17:54       ` Roman Mamedov
2011-05-26 18:02         ` Phil Turmel
2011-05-26 18:12           ` Roman Mamedov
2011-05-26 18:22             ` Phil Turmel
2011-05-26 18:42               ` Torbjørn Skagestad
2011-05-26 18:58                 ` CoolCold
2011-05-26 19:16                   ` Phil Turmel

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=4DDF8997.5090109@turmel.org \
    --to=philip@turmel.org \
    --cc=john.robinson@anonymous.org.uk \
    --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).