From owner-freebsd-fs@freebsd.org Thu Sep 20 13:05:56 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 13F5C109C2E7 for ; Thu, 20 Sep 2018 13:05:56 +0000 (UTC) (envelope-from theraven@freebsd.org) Received: from theravensnest.org (theravensnest.org [46.226.110.62]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "theravensnest.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 918DA8C492 for ; Thu, 20 Sep 2018 13:05:55 +0000 (UTC) (envelope-from theraven@freebsd.org) Received: from [10.164.186.139] ([167.220.196.139]) (authenticated bits=0) by theravensnest.org (8.15.2/8.15.2) with ESMTPSA id w8KD4lHE050912 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 20 Sep 2018 13:04:48 GMT (envelope-from theraven@freebsd.org) X-Authentication-Warning: mail: Host [167.220.196.139] claimed to be [10.164.186.139] Subject: Re: Fixing vdev name To: Alexander Leidinger , freebsd-fs@freebsd.org References: From: David Chisnall Message-ID: <58e2716e-5221-c529-d270-ba4e3b322fac@theravensnest.org> Date: Thu, 20 Sep 2018 14:05:46 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Sep 2018 13:05:56 -0000 [ Please keep me in the cc line - I'm not subscribed to this list ] >> Hello the list, >> >> I have a VM that uses ZFS with a pair of striped devices. The first >> is a partition on the root disk, created by the installer. When >> this was too small, I added another device (da1) and told the pool >> to expand to use it (no redundancy, because the underlying storage >> for the VM images provides that). After a reboot, I can no longer >> boot the system. Booting from the install CD and attempting to >> import the pool, it correctly identifies da0p4 as one of the >> devices, but gives me a long number instead of da1. > > This means ZFS doesn't see the other device (or more correctly no > device with the ZFS meta-data on the device which matches what the > pool wants to see as the second vdev). So there's been some corruption to the disk? > Do you see the second disk from non-ZFS tools? geom lists da1 as a device of the correct type, but zdb doesn't find any labels for it. > Does the partition info > look OK there (if you partitioned it before giving it to ZFS)? I dind't partition it, I just assigned the whole thing to ZFS. > Does the geometry/size look correct? Yup, in geom list it all looks sensible. > >> How do I fix this so that the pool again points to da1? > > As a side note, it doesn't matter if it is da1 or something else (e.g. > /dev/gpt/ or whatever), as long as it is a geom provider > instead of the uuid of the device like it seems to be the case right > now. So does this mean that something on the (virtual) disk was corrupted (sufficiently to remove both copies of the label and the uberblock)? David