Project

General

Profile

Bug #76531

Do not poll for temperature on drives with SMART disabled

Added by Bug Clerk almost 3 years ago. Updated over 2 years ago.

Status:
Done
Priority:
No priority
Assignee:
Vladimir Vinogradenko
Category:
Middleware
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Hi Team,

I have been running FreeNAS as a VM in ESXi 6.0 for years and it has been flawless. Recently, I upgraded to 11.2 and just discovered new messages showing up in the vmkernel.log of the host every 5 minutes that were not present in 11.1. The SCSI devices it is referring to are .VMDK disks used for Boot and Jails storage. There are no error messages seen to any of the HDD disks connected to the PCI Passthrough Controller (zpool).

2019-01-02T13:00:13.831Z cpu4:35434)VSCSIFs: 2235: handle 8194(vscsi1:0):Invalid Opcode (0x4d) from (vmm0:FreeNAS-11)
2019-01-02T13:00:13.831Z cpu7:35433)VSCSIFs: 2235: handle 8195(vscsi1:1):Invalid Opcode (0xb7) from (vmm0:FreeNAS-11)
2019-01-02T13:00:13.831Z cpu4:35434)VSCSIFs: 2235: handle 8194(vscsi1:0):Invalid Opcode (0xb7) from (vmm0:FreeNAS-11)
2019-01-02T13:00:13.831Z cpu10:35431)VSCSIFs: 2235: handle 8195(vscsi1:1):Invalid Opcode (0x37) from (vmm0:FreeNAS-11)
2019-01-02T13:00:13.831Z cpu7:35433)VSCSIFs: 2235: handle 8194(vscsi1:0):Invalid Opcode (0x37) from (vmm0:FreeNAS-11)
2019-01-02T13:05:13.820Z cpu11:35433)VSCSIFs: 2235: handle 8195(vscsi1:1):Invalid Opcode (0x4d) from (vmm0:FreeNAS-11)
2019-01-02T13:05:13.820Z cpu11:35433)VSCSIFs: 2235: handle 8195(vscsi1:1):Invalid Opcode (0x4d) from (vmm0:FreeNAS-11)
2019-01-02T13:05:13.820Z cpu11:35433)VSCSIFs: 2235: handle 8194(vscsi1:0):Invalid Opcode (0x4d) from (vmm0:FreeNAS-11)
2019-01-02T13:05:13.820Z cpu1:35434)VSCSIFs: 2235: handle 8194(vscsi1:0):Invalid Opcode (0x4d) from (vmm0:FreeNAS-11)
2019-01-02T13:05:13.820Z cpu1:35434)VSCSIFs: 2235: handle 8195(vscsi1:1):Invalid Opcode (0xb7) from (vmm0:FreeNAS-11)
2019-01-02T13:05:13.820Z cpu1:35434)VSCSIFs: 2235: handle 8194(vscsi1:0):Invalid Opcode (0xb7) from (vmm0:FreeNAS-11)
2019-01-02T13:05:13.820Z cpu1:35434)VSCSIFs: 2235: handle 8195(vscsi1:1):Invalid Opcode (0x37) from (vmm0:FreeNAS-11)
2019-01-02T13:05:13.820Z cpu1:35434)VSCSIFs: 2235: handle 8194(vscsi1:0):Invalid Opcode (0x37) from (vmm0:FreeNAS-11)
2019-01-02T13:05:13.824Z cpu11:35433)VSCSIFs: 2235: handle 8193(vscsi0:0):Invalid Opcode (0x4d) from (vmm0:FreeNAS-11)
2019-01-02T13:05:13.824Z cpu7:35435)VSCSIFs: 2235: handle 8193(vscsi0:0):Invalid Opcode (0x4d) from (vmm0:FreeNAS-11)
2019-01-02T13:05:13.824Z cpu7:35435)VSCSIFs: 2235: handle 8193(vscsi0:0):Invalid Opcode (0xb7) from (vmm0:FreeNAS-11)
2019-01-02T13:05:13.824Z cpu7:35435)VSCSIFs: 2235: handle 8193(vscsi0:0):Invalid Opcode (0x37) from (vmm0:FreeNAS-11)
2019-01-02T13:10:13.824Z cpu10:35434)VSCSIFs: 2235: handle 8194(vscsi1:0):Invalid Opcode (0x4d) from (vmm0:FreeNAS-11)
2019-01-02T13:10:13.824Z cpu10:35434)VSCSIFs: 2235: handle 8194(vscsi1:0):Invalid Opcode (0x4d) from (vmm0:FreeNAS-11)
2019-01-02T13:10:13.824Z cpu6:35433)VSCSIFs: 2235: handle 8193(vscsi0:0):Invalid Opcode (0x4d) from (vmm0:FreeNAS-11)

Looking at the SCSI commands, they include 'Log Sense' and 'Read Defect Data'. Most likely, these commands are not supported by the VMDK virtual disks and throw this message instead. Curious as I had not seen this before on any previous version of FreeNAS.

Also note, SMART is disabled for these VMDK devices but is enabled for the HDD connected to the PCI Passthrough controller.

We have also started chatting about it - https://forums.freenas.org/index.ph...-to-a-pool-every-5-minutes.70574/#post-500044

and -

https://forums.freenas.org/index.php?threads/virtualized-freenas-11-2-esxi-6-0-vmkernel-log-full-of-vscsi-invalid-opcode-messages.72206/#post-501751

As I understand it, there is little to no impact from these messages but I am still puzzled as I hadn't seen any of these in previous versions. Is there anything that can be done to avoid sending these SCSI Commands to VMDK disks? Were there any changes made on this topic from the previous version 11.1?


Related issues

Copied from FreeNAS - Bug #66927: Virtualized FreeNAS 11.2 ESXi 6.0 - vmkernel.log full of vscsi Invalid Opcode messagesDone

History

#1 Updated by Bug Clerk almost 3 years ago

  • Copied from Bug #66927: Virtualized FreeNAS 11.2 ESXi 6.0 - vmkernel.log full of vscsi Invalid Opcode messages added

#2 Updated by Bug Clerk almost 3 years ago

  • Target version changed from Master - FreeNAS Nightlies to 11.2-U3

#3 Updated by Bug Clerk almost 3 years ago

  • Status changed from Unscreened to In Progress

#4 Updated by Vladimir Vinogradenko almost 3 years ago

Acceptance Criteria

When you disable SMART for specific HDD, it should stop showing it's temperature graph (historic data will remain, but new shouldn't be added)

#5 Updated by Bug Clerk almost 3 years ago

  • Status changed from In Progress to Ready for Testing

#6 Updated by Dru Lavigne almost 3 years ago

  • Subject changed from Virtualized FreeNAS 11.2 ESXi 6.0 - vmkernel.log full of vscsi Invalid Opcode messages to Do not poll for temperature on drives with SMART disabled
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#9 Avatar?id=55038&size=24x24 Updated by Zackary Welch over 2 years ago

  • Status changed from Ready for Testing to Passed Testing
  • Needs QA changed from Yes to No

Confirmed fixed in 11.2-U3.

#10 Updated by Dru Lavigne over 2 years ago

  • Needs Doc changed from No to Yes

#12 Updated by Dru Lavigne over 2 years ago

  • Status changed from Passed Testing to Done
  • Needs Doc changed from Yes to No

Also available in: Atom PDF