Bug#880576: targetcli-fb: Cannot create PSCSI backend for SCSI tape drive

2021-10-28 Thread Ritesh Raj Sarraf
On Fri, 2021-10-22 at 16:12 +0200, Christian Scheffczyk wrote: > Hello Maintainers, > > was this problem fixed ever? I don't think so. I've CCed the other maintainer. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: This

Bug#880576: targetcli-fb: Cannot create PSCSI backend for SCSI tape drive

2021-10-22 Thread Christian Scheffczyk
Hello Maintainers, was this problem fixed ever? I'm running exactly into the same problem while trying to configure a changer and some tape drives as targets! I don't like the manual hack in a production environment. The problem was reported 4 years ago! Any news on that? Thanks and kind

Bug#880576: targetcli-fb: Cannot create PSCSI backend for SCSI tape drive

2018-12-16 Thread H. Elmann
Hello Christian, we are currently facing the same problem as described by Herbert at our institute. Manual configuration as described by you works. Of course, this hack will not survive a reboot. As a workaround, we wrote a custom start script which initializes the export. It works, but is

Bug#880576: targetcli-fb: Cannot create PSCSI backend for SCSI tape drive

2017-11-10 Thread Christian Seiler
Hi, On 11/10/2017 05:37 PM, Herbert Nachtnebel wrote: > I can confirm that using the tape drive from another host does work > like a charm after manually creating the pscsi backend using > configfs, yeah! Fantastic! > Thanks Christian for your input solving this issue! > If you already have a

Bug#880576: targetcli-fb: Cannot create PSCSI backend for SCSI tape drive

2017-11-10 Thread Herbert Nachtnebel
Hi Folks! I can confirm that using the tape drive from another host does work like a charm after manually creating the pscsi backend using configfs, yeah! Thanks Christian for your input solving this issue! If you already have a patch for targetcli to use sysfs' /bus/scsi/devices/... for

Bug#880576: targetcli-fb: Cannot create PSCSI backend for SCSI tape drive

2017-11-09 Thread Christian Seiler
Hi there, On 11/09/2017 09:24 AM, Herbert Nachtnebel wrote: > Thank you very much for the walk through to create the device! > Indeed, with these instruction I could create a backend for the > target. For completeness, one further step was missing: setting the > udev_path before enabling the

Bug#880576: targetcli-fb: Cannot create PSCSI backend for SCSI tape drive

2017-11-09 Thread Herbert Nachtnebel
Hi Christian! Thank you very much for the walk through to create the device! Indeed, with these instruction I could create a backend for the target. For completeness, one further step was missing: setting the udev_path before enabling the device: echo /dev/nst0 >

Bug#880576: targetcli-fb: Cannot create PSCSI backend for SCSI tape drive

2017-11-05 Thread Christian Seiler
Control: tags -1 + confirmed upstream Hi, On 11/02/2017 02:29 PM, Herbert Nachtnebel wrote: > exporting a local SCSI tape drive using targetcli is not possible. The used > SCSI tape > drive is an older HP Ultrium-2 SCSI drive connected via a Adaptec 29320ALP > U320 > PCIe > SCSI controller to

Bug#880576: targetcli-fb: Cannot create PSCSI backend for SCSI tape drive

2017-11-02 Thread Herbert Nachtnebel
Package: targetcli-fb Version: 2.1.43-1 Severity: normal Tags: upstream Dear Maintainer, exporting a local SCSI tape drive using targetcli is not possible. The used SCSI tape drive is an older HP Ultrium-2 SCSI drive connected via a Adaptec 29320ALP U320 PCIe SCSI controller to the host. The