Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 17 Oct 2013 13:14:58 +0200
From:      =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= <trasz@freebsd.org>
To:        Outback Dingo <outbackdingo@gmail.com>
Cc:        freebsd-current <freebsd-current@freebsd.org>, "Miguel C." <miguelmclara@gmail.com>
Subject:   Re: [SOLVED] Can't start iscsid - kldload: can't load iscsi: Exec format error - FreeBSD 10 Alpha 2
Message-ID:  <24483E07-AF51-4E90-A374-C3BA5E279AA9@freebsd.org>
In-Reply-To: <CAKYr3zyD9A-jxgwFRg8cyr0VP3kf1wBnqePV3nWUWOX%2B2g5Ofw@mail.gmail.com>
References:  <52571EF6.8010703@gmail.com> <A88A00CA-C292-42F4-8E3D-976CDAA03A8D@FreeBSD.org> <5257DDD1.4070403@gmail.com> <08D4D879-C866-4BEB-BB1D-9579A32F1975@FreeBSD.org> <7c50c939-bfe7-4fcb-b3ef-5c51d4ae8a9c@email.android.com> <CAKYr3zyD9A-jxgwFRg8cyr0VP3kf1wBnqePV3nWUWOX%2B2g5Ofw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Wiadomo=B6=E6 napisana przez Outback Dingo <outbackdingo@gmail.com> w =
dniu 17 pa=BC 2013, o godz. 03:11:

[..]

> Ive actually noticed what i feel is an anomaly with ctladm... i can =
literally
> run ctladm create -b block -o file=3D/luns/LUN0 numerous times...... =
and create a new LUN
> every time, using the same file.
>=20
> ctladm devlist
> LUN Backend       Size (Blocks)   BS Serial Number    Device ID=20
> san: ~ # ctladm create -b block -o file=3D/mnt/extent6
> LUN created successfully
> backend:       block
> device type:   0
> LUN size:      10485760 bytes
> blocksize      512 bytes
> LUN ID:        0
> Serial Number: MYSERIAL   0
> Device ID;     MYDEVID   0
> san: ~ # ctladm create -b block -o file=3D/mnt/extent6
> LUN created successfully
> backend:       block
> device type:   0
> LUN size:      10485760 bytes
> blocksize      512 bytes
> LUN ID:        1
> Serial Number: MYSERIAL   1
> Device ID;     MYDEVID   1

[..]

> notice the same file is used for each LUN...... it appears that ctladm =
never checks for a LUN using the same file..... or zpool for that =
matter....... anyway we can "correct" said behavior ??

Not really, because in some cases that's exactly what you want.  That's =
why
ctld(8) only warns about it when running with debugging enabled.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24483E07-AF51-4E90-A374-C3BA5E279AA9>