From owner-freebsd-current@FreeBSD.ORG Sun Jul 6 12:18:25 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C706710656CA for ; Sun, 6 Jul 2008 12:18:25 +0000 (UTC) (envelope-from duncan.young@pobox.com) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id 7DC228FC1A for ; Sun, 6 Jul 2008 12:18:25 +0000 (UTC) (envelope-from duncan.young@pobox.com) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id CED0913739A for ; Sun, 6 Jul 2008 08:18:24 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Sun, 06 Jul 2008 08:18:24 -0400 X-Sasl-enc: MG5t/OLGaIKW+QtIuWb/gyZtU1wF177qVhI3DMVrr+5j 1215346704 Received: from triple0.qld.optushome.com.au (c122-108-168-198.rochd4.qld.optusnet.com.au [122.108.168.198]) by mail.messagingengine.com (Postfix) with ESMTPSA id 31FA1FE2A for ; Sun, 6 Jul 2008 08:18:24 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by triple0.qld.optushome.com.au (Postfix) with ESMTP id 80B26B25C7 for ; Sun, 6 Jul 2008 22:18:21 +1000 (EST) From: Duncan Young To: freebsd-current@freebsd.org Date: Sun, 6 Jul 2008 22:18:20 +1000 User-Agent: KMail/1.9.7 References: <200807062143.14016.duncan.young@pobox.com> In-Reply-To: <200807062143.14016.duncan.young@pobox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807062218.20956.duncan.young@pobox.com> Subject: Re: zfs and glabel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: duncan.young@pobox.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jul 2008 12:18:26 -0000 Forgot to mention, all these messages are a result of vfs.zfs.debug=1, so should I assume this is normal behaviour?? The "Cannot open ad2 for writting" occur regardless of the debug setting. regards Duncan On Sun, 6 Jul 2008 09:43:12 pm Duncan Young wrote: > 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