similar to: SCSI/SAS error message by mpt2sas.ko

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: normal My 32Bit Dom0-crashes with error "Out of SW-IOMMU space for 65536 bytes" after doing moderate I/O on the local storage, which is a software-raid1 over 3 harddrives, connected to the builtin Perc H200 controller with ext3-fs. The error is reproduceable with "dd if=/dev/zero of=bigfile bs=1024 count=1000000"

I'm trying to figure out why 2 machines have a "hard I/O lock" on the HDD when running EL6. I have 4 identical machines, all were stable with EL5. 2 work great with EL6, 2 do not. I've checked momtherboard BIOS versions and settings, SAS controller BIOS versions and settings, they are the same between the working and non- working systems. When booting a non-working system,

On Tue Feb 16 03:35:06 PM, John R Pierce wrote: Thanks to both you and Mark Roth for chiming in and thank you for the lsi-raidinfo script. > On 2/16/2016 3:23 PM, Zube wrote: > >Does anyone know what program can be used to query the RAID status > >from the OS for an on-board LSI SAS 2308-4i? > > the 2308 isn't actually a megaraid, Right, that is in agreement with both

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

Hi I am attempting to setup Xen 4.10 with kernel 4.9.86-30 ( virt7-xen-410-testing, virt7-common-testing ) on CentOS7 After installing everything, the machine was unable to boot and hung in dracut stating it could not find its root device. The testsystem I use is a somewhat aged Dell M915 Blade (Quad opteron 61xx), using an MPT SAS controller for it's SAS boot drives. Stock CentOS 7

I have a couple development servers running centos 6.3 64bit that have LSI 9211-8i SAS2 controllers connected to a SAS2 backplane. these work fine with SATA hard disks (populated with a bunch of 3TB SATA drives)... I'm trying to install a OCZ Vertex3 SSD on each of the two servers to do some ssd caching tests... system sees the drive, so I do the following... # parted -a min

I have the exact same issue on several Sunfire v20z (hardware LSI RAID controler). Under high IO load, the raid controler starts complaining with disk errors : [163442.483878] mptbase: ioc0: LogInfo(0x11070000): F/W: DMA Error [163445.172333] sd 2:0:0:0: [sda] Unhandled error code [163445.172338] sd 2:0:0:0: [sda] Result: hostbyte=DID_SOFT_ERROR driverbyte=DRIVER_OK [163445.172345] sd 2:0:0:0:

Hi maintainer, Reprodue an bug on xen-unstable, it''s an irq affinity issue for passthroughed msix device to uek1 pvhvm(2.6.32 stable). I passthrough two mptsas devices(0000:0d:0.0, 0000:1f:0.0) to a pvhvm, irq affinity can''t be changed. Step to reproduce is as below: 1. xl -f pci-assignable-add 0000:0d:0.0; xl -f pci-assignable-add 0000:1f:0.0 2.xm cr -c vm.cfg

Hello, I have a weird problem after adding new PV do LMV volume group. It seems the error comes out only during boot time. Please read the story. I have couple of 1U machines. They all have two, four or more Fujitsu-Siemens SAS 2,5" disks, which are bounded in Raid1 pairs with Linux mdadm. First pair of disks has always two arrays (md0, md1). Small md0 is used for booting and the rest - md1

I have a handful of new systems where I've seen unexpectedly low disk performance on an Avago SAS controller, when using CentOS 7. It looked like a regression, so I installed CentOS 6 on one of them and reloaded CentOS 7 on the other. Immediately after install, a difference is apparent in the RAID rebuild speed. The CentOS 6 system is initializing its software RAID5 array at somewhere

Hi, I''m running OpenSuse 12.2 with kernel 3.5.3 HBA= LSI 1068e using the MPTSAS driver (patched) (https://patchwork.kernel.org/patch/1379181/) SANOS1:/media # uname -a Linux SANOS1 3.5.3 #3 SMP Sun Sep 2 18:44:37 CEST 2012 x86_64 x86_64 x86_64 GNU/Linux I''ve tried to simulate a disk replacement but it seems that now /dev/sdg is stuck in the btrfs pool (RAID10) SANOS1:/media #

On 1/5/2015 7:14 AM, Philippe BOURDEU d'AGUERRE wrote: > > Since Centos 6.6 update (kernel 2.6.32-504), the controller doesn't > initialize at boot. Reverting to kernel 2.6.32-431 allows server to > boot fine. works here fine on the 9261, which is an OEM version of the same card with the connectors in a different orientation... you might check your LSI firmware revision.

I am now testing XEN live migration on two physical hosts with XEN 4.0.1 pvops Ubuntu 10.10 (2.6.35-22). Host A also acts as a NFS server, and Host B acts as a NFS client. When I migrate a guest domain from B to A. The ssh connection experiences a downtime of about 1 minute (the terminal does not react to the keyboard input till about 1 minute later). However, the "sudo xm console" does

The HBA is an HP H220. We haven?t really benchmarked individual drives ? all 12 drives are utilized in one RAID-10 array, I?m unsure how we would test individual drives without breaking the array. Trying ?hdparm -tT /dev/sda? now ? it?s been running for 25 minutes so far? Kelly On 2016-05-25, 2:12 PM, "centos-bounces at centos.org on behalf of Dennis Jacobfeuerborn"

On Wed, May 17, 2017 at 10:07 AM, Sarah Newman <srn at prgmr.com> wrote: > On 05/16/2017 09:04 PM, Jerry wrote: > <snip> > > > > Turns out dracut was unable to mount the root file system. So I went > back > > into the 3.10 kernel again to see if the mpt2sas or mpt3sas driver was in > > its initramfs file... and it wasn't: > > > > >

Processing commands for control at bugs.debian.org: > reassign 603727 linux-2.6 Bug #603727 [xen-hypervisor-4.0-amd64] xen-hypervisor-4.0-amd64: i386 Dom0 crashes after doing some I/O on local storage (software Raid1 on SAS-drives with mpt2sas driver) Bug reassigned from package 'xen-hypervisor-4.0-amd64' to 'linux-2.6'. No longer marked as found in versions xen/4.0.1-1.

Howdy, I hit a snag trying to install Xen4CentOS on a Supermicro based system (X9DRD-7LN4F with the Broadcom/LSI 2308 chipset). I spent a few hours on this today, I'm posting this here in case it helps anyone else and saves them the frustration I dealt with. On this system I did a fresh install of CentOS 7, updated it, rebooted it, then installed Xen. The system was booting fine using the

Kelly Lesperance wrote: > LSI/Avago?s web pages don?t have any downloads for the SAS2308, so I think > I?m out of luck wrt MegaRAID. > > Bounced the node, confirmed MPT Firmware 15.10.09.00-IT. > HP Driver is v 15.10.04.00. > > Both are the latest from HP. > > Unsure why, but the module itself reports version 20.100.00.00: > > [root at r1k1 sys] # cat

Running CentOS 5 (long story, will be updated some day). A 5 yr old Dell PE R415. Whoever spec'd the order, they got the cheapest, embedded controller. Push came to shove - these things gag on a drive > 2TB. So, we bought some PERC H200's for it, and its two mates. This morning, I brought the system down, and put in the card, and moved the SATA cables. This did not end well. The new