James,
>> However, it doesn't look like we have much to work with since there
>> is no ATA Information VPD page exposed.
>
> it's the fat firmware problem again. However, the driver does know, so
> could we persuade a modification of
> mpt3sas_scsih.c:_scsih_display_sata_capabilities() to popula
On Mon, 2018-04-16 at 23:25 -0400, Martin K. Petersen wrote:
> Nikola,
>
> > thanks for explanation. but disabling write same for now is safe,
> > right?
>
> I was hoping we'd be able to disable it for SATA devices only.
>
> > root@siv-70140:~ # sg_vpd /dev/sda
> > Supported VPD pages VPD page:
Nikola,
> thanks for explanation. but disabling write same for now is safe,
> right?
I was hoping we'd be able to disable it for SATA devices only.
> root@siv-70140:~ # sg_vpd /dev/sda
> Supported VPD pages VPD page:
> Supported VPD pages [sv]
> Device identification [di]
> Supported VPD
Hi Martin,
thanks for explanation. but disabling write same for now is safe, right?
to answer your questions:
drives are SATA.
root@siv-70140:~ # sg_inq /dev/sda
standard INQUIRY:
PQual=0 Device_type=0 RMB=0 version=0x02 [SCSI-2]
[AERC=0] [TrmTsk=0] NormACA=0 HiSUP=0 Resp_data_form
Nikola,
> hmm, further checking 4.4.52, it was not really OK too:
>
> [ 1895.084325] blk_update_request: I/O error, dev sda, sector 239461608
> [ 1895.101099] sd 4:1:1:0: [sda] tag#1 FAILED Result: hostbyte=DID_OK
> driverbyte=DRIVER_SENSE
> [ 1895.101101] sd 4:1:1:0: [sda] tag#1 Sense Key : Ille
in the meantime, I've disabled WRITE SAME for mptsas:
diff -Naur linux-4.14/drivers/message/fusion/mptsas.c
linux-4.14-mptsas-disable-write-same/drivers/message/fusion/mptsas.c
--- linux-4.14/drivers/message/fusion/mptsas.c2017-11-12
19:46:13.0 +0100
+++ linux-4.14-mptsas-disabl
hmm, further checking 4.4.52, it was not really OK too:
[ 1895.084325] blk_update_request: I/O error, dev sda, sector 239461608
[ 1895.101099] sd 4:1:1:0: [sda] tag#1 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[ 1895.101101] sd 4:1:1:0: [sda] tag#1 Sense Key : Illegal Request [current
Hi,
after switch from 4.4 to 4.14 we're getting reports of delayed allocation
failures on ext4 filesystems. Since we're getting it on many machines, including
brand new or with new harddrives replaced, I don't think it's disk issue.
here's example of the warning:
[52455.961319] sd 4:1:4:0: [sda]
8 matches
Mail list logo
