Hi,
as an additional note, I've adjusted the rtslib python thingy now and
added 259 (major number of md partitions) to the list. Could add it just
fine then.
One does wonder why it checks major numbers in the first place ;). I
would prefer it'd just accept any block device (b---------), but I don't
know if some might have issues. If I were to export a tape drive or the
likes I'd use another backstore anyways.
Kind regards
On 08.07.2012 21:46, Christoph Hellwig wrote:
Moving to the target-devel list where you might get more useful
answers.
On Fri, Jul 06, 2012 at 05:40:18PM +0200, Ferry wrote:
Hi there,
first off - sorry to bug you guys, relative simple issue -
http://linux-iscsi.org/wiki/Support <- states to come here.
Anyways, walking my first steps with LIO, moving away from IET and
running into an issue.
Rather than have several MD devices created out of partitions, we
did the reverse. Added entire disks to MD and partitioned the MD
set, resulting in device like /dev/md4p1, /dev/md4p2, etc.
Whilst these are block devices (afaik, seem to act that way
everywhere else), targetcli doesn't seem to recognize them. At least
not on the Ubuntu 12.04 server I'm trying it with, frequently giving
not so savvy errors:
/backstores/fileio> create tt /dev/md4p1
For fileio, you must either specify both a file and a size, or just
a device path.
Can't create it, did specify a path (more accurate error would be
nice)
/backstores/fileio> create tt /dev/md4
Generating a wwn serial.
Not using buffered mode.
Created fileio tt with size None.
Entering new node /backstores/fileio/tt
No such path /backstores/fileio/tt
Creates it, but does give a no such path error, can cd into it and
get status just fine....
/backstores/fileio> ls
o- fileio ................................................... [1
Storage Object]
o- tt ................................................. [/dev/md4
deactivated]
/backstores/fileio> cd tt
/backstores/fileio/tt> ls
o- tt ................................................... [/dev/md4
deactivated]
/backstores/fileio/tt> status
Status for /backstores/fileio/tt: /dev/md4 deactivated
/backstores/fileio/tt> cd ..
/backstores/fileio> delete tt
Deleted storage object tt.
Deletes fine.
/backstores/fileio> cd ../iblock
/backstores/iblock> create tt /dev/md4p1
Generating a wwn serial.
Device is not a TYPE_DISK block device.
Same issue here as blockio.
/backstores/iblock> create tt /dev/md4
Generating a wwn serial.
Created iblock storage object tt using /dev/md4.
Entering new node /backstores/iblock/tt
No such path /backstores/iblock/tt
Just like fileio creates it, but states no such path... Again can CD
into it and get status tho'.
/backstores/iblock> cd tt
/backstores/iblock/tt> status
Status for /backstores/iblock/tt: /dev/md4 deactivated
/backstores/iblock/tt> cd ..
/backstores/iblock> delete tt
Deleted storage object tt.
Thanks in advance :).
--
To unsubscribe from this list: send the line "unsubscribe
linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
---end quoted text---
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
