On Mon, Nov 26 2012, Sebastian Andrzej Siewior wrote: > Wouldn't say that. It may adds complexity on another level. The target > subsystem has the same problem with adding luns and there seems nothing > wrong with having lun3 and 4 and leaving 0 and 1 unsued. That's not what Wikipedia claims though (from <http://en.wikipedia.org/wiki/Logical_Unit_Number>): LUN 0: There is one LUN which is required to exist in every target: zero. The logical unit with LUN zero is special in that it must implement a few specific commands, most notably Report LUNs, which is how an initiator can find out all the other LUNs in the target. But LUN zero need not provide any other services, such as a storage volume. That's why I proposed solution where one needs to have continuous numbering of LUNs. I'm not an expert on SCSI though. > With the tcm gadget I get: > > |scsi 0:0:0:2: Direct-Access LIO-ORG RAMDISK-MCP 4.0 PQ: 0 > ANSI: 5 > |scsi 0:0:0:3: Direct-Access LIO-ORG FILEIO 4.0 PQ: 0 > ANSI: 5 > > You notice :2 and :3 instead :0 and :1. While should be there something > wrong with this? It may be that it works on Linux but fails on some other systems (or even older Linux kernels). Like I've said, I'm not SCSI expert, so my knowledge of it is (embarrassingly) minimal. -- Best regards, _ _ .o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o ..o | Computer Science, Michał “mina86” Nazarewicz (o o) ooo +----<email/xmpp: mpn@xxxxxxxxxx>--------------ooO--(_)--Ooo--
Attachment:
pgpd0BsegGBSE.pgp
Description: PGP signature
