similar to: [PATCH] Staging: hv: storvsc: Show the modulename in /sys/class/scsi_host/*/proc_name

Hi, i am currently struggling around with gluster restapi (not heketi), somehow i am a bit stuck. During startup of glusterrestd service it drops some python errors, heres a error log output with increased loglevel. Maybe someone can give me a hint how to fix this -- snip -- [2017-11-07 10:29:04 +0000] [30982] [DEBUG] Current configuration: proxy_protocol: False worker_connections: 1000

Processing commands for control at bugs.debian.org: > reassign 295352 logcheck-database Bug#295352: logcheck doesn't ignore rsync's log "rsync on modulename-with-hyphen from host (ip)" Bug reassigned from package `rsync' to `logcheck-database'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator

On my C5 machine (a Dell XPS420) I have a 500Gb disk on the internal SATA controller. I also have a SiI3132 dual-port multi-device eSATA card. This is connected to an external SATA array of disks. Now occasionally I see something like this in my logs ata7.01: exception Emask 0x0 SAct 0x0 SErr 0x0 a ction 0x0 ata7.01: irq_stat 0x00060002, device error via D 2H FIS ata7.01: cmd

From: Hank Janssen <hjanssen at microsoft.com> Increased storvsc ringbuffer and max_io_requests. This now more closely mimics the numbers on Hyper-V. And will allow more IO requests to take place for the SCSI driver. Signed-off-by:Hank Janssen <hjanssen at microsoft.com> Signed-off-by:Haiyang Zhang <haiyangz at microsoft.com> --- drivers/staging/hv/storvsc_api.h | 4 ++--

From: Hank Janssen <hjanssen at microsoft.com> Increased storvsc ringbuffer and max_io_requests. This now more closely mimics the numbers on Hyper-V. And will allow more IO requests to take place for the SCSI driver. Signed-off-by:Hank Janssen <hjanssen at microsoft.com> Signed-off-by:Haiyang Zhang <haiyangz at microsoft.com> --- drivers/staging/hv/storvsc_api.h | 4 ++--

This series implements virtio-scsi queue steering, which gives performance improvements of up to 50% (measured both with QEMU and tcm_vhost backends). The patches build on top of the new virtio APIs at http://permalink.gmane.org/gmane.linux.kernel.virtualization/18431; the new API simplifies the locking of the virtio-scsi driver nicely, thus it makes sense to require them as a prerequisite.

This series implements virtio-scsi queue steering, which gives performance improvements of up to 50% (measured both with QEMU and tcm_vhost backends). The patches build on top of the new virtio APIs at http://permalink.gmane.org/gmane.linux.kernel.virtualization/18431; the new API simplifies the locking of the virtio-scsi driver nicely, thus it makes sense to require them as a prerequisite.

This series implements virtio-scsi queue steering, which gives performance improvements of up to 50% (measured both with QEMU and tcm_vhost backends). This version rebased on Rusty's virtio ring rework patches. We hope this can go into virtio-next together with the virtio ring rework pathes. V5: improving the grammar of 1/5 (Paolo) move the dropping of sg_elems to 'virtio-scsi: use

This series implements virtio-scsi queue steering, which gives performance improvements of up to 50% (measured both with QEMU and tcm_vhost backends). This version rebased on Rusty's virtio ring rework patches. We hope this can go into virtio-next together with the virtio ring rework pathes. V5: improving the grammar of 1/5 (Paolo) move the dropping of sg_elems to 'virtio-scsi: use

This series implements virtio-scsi queue steering, which gives performance improvements of up to 50% (measured both with QEMU and tcm_vhost backends). This version rebased on Rusty's virtio ring rework patches. We hope this can go into virtio-next together with the virtio ring rework pathes. V4: rebase on virtio ring rework patches (rusty's pending-rebases branch) V3 and be found

This series implements virtio-scsi queue steering, which gives performance improvements of up to 50% (measured both with QEMU and tcm_vhost backends). This version rebased on Rusty's virtio ring rework patches. We hope this can go into virtio-next together with the virtio ring rework pathes. V4: rebase on virtio ring rework patches (rusty's pending-rebases branch) V3 and be found

Does anyone know if this is going to be fixed in CentOS ? // test case code below // expected behaviour is "all good" and a return code of zero. // this works on 2.6.35-1 // does not work on 2.6.18-194.17.4.el5 from Centos 5.5 // think this bug was fixed in git commit 8948e11f450e6189a79e47d6051c3d5a0b98e3f3 // around 2.6.22 // http://www.mail-archive.com/git-commits-head at

If a LUN larger than 2 TB is attached to a Linux VM on Hyper-V, we currently report a maximum size of 2 TB. This patch resolves the issue in hv_storvsc. Thanks to Robert Scheck <robert.scheck at etes.de> for reporting the issue. Signed-off-by: Mike Sterling <mike.sterling at microsoft.com> Signed-off-by: K.Y. Srinivasan <kys at microsoft.com> Signed-off-by: Haiyang Zhang

If a LUN larger than 2 TB is attached to a Linux VM on Hyper-V, we currently report a maximum size of 2 TB. This patch resolves the issue in hv_storvsc. Thanks to Robert Scheck <robert.scheck at etes.de> for reporting the issue. Signed-off-by: Mike Sterling <mike.sterling at microsoft.com> Signed-off-by: K.Y. Srinivasan <kys at microsoft.com> Signed-off-by: Haiyang Zhang

This series implements virtio-scsi queue steering, which gives performance improvements of up to 50% (measured both with QEMU and tcm_vhost backends). This version rebased on Rusty's virtio ring rework patches, which has already gone into virtio-next today. We hope this can go into virtio-next together with the virtio ring rework pathes. V6: rework "redo allocation of target data"

This series implements virtio-scsi queue steering, which gives performance improvements of up to 50% (measured both with QEMU and tcm_vhost backends). This version rebased on Rusty's virtio ring rework patches, which has already gone into virtio-next today. We hope this can go into virtio-next together with the virtio ring rework pathes. V6: rework "redo allocation of target data"

This series implements virtio-scsi queue steering, which gives performance improvements of up to 50% (measured both with QEMU and tcm_vhost backends). This version rebased on Rusty's virtio ring rework patches, which has already gone into virtio-next today. We hope this can go into virtio-next together with the virtio ring rework pathes. V7: respin to fix the patch apply error V6: rework

This series implements virtio-scsi queue steering, which gives performance improvements of up to 50% (measured both with QEMU and tcm_vhost backends). This version rebased on Rusty's virtio ring rework patches, which has already gone into virtio-next today. We hope this can go into virtio-next together with the virtio ring rework pathes. V7: respin to fix the patch apply error V6: rework

Hi all, this series adds multiqueue support to the virtio-scsi driver, based on Jason Wang's work on virtio-net. It uses a simple queue steering algorithm that expects one queue per CPU. LUNs in the same target always use the same queue (so that commands are not reordered); queue switching occurs when the request being queued is the only one for the target. Also based on Jason's

Hi all, this series adds multiqueue support to the virtio-scsi driver, based on Jason Wang's work on virtio-net. It uses a simple queue steering algorithm that expects one queue per CPU. LUNs in the same target always use the same queue (so that commands are not reordered); queue switching occurs when the request being queued is the only one for the target. Also based on Jason's