Awesome. Thanks Darryl. Do you want to propose a fix to stgt, or shall I? On Aug 8, 2013 7:21 PM, "Darryl Bond" <db...@nrggos.com.au> wrote:
> Dan, > I found that the tgt-admin perl script looks for a local file > > if (-e $backing_store && ! -d $backing_store && $can_alloc == 1) { > > A bit nasty, but I created some empty files relative to / of the same > path as the RBD backing store which worked around the problem. > > mkdir /iscsi-spin > touch /iscsi-spin/test > > Lets me restart tgtd and have the LUN created properly. > > tgt-admin --dump is also not that useful, doesn't output the backing > store type. > > # tgt-admin --dump > default-driver iscsi > > <target iqn.2013.com.ceph:test> > backing-store iscsi-spin/test > initiator-address 192.168.6.100 > </target> > > > Darryl > > On 08/09/13 07:23, Dan Mick wrote: > >> On 08/04/2013 10:15 PM, Darryl Bond wrote: >> >>> I am testing scsi-target-utils tgtd with RBD support. >>> I have successfully created an iscsi target using RBD as an iscsi target >>> and tested it. >>> It backs onto a rados pool iscsi-spin with a RBD called test. >>> Now I want it to survive a reboot. I have created a conf file >>> >>> <target iqn.2008-09.com.ceph:test> >>> <backing-store iscsi-spin/test> >>> bs-type rbd >>> path iscsi-spin/test >>> </backing-store> >>> </target> >>> >>> When I restart tgtd It creates the target but doesn't connect the >>> backing store. >>> The tool tgt-admin has a test mode for the configuration file >>> >>> [root@cephgw conf.d]# tgt-admin -p -e >>> # Adding target: iqn.2008-09.com.ceph:test >>> tgtadm -C 0 --lld iscsi --op new --mode target --tid 1 -T >>> iqn.2008-09.com.ceph:test >>> # Skipping device: iscsi-spin/test >>> # iscsi-spin/bashful-spin does not exist - please check the >>> configuration file >>> tgtadm -C 0 --lld iscsi --op bind --mode target --tid 1 -I ALL >>> >>> It looks to me like tgtd support RBD backing stores but the >>> configuration utilities don't. >>> >> I have not tried config files or tgt-admin to any great extent, but it >> doesn't look to me like there are backend dependencies in those tools >> (or I would have modified them at the time :)), but, that said, there >> may be some weird problem. tgt-admin is a Perl script that could be >> instrumented to figure out what's going on. >> >> I do know that the syntax of the config file is dicey. >> >> Anyone tried this? >>> What have I missed? >>> >>> Regards >>> Darryl >>> >>> >>> The contents of this electronic message and any attachments are intended >>> only for the addressee and may contain legally privileged, personal, >>> sensitive or confidential information. If you are not the intended >>> addressee, and have received this email, any transmission, distribution, >>> downloading, printing or photocopying of the contents of this message or >>> attachments is strictly prohibited. Any legal privilege or >>> confidentiality attached to this message and attachments is not waived, >>> lost or destroyed by reason of delivery to any person other than >>> intended addressee. If you have received this message and are not the >>> intended addressee you should notify the sender by return email and >>> destroy all copies of the message and any attachments. Unless expressly >>> attributed, the views expressed in this email do not necessarily >>> represent the views of the company. >>> ______________________________**_________________ >>> ceph-users mailing list >>> ceph-users@lists.ceph.com >>> http://lists.ceph.com/**listinfo.cgi/ceph-users-ceph.**com<http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com> >>> >> > > The contents of this electronic message and any attachments are intended > only for the addressee and may contain legally privileged, personal, > sensitive or confidential information. If you are not the intended > addressee, and have received this email, any transmission, distribution, > downloading, printing or photocopying of the contents of this message or > attachments is strictly prohibited. Any legal privilege or confidentiality > attached to this message and attachments is not waived, lost or destroyed > by reason of delivery to any person other than intended addressee. If you > have received this message and are not the intended addressee you should > notify the sender by return email and destroy all copies of the message and > any attachments. Unless expressly attributed, the views expressed in this > email do not necessarily represent the views of the company. >
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com