Marius, > [ +0,000007] sd 2:0:1:0: [sdb] tag#325 ABORT operation started > [Nov14 23:50] sd 2:0:1:0: ABORT operation timed-out. > [ +0,009594] scsi target2:0:0: TARGET RESET operation started > [ +4,905550] scsi target2:0:0: TARGET RESET operation timed-out. > [ +0,000005] scsi target2:0:1: TARGET RESET operation started > [ +34,407328] scsi target2:0:1: TARGET RESET operation timed-out. > [ +9,829432] sd 2:0:0:0: [sda] tag#76 ABORT operation started > [ +0,002336] sym0: SCSI BUS reset detected. > [ +0,002062] sd 2:0:0:0: ABORT operation complete. > [ +0,005062] sym0: SCSI BUS has been reset. > [ +3,193215] sd 2:0:1:0: Power-on or device reset occurred > [ +0,000057] sd 2:0:0:0: [sda] tag#76 BUS RESET operation started > [ +0,002319] sd 2:0:0:0: BUS RESET operation complete. > [ +0,000008] sym0: SCSI BUS reset detected. > [ +0,006945] sym0: SCSI BUS has been reset. Hannes made some tweaks to the sym53c8xx_2 handling about a year ago which may explain the difference in behavior when I/Os time out due to load. But why rely on emulating 20-year old hardware in a performance-conscious environment? I thought Proxmox defaulted to virtio? -- Martin K. Petersen Oracle Linux Engineering
