Goose
Dabbler
- Joined
- Oct 4, 2014
- Messages
- 25
I get these, occasionally.
Nov 28 03:45:00 mother-goose ZFS: vdev state changed, pool_guid=4753035133703495120 vdev_guid=15343288276930064957
Nov 28 03:45:00 mother-goose ZFS: vdev state changed, pool_guid=4753035133703495120 vdev_guid=17738397629967930008
I read on a few threads that VMs might, perhaps, be the cause of this but most of the posts mention that it could be to do with disks that are set to powersave. Mine aren't but I am trialling a Windows 10 VM and maybe that is the link. I also have a couple of iSCSI drives also running off physical machines and a VM running on VBox on a laptop I had lying around.
No errors on any of the host OSes.
I'm happy to switch off the FreeNAS VM to see if the error goes but that isn't a good test as the errors are that infrequent.
Is there a way to see what vdev was changed and what it was being used by at the time?
Cheers,
Goose
Nov 28 03:45:00 mother-goose ZFS: vdev state changed, pool_guid=4753035133703495120 vdev_guid=15343288276930064957
Nov 28 03:45:00 mother-goose ZFS: vdev state changed, pool_guid=4753035133703495120 vdev_guid=17738397629967930008
I read on a few threads that VMs might, perhaps, be the cause of this but most of the posts mention that it could be to do with disks that are set to powersave. Mine aren't but I am trialling a Windows 10 VM and maybe that is the link. I also have a couple of iSCSI drives also running off physical machines and a VM running on VBox on a laptop I had lying around.
No errors on any of the host OSes.
I'm happy to switch off the FreeNAS VM to see if the error goes but that isn't a good test as the errors are that infrequent.
Is there a way to see what vdev was changed and what it was being used by at the time?
Cheers,
Goose