From: Jim Rees <rees@umich.edu>
To: Benny Halevy <bhalevy@panasas.com>
Cc: linux-nfs@vger.kernel.org, peter honeyman <honey@citi.umich.edu>
Subject: Re: [PATCH 4/5] various minor cleanups
Date: Thu, 2 Dec 2010 11:10:42 -0500 [thread overview]
Message-ID: <20101202161042.GA15055@merit.edu> (raw)
In-Reply-To: <4CF7B086.6000403@panasas.com>
Benny Halevy wrote:
Why can't it always dump the signature in hex, even if it happens to be ASCII?
I need it in ascii because that's how all my other tools print it out. When
I mis-place a disk, I start by looking at it on the server:
[nasadmin@emc-0 ~]$ nas_disk -l
id inuse sizeMB storageID-devID type name servers
1 y 11263 APM00064403224-0000 CLSTD root_disk 1,2
2 y 11263 APM00064403224-0001 CLSTD root_ldisk 1,2
3 y 2047 APM00064403224-0002 CLSTD d3 1,2
4 y 2047 APM00064403224-0003 CLSTD d4 1,2
5 y 2047 APM00064403224-0004 CLSTD d5 1,2
6 y 32767 APM00064403224-0005 CLSTD d6 1,2
7 n 451387 APM00064403224-0010 CLSTD d7 1,2
8 y 451387 APM00064403224-0011 CLSTD d8 1,2
Then on the client:
pdsi7# mpfsinq
Celerra signature vendor product_id device serial number or pathinfo
APM000644032240000-0008 DGC RAID 5 60:06:01:60:80:40:1a:00:be:91:96:89:d5:26:dd:11
path = /dev/sdh Active SP-b0 /dev/sg7
path = /dev/sdg Passive SP-a0 /dev/sg6
APM000644032240000-0007 DGC RAID 5 60:06:01:60:55:d1:19:00:1e:12:0e:87:d5:26:dd:11
path = /dev/sde Active SP-a0 /dev/sg4
path = /dev/sdf Passive SP-b0 /dev/sg5
And finally in the blkmapd log:
blkmapd: process_deviceinfo: 28 vols
blkmapd: decode_blk_volume: bv_type 0
blkmapd: decode_blk_signature: si_comps[0]: bs_length 4, bs_string 0x7
blkmapd: decode_blk_signature: si_comps[1]: bs_length 32, bs_string APM000644032240000
blkmapd: read_cmp_blk_sig: /dev/sde sig 0x7 at 473313851392
blkmapd: read_cmp_blk_sig: /dev/sde sig APM000644032240000 at 473313851492
blkmapd: decode_blk_volume: bv_type 1
blkmapd: decode_blk_volume: bv_type 0
blkmapd: decode_blk_signature: si_comps[0]: bs_length 4, bs_string 0x8
blkmapd: decode_blk_signature: si_comps[1]: bs_length 32, bs_string APM000644032240000
blkmapd: read_cmp_blk_sig: /dev/sdh sig 0x8 at 473313851392
blkmapd: read_cmp_blk_sig: /dev/sdh sig APM000644032240000 at 473313851492
next prev parent reply other threads:[~2010-12-02 16:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 19:13 [PATCH 0/5] nfs-utils: various changes Jim Rees
2010-11-30 19:13 ` [PATCH 1/5] add blkmapd and spnfsd to list of build targets to ignore Jim Rees
2010-12-02 14:05 ` Benny Halevy
2010-11-30 19:13 ` [PATCH 2/5] Remove blkmapd config file, which is no longer used Jim Rees
2010-12-02 14:06 ` Benny Halevy
2010-11-30 19:14 ` [PATCH 3/5] disk signature fixes Jim Rees
2010-11-30 19:14 ` [PATCH 4/5] various minor cleanups Jim Rees
2010-12-02 13:59 ` Benny Halevy
2010-12-02 14:11 ` Benny Halevy
2010-12-02 14:40 ` [PATCH] SQUASHME: decorate truncated signatures with "..." Benny Halevy
2010-12-02 14:41 ` [PATCH 4/5] various minor cleanups Jim Rees
2010-12-02 14:43 ` Benny Halevy
2010-12-02 16:10 ` Jim Rees [this message]
2010-12-02 14:35 ` [PATCH] SQUASHME: blkmapd: fix pretty_sig short sig endianess agnosticity Benny Halevy
2010-12-02 16:24 ` Jim Rees
2010-12-02 16:30 ` Benny Halevy
2010-12-02 16:58 ` Jim Rees
2010-11-30 19:14 ` [PATCH 5/5] device mapping fixes Jim Rees
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=20101202161042.GA15055@merit.edu \
--to=rees@umich.edu \
--cc=bhalevy@panasas.com \
--cc=honey@citi.umich.edu \
--cc=linux-nfs@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).