Date: Wed, 31 Oct 2012 17:31:53 -0400 From: Ryan Stone <rysto32@gmail.com> To: Artem Belevich <art@freebsd.org> Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: ZFS corruption due to lack of space? Message-ID: <CAFMmRNytJ%2BnRA2j6-TSEG9CKck_bVRGZ-wftZ1MSLojPETW88w@mail.gmail.com> In-Reply-To: <CAFqOu6hkB4%2BWHbcPSyRhBOWcRHqehYmh-40XH_iGTjekNK-7eg@mail.gmail.com> References: <27087376D1C14132A3CC1B4016912F6D@multiplay.co.uk> <A394192F694F49488291020AB9FBF00E@multiplay.co.uk> <CAFqOu6hkB4%2BWHbcPSyRhBOWcRHqehYmh-40XH_iGTjekNK-7eg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFMmRNytJ%2BnRA2j6-TSEG9CKck_bVRGZ-wftZ1MSLojPETW88w>