Re: backstore created in "deactivated" state

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Please ignore my previous email, I figured it out.  I had to go into
the loopback target / lun ("cd naa.500140582a838aa2/luns/") and then
manually issue a "create" command for each backstore for which I
wanted to created a loopback device.  It would be nice it this
critical steps was mentioned in the wiki.

Regards,
Ahmed.

On Sun, Jun 21, 2015 at 7:19 PM, Ahmed Al-Mehdi <ahmedalmehdi@xxxxxxxxx> wrote:
> Hello,
>
> I am trying to setup a loopback setup using "targetcli".  I am
> following the steps mentioned at site -
> http://linux-iscsi.org/wiki/Loopback
>
> I issued the following commands:
>
> /backstores/fileio> create  dev_file_disk file_disk 10mb
> /loopback> create
> Created target naa.5001405f29525ad4.
>
>
> However, I see the fileio backstore created in "deactivated" state:
>
>   | o- fileio ..................................................................
> [Storage Objects: 1]
>   | | o- dev_file_disk .................... [file_disk (10.0MiB)
> write-back deactivated]
>
> How can I activated the fileio backstore (dev_file_disk)?  My
> understanding, if all is setup right (fileio backstore active), a new
> entry /dev/sdx  will be created.  Is that right?
>
>
> I have a related question.  If I create multiple fileio and/or block
> backstore.  Is there a way I can control which of the fileio/blockio
> are created a loopback, rather than all of them.
>
> Thank you,
> Ahmed.
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in



[Index of Archives]     [Linux SCSI]     [Kernel Newbies]     [Linux SCSI Target Infrastructure]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Device Mapper]

  Powered by Linux