[Bug 236042] Windows Server 2016 Hyper-V snapshot triggers SCSI errors
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236042 Juraj Lutter changed: What|Removed |Added CC||ju...@lutter.sk --- Comment #14 from Juraj Lutter --- FWIW, I'm seeing this with recent 12-STABLE as well. I will review Andriy's patch. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 236042] Windows Server 2016 Hyper-V snapshot triggers SCSI errors
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236042 --- Comment #13 from Dexuan Cui --- (In reply to Michael from comment #11) When you see the SCSI errors, can the live backup procedure succeed? Do you notice any instability issue (e.g.hang/panic)? Do you notice any data corruption issue (e.g. the back-up procedure says it succeeded, but later you may find that the data is not really consistently backed up, i.e. 'fsck' may run while you think it should not)? If the backup procedure still succeeds, and you never notice any real issue, then I think it should be safe to ignore the SCSI error messages -- if we want to get rid of the messages, it looks sys/dev/hyperv/utilities/hv_snapshot.c is not an issue -- it looks we need to improve sys/dev/hyperv/storvsc/hv_storvsc_drv_freebsd.c and/or the other part of SCSI subsystem. Linux VM on Hyper-V shows the same/similar messages when Hyper-V live backup is being performed (at least this was the case in June 2017): sd 2:0:0:0: [storvsc] Sense Key : Unit Attention [current] sd 2:0:0:0: [storvsc] Add. Sense: Changed operating definition sd 2:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. These messages in a Linux VM can be seen even if the back-up is successful, so it looks people just ignore the messages in Linux. The messages are caused as a result of the way how Hyper-V live-backup works: usually the VM's .vhdx file has a block size of 32MB, and during the live-backup procedure IIRC it looks a temporary .avhdx of a 2MB block size is generated and the host returns sense key "Unit Attention" with asc 0x3f and ascq 0x2 (Changed Operating Definition); the host sends "Unit Attention" because the backing VHD block size has changed after checkpoint or backup and this results in a change in the granularity of the UNMAP. Linux SCSI layer can deal with the following asc 0x3f on Unit Attention: ascq 0x3 (Inquiry Data Has Changed) ascq 0xe (Reported Luns Data Has Changed) However ascq 0x2 is ignored. The SCSI won’t know the UNMAP granularity change, it will run at probably slower UNMAP but won’t affect other parts. Note: I excerpted the above details from a 2017 email discussing the SCSI errors in a Linux VM on Hyper-V. My understanding is that the messages can be safely ignored in Linux, but I'm not sure about FreeBSD, as the SCSI subsystem in FreeBSD may handle the sense info in a different manner. I have moved on to different projects, so I am sorry I can not follow this up... I hope someone would find the info I shared here is useful, in case something has to be done in FreeBSD VM. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 236042] Windows Server 2016 Hyper-V snapshot triggers SCSI errors
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236042 meichthys changed: What|Removed |Added CC||mattbju2...@gmail.com --- Comment #12 from meichthys --- I am also seeing this when Veeam takes a snapshot of my HyperV VM running FreeNAS. FreeNAS seems to lock up for a short amount of time and then seems to recover after a few minutes. (da1:storvsc1:0:0:0): WRITE(10). CDB: 2a 00 2c 10 8e 88 00 00 08 00 (da1:storvsc1:0:0:0): CAM status: SCSI Status Error (da1:storvsc1:0:0:0): SCSI status: Check Condition (da1:storvsc1:0:0:0): SCSI sense: UNIT ATTENTION asc:3f,2 (Changed operating definition) (da1:storvsc1:0:0:0): Retrying command (per sense data) Hyperv-2019 FreeNAS-11.3-U1 Veeam Backup & Replication 10 (For HyperV VM replication) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 236042] Windows Server 2016 Hyper-V snapshot triggers SCSI errors
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236042 --- Comment #11 from Michael --- (In reply to Andriy Gapon from comment #10) Did not help. Messages one to one after applying this patch and make cleanworld && make cleandir && make -j8 buildworld && make -j8 buildkernel KERNCONF=GENERIC -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 236042] Windows Server 2016 Hyper-V snapshot triggers SCSI errors
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236042 Andriy Gapon changed: What|Removed |Added CC||a...@freebsd.org --- Comment #10 from Andriy Gapon --- Created attachment 209124 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209124=edit proposed patch, ported from Linux Could anyone observing the problem please test this patch? Thanks! P.S. There is a review request for it as well: https://reviews.freebsd.org/D22313 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 236042] Windows Server 2016 Hyper-V snapshot triggers SCSI errors
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236042 --- Comment #9 from Michael --- Linux seems to have the same problem: https://bugzilla.redhat.com/show_bug.cgi?id=1502601 I wonder if FreeBSD solved it or not? ...But the output of SCSI Status Error messages in FreeBSD is very similar to the already resolved problem in Linux. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 236042] Windows Server 2016 Hyper-V snapshot triggers SCSI errors
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236042 Michael changed: What|Removed |Added CC||michael@gmail.com --- Comment #8 from Michael --- I can confirm that I have the same SCSI errors during HyperV snapshots. FreeBSD from 11.2 to current 13.0 have this problem. Also this problem and on ZFS too. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 236042] Windows Server 2016 Hyper-V snapshot triggers SCSI errors
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236042 Nick changed: What|Removed |Added CC||n...@njctech.com --- Comment #7 from Nick --- I am having this problem with PFSense (2.4.4-RELEASE-p3) running on Hyper-V (Windows 2012 R2). In my case, replication might run fine for a while (hours, days) but at some point there is a SCSI Status Error during a WRITE operation and PFSense/FreeBSD will become locked up or partially working but eventually will not respond to network or UI requests. I would love a resolution to this. For the moment, I've disabled replication and it's been fine. Perhaps useful, perhaps not: I've been running PFSense for years as a replicating VM on Hyper-V W2K2012R2 without issues. It was just this week when I started having problems. PFSense was previously running many different versions (2.2, 2.3, 2.4.3). When I started having problems this week I had not upgraded PFSsense or the hypervisor. As far as I can tell "nothing changed". Nick -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 236042] Windows Server 2016 Hyper-V snapshot triggers SCSI errors
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236042 thomaslauer changed: What|Removed |Added CC||la...@glsh.net --- Comment #6 from thomaslauer --- Hi, i have 120 PFSense VMs from 2.3.4 to 2.4.4-2 all Hyperv VMs with GEN2 and UFS. and some vms with Hyperv GEN2 and UFS. All this VM has the same issue. I have only one VM with GEN2 and ZFS. This VM has no SCSI Errors during the snapshot. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 236042] Windows Server 2016 Hyper-V snapshot triggers SCSI errors
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236042 Alex G changed: What|Removed |Added Severity|Affects Only Me |Affects Many People -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 236042] Windows Server 2016 Hyper-V snapshot triggers SCSI errors
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236042 --- Comment #5 from Gesture --- I'm using FreeBSD 11.2 and a pfSense 2.4.4 HyperV Virtual machine -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 236042] Windows Server 2016 Hyper-V snapshot triggers SCSI errors
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236042 --- Comment #4 from Gesture --- Hi, I can confirm that I have the same SCSI errors during HyperV snapshots. Greetings Gesture -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 236042] Windows Server 2016 Hyper-V snapshot triggers SCSI errors
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236042 Gesture changed: What|Removed |Added CC||gluk...@hotmail.com --- Comment #3 from Gesture --- Created attachment 203786 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203786=edit SCSI error during snapshot -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 236042] Windows Server 2016 Hyper-V snapshot triggers SCSI errors
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236042 j.mori...@educationetformation.fr changed: What|Removed |Added CC||j.morillo@educationetformat ||ion.fr --- Comment #2 from j.mori...@educationetformation.fr --- I'm also having same problem with different setup: - HyperV 2016 with OPNSense as Guest (FreeBSD 11.1-RELEASE-p17) This VM has a replicate on another HyperV wich often failed (need to force sync again). Here is FreeBSD log: (da0:storvsc0:0:0:0): WRITE(10). CDB: 2a 00 00 cd ac a8 00 01 00 00 (da0:storvsc0:0:0:0): CAM status: SCSI Status Error (da0:storvsc0:0:0:0): SCSI status: Check Condition (da0:storvsc0:0:0:0): SCSI sense: UNIT ATTENTION asc:3f,2 (Changed operating definition) (da0:storvsc0:0:0:0): Retrying command (per sense data) (da0:storvsc0:0:0:0): WRITE(10). CDB: 2a 00 00 ca 90 68 00 00 40 00 (da0:storvsc0:0:0:0): CAM status: SCSI Status Error (da0:storvsc0:0:0:0): SCSI status: Check Condition (da0:storvsc0:0:0:0): SCSI sense: UNIT ATTENTION asc:3f,2 (Changed operating definition) (da0:storvsc0:0:0:0): Retrying command (per sense data) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
[Bug 236042] Windows Server 2016 Hyper-V snapshot triggers SCSI errors
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236042 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|virtualizat...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
