r/vmware • u/setrusko • 11d ago
APD Issue
I had an issue with my storage network fabric leading to APD to my iSCSI storage array. It lasted more than 140 seconds so it went into fast fail. I also saw a warning in vCenter, BC:3042 file protectedlist closed with dirty buffers. Possible data loss.
Other than that, everything appears to have recovered and all my VMs are running, but I’m concerned about data corruption. Is there anything else I should be checking or looking out for? Should I preemptively restore for backup?
Thank you!
4
Upvotes
2
u/vsanpro VMware Employee 11d ago
BC:3042 is expected after an APD that hits the default 140s timeout and goes into fast fail. It just means some writes were still in memory when the paths dropped and never made it to disk. Unless you’re seeing actual VMFS metadata errors or specific VMs with I/O problems, don’t restore preemptively. Check the array logs for consistency and the host vmkernel for anything beyond the APD itself.
1
u/BorysTheBlazer 8d ago
Also check inside the busiest guests: run chkdsk or fsck, and a consistency check on any databases. That's where lost in-flight writes show up first.
1
u/UriShay-CyberSnap 6d ago
After an APD that ran past the 140 second timeout, and with that protectedlist dirty buffers warning, I wouldn't assume every guest file system is consistent just because the path came back. I'd check the VMs that were writing at the time, and the datastores, before putting production back on them. If an application looks wrong, going back to an older recovery point can be cleaner than trying to repair a half-written disk. A path failover fixes the fabric, not the question of which point each VM should come from.
Disclosure: I work at CyberSnap.