From: Phil Turmel <philip@turmel.org>
To: "Torbjørn Skagestad" <torbjorn@itpas.no>
Cc: linux-raid@vger.kernel.org, Roman Mamedov <roman@rm.pp.ru>,
John Robinson <john.robinson@anonymous.org.uk>,
CoolCold <coolthecold@gmail.com>
Subject: Re: Storage device enumeration script
Date: Thu, 26 May 2011 07:39:29 -0400 [thread overview]
Message-ID: <4DDE3BF1.7030105@turmel.org> (raw)
In-Reply-To: <1306403130.9437.109.camel@torbjorn>
Thanks Torbjørn !
I tend to short the error-checking when I'm putting something together... Clearly, this script was less baked than I thought.
On 05/26/2011 05:45 AM, Torbjørn Skagestad wrote:
> @@ -166,9 +171,12 @@
> devpath = os.path.realpath(devpathlink)
> if devpath in phydevs:
> return phydevs[devpath]
> - phy = Struct(dpath=devpath, node=nodestr,
> - vendor=io.FileIO(devpath+'/vendor').read().split("\n",1)[0].strip(),
> - model=io.FileIO(devpath+'/model').read().split("\n",1)[0].strip())
> + try:
> + phy = Struct(dpath=devpath, node=nodestr,
> + vendor=io.FileIO(devpath+'/vendor').read().split("\n",1)[0].strip(),
> + model=io.FileIO(devpath+'/model').read().split("\n",1)[0].strip())
> + except IOError:
> + return None
> if os.path.exists(devpath+'/unique_id'):
> phy.serial = io.FileIO(devpath+'/unique_id').read().split("\n",1)[0].strip()
> if not phy.serial:
This hunk will have to be done differently. "phy" needs to be set without vendor & model if they can't be read. I'll make a helper function to read the first line of a file, or return None.
On 05/26/2011 04:11 AM, CoolCold wrote:
> May be setup some github repo for this?
>
Yes, I'll do this later today. Obviously needed. :(
Phil
--
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-26 11:39 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
2011-06-01 3:43 ` Phil Turmel
2011-05-26 11:39 ` Phil Turmel [this message]
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=4DDE3BF1.7030105@turmel.org \
--to=philip@turmel.org \
--cc=coolthecold@gmail.com \
--cc=john.robinson@anonymous.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=roman@rm.pp.ru \
--cc=torbjorn@itpas.no \
/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).