Re: MPT Fusion - ext4 delayed allocation failed errors on 4.14!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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_format=2
  SCCS=0  ACC=0  TPGS=0  3PC=0  Protect=0  [BQue=0]
  EncServ=0  MultiP=0  [MChngr=0]  [ACKREQQ=0]  Addr16=0
  [RelAdr=0]  WBus16=1  Sync=1  Linked=0  [TranDis=0]  CmdQue=1
    length=57 (0x39), but only fetched 56 bytes   Peripheral device type: disk
 Vendor identification: LSILOGIC
 Product identification: Logical Volume  
 Product revision level: 3000


root@siv-70140:~ # sg_vpd /dev/sda
Supported VPD pages VPD page:
  Supported VPD pages [sv]
  Device identification [di]
  Supported VPD pages [sv]
  Supported VPD pages [sv]

BR

nik


On Thu, Apr 12, 2018 at 10:31:58PM -0400, Martin K. Petersen wrote:
> 
> 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 : Illegal Request [current] 
> > [ 1895.101103] sd 4:1:1:0: [sda] tag#1 Add. Sense: No additional sense information
> 
> It's the "No additional sense information" that's the problem.
> 
> Under normal circumstances the drive would return "INVALID COMMAND
> OPCODE" or "INVALID FIELD IN CDB" in the additional sense data. That
> would cause us to disable WRITE SAME for the drive in question and
> report to the block layer that it should zero the blocks manually.
> 
> However, because we don't get any of the expected sense data back in
> your case, the failure manifests itself as a generic I/O failure to the
> stack. And that's why the error is reported up to ext4 instead of the
> block layer transparently doing fallback zeroing after WRITE SAME has
> been disabled.
> 
> What kind of drive is attached to your controller? SATA? SAS?
> 
> Please send us the output of:
> 
>        sg_inq /dev/sda
> 
> and
> 
>        sg_vpd /dev/sda
> 
> Thanks!
> 
> -- 
> Martin K. Petersen	Oracle Linux Engineering
> 

-- 
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28.rijna 168, 709 00 Ostrava

tel.:   +420 591 166 214
fax:    +420 596 621 273
mobil:  +420 777 093 799
www.linuxbox.cz

mobil servis: +420 737 238 656
email servis: servis@xxxxxxxxxxx
-------------------------------------



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]

  Powered by Linux