zfs and glabel
Duncan Young
duncan.young at pobox.com
Sun Jul 6 12:00:51 UTC 2008
Hi all
I believe I'm having a few problems with using geom to label disks and then
use them in zfs.
# zpool status rootzfs
pool: rootzfs
state: ONLINE
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
rootzfs ONLINE 0 0 0
mirror ONLINE 0 0 0
label/sysdisk_A ONLINE 0 0 0
label/sysdisk_B ONLINE 0 0 0
errors: No known data errors
# glabel status
Name Status Components
label/bootdisk_A N/A ad0s1a
label/swap_A N/A ad0s1b
label/sysdisk_A N/A ad0s1d
label/bootdisk_B N/A ad2s1a
label/swap_B N/A ad2s1b
label/sysdisk_B N/A ad2s1d
# gmirror status
Name Status Components
mirror/swap_AB COMPLETE label/swap_A
label/swap_B
# swapinfo
Device 1K-blocks Used Avail Capacity
/dev/mirror/swap_AB 4194300 158224 4036076 4%
# mount -t ufs
/dev/label/bootdisk_A on /bootdirA (ufs, local)
/dev/label/bootdisk_B on /bootdirB (ufs, local)
As can be seen I have the boot disk set up with separate /boot partitions
(independent of each other), mirrored swap and the rest of the root file
system in zfs.
Currently I am watching the following appearing every second or two in the
messages file:
kernel: vdev_geom_detach:177[1]: Closing access to label/sysdisk_B.
kernel: vdev_geom_detach:177[1]: Closing access to label/sysdisk_A.
kernel: vdev_geom_detach:181[1]: Destroyed consumer to label/sysdisk_A.
kernel: vdev_geom_detach:177[1]: Closing access to label/sysdisk_B.
kernel: vdev_geom_detach:181[1]: Destroyed consumer to label/sysdisk_B.
kernel: vdev_geom_open:371[1]: Found provider by name /dev/label/sysdisk_A.
kernel: vdev_geom_attach:116[1]: Attaching to label/sysdisk_A.
kernel: vdev_geom_attach:157[1]: Created consumer for label/sysdisk_A.
kernel: vdev_geom_open:385[1]: ID match for provider /dev/label/sysdisk_A.
kernel: vdev_geom_open:371[1]: Found provider by name /dev/label/sysdisk_B.
kernel: vdev_geom_attach:116[1]: Attaching to label/sysdisk_B.
kernel: vdev_geom_attach:157[1]: Created consumer for label/sysdisk_B.
kernel: vdev_geom_open:385[1]: ID match for provider /dev/label/sysdisk_B.
much of the time only one disk is "lost" at a time.
I also get "kernel: ZFS WARNING: Cannot open ad2 for writting" (also for ad0)
upon imports etc.
I'm running 7.0-RELEASE-p2 on amd64.
I also have another raidz set of 6 disks, but I don't use labels on them and
have no messages as a result.
Any suggestions if I should be concerned or not.
I also have periodic lockups (under load) which I believe are zfs related, but
I have only just set up the serial console and I am waiting to get a crash
dump.
regards
Duncan
More information about the freebsd-current
mailing list