From: Jim Rees <rees@umich.edu>
To: Bruno Silva <bs@cin.ufpe.br>
Cc: Lev Solomonov <solo@tonian.com>, linux-nfs@vger.kernel.org
Subject: Re: About pNFS installation process.
Date: Fri, 23 Mar 2012 14:02:47 -0400 [thread overview]
Message-ID: <20120323180247.GA2815@umich.edu> (raw)
In-Reply-To: <CAAJC9VbvRm49iW2jFUfVqw4k20hPbLfrUr_Wm=pHLmD_23WJew@mail.gmail.com>
Blkmapd is finding your iscsi devices, but can't create the mapped device
for some reason. I suspect the geometry is wrong but you'd have to do some
debugging to figure out exactly why.
I guess we should fix or get rid of pretty_sig.
Date: Thu, 2 Dec 2010 09:41:26 -0500
From: Jim Rees <rees@umich.edu>
Subject: Re: [PATCH 4/5] various minor cleanups
To: Benny Halevy <bhalevy@panasas.com>
Cc: linux-nfs@vger.kernel.org, peter honeyman <honey@citi.umich.edu>
...
I am glad you are paying attention! I am aware of the shortcomings of
pretty_sig(). In addition to the problems you noted, it also assumes that a
signature over 8 bytes long is representable as a text string, which is not
guaranteed. The code it replaced was worse.
I put this in because for debugging I need to be able to follow a signature
all the way from my EMC server to the devmapper. pretty_sig() simply prints
the signature in a way that I can match it up with the signature on the
server.
I don't want to spend a lot of time on this, but I also am uneasy leaving
EMC-specific code in nfs-utils, especially since it can blow up if you use
it against a non-EMC server. My inclination is to remove this debugging
code when I no longer need it. I guess at the very least I should put in a
comment. I am open to suggestions.
next prev parent reply other threads:[~2012-03-23 18:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 20:23 About pNFS installation process Bruno Silva
2012-03-16 0:16 ` Jim Rees
2012-03-16 18:14 ` About Direct I/O Alexandre Depoutovitch
2012-03-16 20:35 ` J. Bruce Fields
2012-03-16 20:58 ` Myklebust, Trond
2012-03-18 10:51 ` About pNFS installation process Lev Solomonov
2012-03-23 17:21 ` Bruno Silva
2012-03-23 18:02 ` Jim Rees [this message]
2012-04-04 0:20 ` Lev Solomonov
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=20120323180247.GA2815@umich.edu \
--to=rees@umich.edu \
--cc=bs@cin.ufpe.br \
--cc=linux-nfs@vger.kernel.org \
--cc=solo@tonian.com \
/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