From owner-freebsd-chat@FreeBSD.ORG Wed Aug 11 14:14:08 2010 Return-Path: Delivered-To: freebsd-chat@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65B8A1065674 for ; Wed, 11 Aug 2010 14:14:08 +0000 (UTC) (envelope-from oskars.games@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1B1AB8FC2C for ; Wed, 11 Aug 2010 14:14:07 +0000 (UTC) Received: by qyk32 with SMTP id 32so223285qyk.13 for ; Wed, 11 Aug 2010 07:14:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=1eFM5Rs4+sMKG3Advuq+5YhD4KqKnNLOKXDoY/TSIYE=; b=WPZN5oOLDj1cMbNIO8gQjJ1IcA44kRgUKWi5jvvQWb03z0uSphXwDPOW8sG92N90wV RV7jbzqYO3h6IpFx6K/Oya8ktQgO9wk6PEz9wNfVprg7zfWR22OJVBgJVaLn0HXZj4Y2 mxDi/AGnOpR7PxdeeCnLSbSbGMeVfpQIqDVh4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=nfytNqmCQbqxd2xm7n9t3rtqnP5R9eg/9ImWklXNlyMS5IpJPOZb1IX/GlD/CpfGYJ BZvtEe09bLzxhDEuCtQQLN4HtejnUC7AyghL3GkV54dDHn6VeoAd8tUTp0Wff7tjHGVG fY31CKJlfzfcHJFPwO2rV4ueBzutz+ahwDUZg= MIME-Version: 1.0 Received: by 10.224.54.134 with SMTP id q6mr10706623qag.377.1281534719103; Wed, 11 Aug 2010 06:51:59 -0700 (PDT) Received: by 10.224.67.84 with HTTP; Wed, 11 Aug 2010 06:51:59 -0700 (PDT) Date: Wed, 11 Aug 2010 16:51:59 +0300 Message-ID: From: Oskar Ahlgren To: freebsd-chat@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: glabel is lost X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Aug 2010 14:14:08 -0000 Hi everyone, I have a problem with a lost glabel. I used the following command # glabel label -v WCD3 /dev/ad16 to label the disk. Afterwards I checked that the label was indeed working, by checking the content in the /dev/label folder. Then I replaced a failed disk in a pool with # zpool replace ztuff label/WCD label/WCD3 and the system started scrubing. When I checked it later the label was lost and the drive ad16 was included in the pool instead. As a result the pool is still degraded according to the system as the original disk is unavailible. What should I do? I just dont want to destroy the pool and create a new one. To avoid that was the point of introducing the labels to begin with... I'm running 8.0 RC3, but I want to upgrade to 8.1 release. But for some reason I wasnt able to connect to the server. Can the label troubble have something to do with the OS version? I hope someone has an idea about what to do. \oskar