search for: scsi_device

...83177.html That was just a question on why virtio uses the per-device tags, which didn't look like it made any sense. What I'm worried about here is mixing up the concept of reserved tags in the tagset, and queues to use them. Note that we already have the scsi_get_host_dev to allocate a scsi_device and thus a request_queue for the host itself. That seems like the better interface to use a tag for a host wide command vs introducing a parallel path.

...83177.html That was just a question on why virtio uses the per-device tags, which didn't look like it made any sense. What I'm worried about here is mixing up the concept of reserved tags in the tagset, and queues to use them. Note that we already have the scsi_get_host_dev to allocate a scsi_device and thus a request_queue for the host itself. That seems like the better interface to use a tag for a host wide command vs introducing a parallel path.

On 4/23/20 4:13 PM, John Garry wrote: > On 07/04/2020 17:30, Christoph Hellwig wrote: >> On Tue, Apr 07, 2020 at 04:00:10PM +0200, Hannes Reinecke wrote: >>> My concern is this: >>> >>> struct scsi_device *scsi_get_host_dev(struct Scsi_Host *shost) >>> { >>> ????[ .. ] >>> ????starget = scsi_alloc_target(&shost->shost_gendev, 0, >>> shost->this_id); >>> ????[ .. ] >>> >>> and we have typically: >>> >>> driver...

...hile attempting to do so. Is there any workaround around this? Any better way, forking virsh execution somehow? Could anyone explain why this is creating a deadlock in the first place? Isn't libvirt multithreaded? Thanks for the help! Shlomi ### hook script: #!/bin/bash enum_scsi() { scsi_devices=`cd /dev;ls sd[^a]*` } gen_hba_xml() { cat > ./hba.xml << EOF <controller type='scsi' model='virtio-scsi'/> EOF } passthrough_start() { # create virtio-scsi HBA gen_hba_xml virsh attach-device --persistent $domain_name ./hba.xml rm -f ./hba....

...ses the per-device tags, which >>> didn't look like it made any sense.? What I'm worried about here is >>> mixing up the concept of reserved tags in the tagset, and queues to use >>> them.? Note that we already have the scsi_get_host_dev to allocate >>> a scsi_device and thus a request_queue for the host itself.? That seems >>> like the better interface to use a tag for a host wide command vs >>> introducing a parallel path. >>> >> Thinking about it some more, I don't think that scsi_get_host_dev() is >> the best way o...

pvSCSI backend driver Signed-off-by: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com> Signed-off-by: Jun Kamada <kama@jp.fujitsu.com> ----- Jun Kamada _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...ioctl(struct block_device *bdev, fmode_t mode, - unsigned int cmd, unsigned long arg) +static int sd_ioctl_common(struct block_device *bdev, fmode_t mode, + unsigned int cmd, void __user *p) { struct gendisk *disk = bdev->bd_disk; struct scsi_disk *sdkp = scsi_disk(disk); struct scsi_device *sdp = sdkp->device; - void __user *p = (void __user *)arg; int error; SCSI_LOG_IOCTL(1, sd_printk(KERN_INFO, sdkp, "sd_ioctl: disk=%s, " @@ -1507,9 +1506,6 @@ static int sd_ioctl(struct block_device *bdev, fmode_t mode, break; default: error = scsi_cmd_blk_ioctl(b...

Hi Jens, James and Martin, This series concludes the work I did for linux-5.5 on the compat_ioctl() cleanup, killing off fs/compat_ioctl.c and block/compat_ioctl.c by moving everything into drivers. Overall this would be a reduction both in complexity and line count, but as I'm also adding documentation the overall number of lines increases in the end. My plan was originally to keep the

...eate Partition (??) 3. REBOOT (!!) 4. PVCreate 5. VGExtend 6. LVExtend 7. Resize2fs Going to a LVM/partition-less setup reduces expansion to 3 steps and we don't need to take the VM OS offline! 1. Increase size of VMDK 2- Inside the VM, OS, rescan the scsi drive with:'echo 1 >/sys/class/scsi_device//rescan; dmesg' (dmesg will check that you drive isize has grown) 3- Resize2fs. Our current disk arrangement has 3 VM HD devices 0 - small device (100M) with a single BOOT partition 1 - entire device is / 2 - entire device is SWAP Doing this has simplified resizing so much, I now let the juni...

...ioctl(struct block_device *bdev, fmode_t mode, - unsigned int cmd, unsigned long arg) +static int sd_ioctl_common(struct block_device *bdev, fmode_t mode, + unsigned int cmd, void __user *p) { struct gendisk *disk = bdev->bd_disk; struct scsi_disk *sdkp = scsi_disk(disk); struct scsi_device *sdp = sdkp->device; - void __user *p = (void __user *)arg; int error; SCSI_LOG_IOCTL(1, sd_printk(KERN_INFO, sdkp, "sd_ioctl: disk=%s, " @@ -1507,9 +1506,6 @@ static int sd_ioctl(struct block_device *bdev, fmode_t mode, break; default: error = scsi_cmd_blk_ioctl(b...

...+++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/drivers/scsi/virtio_scsi.c b/drivers/scsi/virtio_scsi.c index db3b494..6cd39cd 100644 --- a/drivers/scsi/virtio_scsi.c +++ b/drivers/scsi/virtio_scsi.c @@ -26,6 +26,7 @@ #include <scsi/scsi_host.h> #include <scsi/scsi_device.h> #include <scsi/scsi_cmnd.h> +#include <scsi/scsi_tcq.h> #define VIRTIO_SCSI_MEMPOOL_SZ 64 #define VIRTIO_SCSI_EVENT_LEN 8 @@ -633,6 +634,36 @@ static int virtscsi_device_reset(struct scsi_cmnd *sc) return virtscsi_tmf(vscsi, cmd); } +/** + * virtscsi_change_queue_depth()...

...+++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/drivers/scsi/virtio_scsi.c b/drivers/scsi/virtio_scsi.c index db3b494..6cd39cd 100644 --- a/drivers/scsi/virtio_scsi.c +++ b/drivers/scsi/virtio_scsi.c @@ -26,6 +26,7 @@ #include <scsi/scsi_host.h> #include <scsi/scsi_device.h> #include <scsi/scsi_cmnd.h> +#include <scsi/scsi_tcq.h> #define VIRTIO_SCSI_MEMPOOL_SZ 64 #define VIRTIO_SCSI_EVENT_LEN 8 @@ -633,6 +634,36 @@ static int virtscsi_device_reset(struct scsi_cmnd *sc) return virtscsi_tmf(vscsi, cmd); } +/** + * virtscsi_change_queue_depth()...

...d. >>> >>> wouldn't that limit 1x scsi device per host, not that I know if any >>> more would ever be required? But it does still seem better to use the >>> request queue in the scsi device. >>> >> My concern is this: >> >> struct scsi_device *scsi_get_host_dev(struct Scsi_Host *shost) >> { >> ?????[ .. ] >> ?????starget = scsi_alloc_target(&shost->shost_gendev, 0, >> shost->this_id); >> ?????[ .. ] >> >> and we have typically: >> >> drivers/scsi/hisi_sas/hisi_sas_v3_hw.c:...

...n/tgtd -f -d8 The above command runs the daemon in the foreground. So run start VMs with another terminal. If everything goes well, a SCSI host shows up in your VM (DomainU). clematis:/# cat /sys/class/scsi_host/host0/proc_name scsifront And you can see a disk driver: clematis:/# ls /sys/class/scsi_device/0\:0\:0\:0/device/ block:sda iocounterbits queue_depth scsi_level vendor bus iodone_cnt queue_type state delete ioerr_cnt rescan timeout device_blocked iorequest_cnt rev type driver model scs...

I don't think I've seen this with CentOS 6 or 5, but I had to repair an external RAID box this morning. The server, running CentOS 7, has an LSI HBA card in it, and it's presented to the system as /dev/sdb. I shut off the RAID controller, powered it off, did the repair, then plugged everything back in (that includes the two fiber cables and the ethernet), and brought the RAID back up.

...dev may be assigning the /dev/sdj (and other) identifier so I checked this. In /etc/udev/rules.d/* I see rules for scsi subsystem (sysfs type 0 is "disk"): ACTION=="add", SUBSYSTEM=="scsi", WAIT_FOR_SYSFS="ioerr_cnt" ACTION=="add", SUBSYSTEM=="scsi_device", SYSFS{type}=="0", RUN+="socket:/org/kernel/diskres/uevents" ACTION=="remove", SUBSYSTEM=="scsi_device", RUN+="socket:/org/kernel/diskres/uevents" So I do not see anything which could answer my question. There have been other rules for differ...

Please refer following Mr. Steven''s mail posted on June 24th. Message-ID: <20080624131313.GB18379@weybridge.uk.xensource.com> Message-ID: <20080624131256.GA18379@weybridge.uk.xensource.com> Signed-off-by: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com> Signed-off-by: Jun Kamada <kama@jp.fujitsu.com> ----- Jun Kamada

...ontroller (in the RAID box. >> >> I couldn't remount the drive until I rebooted the server. > > Before powering off/disconnecting RAID box, did you remove resembling SCSI > device? this is done if my memory doesn't fail me by doing this: > > echo 1 > /sys/class/scsi_device/6:0:0:0/device/delete No - I've never done that. With hot-swap drive bays, the system sees it going out, and says so, and then the drive goes away, or becomes inactive... but when I shove one back in, it sees it, though it may make it as /dev/sd[letter+1] (that is, if it had been /dev/sdb, it&...

...39;s an important web server without any kind of HA/Load Balancing (don't do that, kids). So what happened, is that after another administrator had extended the disk from VMWare, I tried to extend it from the OS side. Everything went well, listing my steps here: * echo 1 > /sys/class/scsi_device/2\:0\:0\:0/device/rescan * fdisk /dev/sdb (the usual, delete partition and make a new, bigger one) Now's when the problems happened. After writing the partition table I got the usual "Busy" error. But I needed to do this without downtime. So, what did I try to get the kernel ackn...

...LEN; i++) { + vscsi->event_list[i].vscsi = vscsi; + virtscsi_kick_event(vscsi, &vscsi->event_list[i]); + } + + return 0; +} + +static void virtscsi_handle_transport_reset(struct virtio_scsi *vscsi, + struct virtio_scsi_event *event) +{ + struct scsi_device *sdev; + struct Scsi_Host *shost = virtio_scsi_host(vscsi->vdev); + unsigned int target = event->lun[1]; + unsigned int lun = (event->lun[2] << 8) | event->lun[3]; + + switch (event->reason) { + case VIRTIO_SCSI_EVT_RESET_RESCAN: + scsi_add_device(shost, 0, target, lun); + br...