From owner-freebsd-stable@FreeBSD.ORG Sat Dec 29 03:48:10 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4E402BAE; Sat, 29 Dec 2012 03:48:10 +0000 (UTC) (envelope-from greg.bonett@gmail.com) Received: from mail-vc0-f181.google.com (mail-vc0-f181.google.com [209.85.220.181]) by mx1.freebsd.org (Postfix) with ESMTP id 789F48FC08; Sat, 29 Dec 2012 03:48:09 +0000 (UTC) Received: by mail-vc0-f181.google.com with SMTP id gb30so11236320vcb.40 for ; Fri, 28 Dec 2012 19:48:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ncjkxSAoOt2LrvynKH4eygO1vt7B50JQ9Knqs+YI06A=; b=paDCMMnwEP6eu/+tj9yGw0us8XQTZoskNPJ4iAv8/yYaT4itq43AofkGnFRoFgRvB8 8y6KrMLCvCWDVge18fH7hFrgEsVeR0tuYHHcLgBt4rHIjpuERjfN8FZ9Mg3btJGNcAgB UB6+0bN2EUkfeAc+pzmfxo2LgciKXcLLlmXx3WuN4uhq6trjyHofPeRVZgndq70HXtNu cCyxjiDSwK2WKBu9o4yAbG1M4TewKDg/Z7G47L8i3dxRWoa+7lcpgUyNGv3cLY2FcyO/ 8nRo7KhfeHI7BrPD9W8g6F+ZWk9eNCxHdnjTraHiau5vzfReud0LH7cXZHn8++ymijyO SwYw== MIME-Version: 1.0 Received: by 10.220.106.147 with SMTP id x19mr54354908vco.37.1356752882722; Fri, 28 Dec 2012 19:48:02 -0800 (PST) Received: by 10.58.40.33 with HTTP; Fri, 28 Dec 2012 19:48:02 -0800 (PST) In-Reply-To: References: Date: Sat, 29 Dec 2012 03:48:02 +0000 Message-ID: Subject: Re: how to destroy zfs parent filesystem without destroying children - corrupted file causing kernel panick From: Greg Bonett To: Artem Belevich Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Dec 2012 03:48:10 -0000 ahh, unfortunately the filesystem I want to destroy is the top-most file system for the pool. Does this mean I'll need to set up another pool with enough free space to move everything over? Any ideas for a way to remove the corrupted file without destroying the file system? thanks! On Sat, Dec 29, 2012 at 3:35 AM, Artem Belevich wrote: > > On Fri, Dec 28, 2012 at 12:46 PM, Greg Bonett wrote: > >> However, I can't figure out how to destroy the /tank filesystem without >> destroying /tank/tempfs (and the other /tank children). Is it possible to >> destroy a parent without destroying the children? Or, create a new parent >> zfs file system on the same zpool and move the /tank children there before >> destroying /tank? >> > > It is possible in case parent is not the top-most zfs filesystem (i.e > tomp-most filesystem for the pool). > > I.e. if your zfs filesystem layout looked like zfs-pool/tank/tempfs, then > you could simply do "zfs rename zfs-pool/tank/tempfs zfs-pool/tempfs" and > then would be free to remove zfs-pool/tank. Alas this rename semantics > breaks down when you can no longer rename sub-filesystem upward. I don't > think ZFS would allow you to promote inner filesystem to a pool which is > what you seem to want. > > --Artem >