Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 31 Oct 2012 13:48:19 -0700
From:      Artem Belevich <art@freebsd.org>
To:        Steven Hartland <killing@multiplay.co.uk>
Cc:        freebsd-fs@freebsd.org, freebsd-stable@freebsd.org
Subject:   Re: ZFS corruption due to lack of space?
Message-ID:  <CAFqOu6hkB4%2BWHbcPSyRhBOWcRHqehYmh-40XH_iGTjekNK-7eg@mail.gmail.com>
In-Reply-To: <A394192F694F49488291020AB9FBF00E@multiplay.co.uk>
References:  <27087376D1C14132A3CC1B4016912F6D@multiplay.co.uk> <A394192F694F49488291020AB9FBF00E@multiplay.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 31, 2012 at 10:55 AM, Steven Hartland
<killing@multiplay.co.uk> wrote:
> At that point with the test seemingly successful I went
> to delete test files which resulted in:-
> rm random*
> rm: random1: Unknown error: 122

ZFS is a logging filesystem. Even removing a file apparently requires
some space to write a new record saying that the file is not
referenced any more.

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.

Good luck,
--Artem



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFqOu6hkB4%2BWHbcPSyRhBOWcRHqehYmh-40XH_iGTjekNK-7eg>