From: John Robinson <john.robinson@anonymous.org.uk>
To: Phil Turmel <philip@turmel.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Storage device enumeration script
Date: Fri, 27 May 2011 10:15:05 +0100 [thread overview]
Message-ID: <4DDF6B99.20602@anonymous.org.uk> (raw)
In-Reply-To: <4DDE249C.7080004@anonymous.org.uk>
On 26/05/2011 10:59, John Robinson wrote:
[...]
> [root@beast lsdrv]# python2.6 lsdrv
> PCI [pata_marvell] 03:00.0 IDE interface: Marvell Technology Group Ltd.
> 88SE6121 SATA II Controller (rev b2)
> └─scsi 0:0:0:0 HL-DT-ST DVD-RAM GH22NP20
> └─sr0: Empty/Unknown 1.00g
> PCI [ahci] 00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10
> Family) SATA AHCI Controller
> ├─scsi 2:0:0:0 ATA Hitachi HDS72101
> │ └─sda: Empty/Unknown 931.51g
> Traceback (most recent call last):
> File "lsdrv", line 387, in <module>
> show_blocks(" %s " % branch[0], [phy.block])
> File "lsdrv", line 339, in show_blocks
> show_blocks("%s %s " % (indent, branch[0]), [blockbyname[x] for x in subs])
> KeyError: 'sda1'
>
> Now, something's not getting picked up about sda. Looking at Mathias'
> "sweet" output, it's not coping with the (DOS) partition table. Another
> variation on my kernel's /sys or still to old a Python or ...?
Still seeing this. I added a print command so I can see that
dev.partitions is being populated successfully. 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...
Cheers,
John.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-05-27 9:15 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 [this message]
2011-05-27 9:44 ` John Robinson
2011-05-27 11:23 ` Phil Turmel
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=4DDF6B99.20602@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.