That should be just as safe or unsafe as running fsck on the UFS file system that is using a disk directly. Fsck interacts with the UFS file system only, and does not know what the underlying block storage layer is, whether it is a single physical disk or a gmirror "virtual" disk.
It is ok to run fsck on a gmirror, expecially if the mirror has Status=COMPLETE.
In case of DEGRADED mirror you need to completely understand what you doing.
You should not shutdown a mirror and run fsch on disks who are members of the mirror without following array rebuild because having some "balance algorithms" you may got a mess instead of your data.
It may be a good idea to add to the /etc/rc.conf
Code:
fsck_y_enable="YES"
background_fsck="NO"
FreeBSD will run fsck by itself when required and will try to resolve issues without interrupting boot process.
It will slowdown boot process after unclean shutdown on large disks.
p.s.
I prefer to use a gmirror's balance algorithm "prefer" (Read from the component with the biggest priority) on machines where I am expecting high number of unclean shutdowns. It allows to configure like a primary disk of the mirror by setting its priority, and the gmirror will always use it for read requests until it exists.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
