From owner-freebsd-fs@FreeBSD.ORG  Wed Oct 31 21:31:55 2012
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
 by hub.freebsd.org (Postfix) with ESMTP id 3CB246B3;
 Wed, 31 Oct 2012 21:31:55 +0000 (UTC)
 (envelope-from rysto32@gmail.com)
Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com
 [209.85.220.182])
 by mx1.freebsd.org (Postfix) with ESMTP id BC51A8FC08;
 Wed, 31 Oct 2012 21:31:54 +0000 (UTC)
Received: by mail-vc0-f182.google.com with SMTP id fw7so2677243vcb.13
 for <multiple recipients>; Wed, 31 Oct 2012 14:31:53 -0700 (PDT)
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=pqae7FdZL9WSNEyXswPexnAL8jbV6Tbp5y/vgv0k7p4=;
 b=uw5ULVVR846/dl4pIqKwM5SPxaIIxz3vsVK/OVrn2vI67Lt84m5cuIlZaFZNQcHgOV
 TpXY/d5rDZily61UxCFtIgTb5XKaddPQqOEHItmFGFfIv1lBPnUBxLNSFgMH26zDNFSv
 O6TOiol/Fh6wysY6ggzKhS1kaTmb9wlVg/Yp4K9WgPI22Hh/hd0qzpWjwuEz8Eg0MLnd
 S/n6geoiP/EQdytOMjhW5Q14O6WlTgOOEnQNzv5hPXKPg9PlFOfysh0GUTNJVJR1uetB
 Ac1GOW4x9Us0K2Yu0o2J90GIh8j6oM6klRatvlHrIyhC8kum3uVLmU/+pVEx530Bm5Fc
 +2dA==
MIME-Version: 1.0
Received: by 10.52.155.199 with SMTP id vy7mr50194247vdb.54.1351719113870;
 Wed, 31 Oct 2012 14:31:53 -0700 (PDT)
Received: by 10.58.207.114 with HTTP; Wed, 31 Oct 2012 14:31:53 -0700 (PDT)
In-Reply-To: <CAFqOu6hkB4+WHbcPSyRhBOWcRHqehYmh-40XH_iGTjekNK-7eg@mail.gmail.com>
References: <27087376D1C14132A3CC1B4016912F6D@multiplay.co.uk>
 <A394192F694F49488291020AB9FBF00E@multiplay.co.uk>
 <CAFqOu6hkB4+WHbcPSyRhBOWcRHqehYmh-40XH_iGTjekNK-7eg@mail.gmail.com>
Date: Wed, 31 Oct 2012 17:31:53 -0400
Message-ID: <CAFMmRNytJ+nRA2j6-TSEG9CKck_bVRGZ-wftZ1MSLojPETW88w@mail.gmail.com>
Subject: Re: ZFS corruption due to lack of space?
From: Ryan Stone <rysto32@gmail.com>
To: Artem Belevich <art@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Oct 2012 21:31:55 -0000

On Wed, Oct 31, 2012 at 4:48 PM, Artem Belevich <art@freebsd.org> wrote:
> One way out of this jam is to try truncating some large file in place.
> Make sure that file is not part of any snapshot.
> Something like this may do the trick:
> #dd if=/dev/null of=existing_large_file
>
> Or, perhaps even something as simple as 'echo -n > large_file' may work.

truncate -s 0?