search for: scsi_devices

On Tue, Mar 10, 2020 at 09:08:56PM +0000, John Garry wrote: > On 10/03/2020 18:32, Christoph Hellwig wrote: > > On Wed, Mar 11, 2020 at 12:25:28AM +0800, John Garry wrote: > > > From: Hannes Reinecke <hare at suse.com> > > > > > > Allocate a separate 'reserved_cmd_q' for sending reserved commands. > > > > Why? Reserved command

On Tue, Mar 10, 2020 at 09:08:56PM +0000, John Garry wrote: > On 10/03/2020 18:32, Christoph Hellwig wrote: > > On Wed, Mar 11, 2020 at 12:25:28AM +0800, John Garry wrote: > > > From: Hannes Reinecke <hare at suse.com> > > > > > > Allocate a separate 'reserved_cmd_q' for sending reserved commands. > > > > Why? Reserved command

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,

...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.x...

On 4/7/20 1:54 PM, John Garry wrote: > On 06/04/2020 10:05, Hannes Reinecke wrote: >> On 3/11/20 7:22 AM, Christoph Hellwig wrote: >>> On Tue, Mar 10, 2020 at 09:08:56PM +0000, John Garry wrote: >>>> On 10/03/2020 18:32, Christoph Hellwig wrote: >>>>> On Wed, Mar 11, 2020 at 12:25:28AM +0800, John Garry wrote: >>>>>> From: Hannes

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

Each driver calling scsi_ioctl() gets an equivalent compat_ioctl() handler that implements the same commands by calling scsi_compat_ioctl(). The scsi_cmd_ioctl() and scsi_cmd_blk_ioctl() functions are compatible at this point, so any driver that calls those can do so for both native and compat mode, with the argument passed through compat_ptr(). With this, we can remove the entries from

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

I came across an old post comment yesterday (from http://echenh.blogspot.com/2010/04/how-to-extend-lvm-on-vmware-guest-os.html ) discussing the "hack" of LVM on Linux VM guests and whether it's better not to use it to simplify disk management. I've re-posted the comment below, does it sound reasonable? Is it better to not use LVM on Linux VM guests? --Russell

Each driver calling scsi_ioctl() gets an equivalent compat_ioctl() handler that implements the same commands by calling scsi_compat_ioctl(). The scsi_cmd_ioctl() and scsi_cmd_blk_ioctl() functions are compatible at this point, so any driver that calls those can do so for both native and compat mode, with the argument passed through compat_ptr(). With this, we can remove the entries from

change_queue_depth allows changing per-target queue depth via sysfs. It also allows the SCSI midlayer to ramp down the number of concurrent inflight requests in response to a SCSI BUSY status response and allows the midlayer to ramp the count back up to the device maximum when the BUSY condition has resolved. Signed-off-by: Venkatesh Srinivas <venkateshs at google.com> ---

change_queue_depth allows changing per-target queue depth via sysfs. It also allows the SCSI midlayer to ramp down the number of concurrent inflight requests in response to a SCSI BUSY status response and allows the midlayer to ramp the count back up to the device maximum when the BUSY condition has resolved. Signed-off-by: Venkatesh Srinivas <venkateshs at google.com> ---

On 4/7/20 4:35 PM, John Garry wrote: > On 07/04/2020 15:00, Hannes Reinecke wrote: >> On 4/7/20 1:54 PM, John Garry wrote: >>> On 06/04/2020 10:05, Hannes Reinecke wrote: [ .. ] >>>> This would be okay if 'this_id' would have been defined by the driver; >>>> sadly, most drivers which are affected here do set 'this_id' to -1.

This patchset includes an updated version of the SCSI frontend and backend drivers. The frontend and backend drivers exchange SCSI RDMA Protocol (SRP) messages via a ring buffer. The backend driver sends SCSI commands to the user-space daemon, which performs SCSI commands and I/O operations. The backend driver uses VM_FOREIGN feature like the blktap driver for zero-copy of data pages. Like the

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.

Hi All :) I am currently involved in a project in which there is a SAN array (Sun Storagetek 2540) which exports LUNs for some servers with Centos 5.2 x86. I will be performing a migration to Centos 5.9 x86_64 in some time and am gathering needed info now :) I am trying to find the place in the OS where there is the information about LUN mappings to /dev/ devices. For example on array level I

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

Valeri Galtsev wrote: > > On Fri, March 25, 2016 9:55 am, m.roth at 5-cent.us wrote: >> 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, >

Hello, Today a virtual server under my administration ran out of disk space, so I had to get extra space to it.. while it was running, because it'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,

This patch implements the hotplug support for virtio-scsi. When there is a device attached/detached, the virtio-scsi driver will be signaled via event virtual queue and it will add/remove the scsi device in question automatically. v2: handle no_event event Signed-off-by: Cong Meng <mc at linux.vnet.ibm.com> Signed-off-by: Sen Wang <senwang at linux.vnet.ibm.com> ---