Hi all
This is the first time I could not resolve an issue by checking the information that is somewhere in forums or handbooks, so I really hope for your help on this:
I have a hardware machine that runs release 11p6. The filesystem is ZFS on two SSDs in mirror mode.
On this machine I have 4 virtual machines running. They use zvols with volmode=dev, volblksize 32k as devices in bhyve (I use chyves as a frontend).
Inside the VMs I have again release 11p6, this time with UFS/Swap (mostly default configuration).
Everything works fine. But if i do a fsck on the guest, it reports random errors (see bottom). I say random, because the list changes every time I run fsck. Switching to single user mode, really fix the errors and go back multi user changes nothing.
I am mildly scared, that something terrible happens over time and I am just not aware of it yet...
What am I missing or what am I doing wrong...?
Many thanks for your help,
Marco
[/CODE]
This is the first time I could not resolve an issue by checking the information that is somewhere in forums or handbooks, so I really hope for your help on this:
I have a hardware machine that runs release 11p6. The filesystem is ZFS on two SSDs in mirror mode.
On this machine I have 4 virtual machines running. They use zvols with volmode=dev, volblksize 32k as devices in bhyve (I use chyves as a frontend).
Inside the VMs I have again release 11p6, this time with UFS/Swap (mostly default configuration).
Everything works fine. But if i do a fsck on the guest, it reports random errors (see bottom). I say random, because the list changes every time I run fsck. Switching to single user mode, really fix the errors and go back multi user changes nothing.
I am mildly scared, that something terrible happens over time and I am just not aware of it yet...
What am I missing or what am I doing wrong...?
Many thanks for your help,
Marco
Code:
#####
** /dev/ada0p2 (NO WRITE)
USE JOURNAL? no
** Skipping journal, falling through to full fsck
SETTING DIRTY FLAG IN READ_ONLY MODE
UNEXPECTED SOFT UPDATE INCONSISTENCY
** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
UNREF FILE I=810042 OWNER=root MODE=100644
SIZE=0 MTIME=Jan 3 15:17 2017
RECONNECT? no
CLEAR? no
UNREF FILE I=810045 OWNER=root MODE=100644
SIZE=0 MTIME=Jan 3 15:17 2017
RECONNECT? no
CLEAR? no
UNREF FILE I=810049 OWNER=root MODE=100644
SIZE=0 MTIME=Jan 3 15:17 2017
RECONNECT? no
CLEAR? no
** Phase 5 - Check Cyl groups
SUMMARY INFORMATION BAD
SALVAGE? no
BLK(S) MISSING IN BIT MAPS
SALVAGE? no
262128 files, 1120140 used, 806227 free (5811 frags, 100052 blocks, 0.3% fragmentation)
#####[CODE]