From: Steven Graf <sgraf@resolutech.net>
To: stgt@vger.kernel.org
Subject: Strange behavior from 1.0.46
Date: Wed, 21 May 2014 14:33:59 -0400 [thread overview]
Message-ID: <537CF197.7070308@resolutech.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
Hello Everyone,
I'm working with stgtd 1.0.46 (via Git) on CentOS 6.5 and I am getting
some inconsistent behavior. I did my own build with the CEPH_RBD=1 flag
passed into make. I then used "make rpm" to generate a RPM that I could
use to install on some test machines. What I have found is that on 2 of
the 3 machines the rbd backing store isn't showing up at all when I run
"tgtadm --lld iscsi --mode system --op show". On the 3rd machine
everything works great. These were all installed from the exact same
RPM (MD5s matched). What's even stranger yet is the tgtd in /usr/sbin
are all different sizes but all banner back with a --version as 1.0.46.
Thoughts?
--
Steven Graf
President
Resolutech, LLC
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3746 bytes --]
reply other threads:[~2014-05-21 18:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=537CF197.7070308@resolutech.net \
--to=sgraf@resolutech.net \
--cc=stgt@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