Date: Thu, 30 Jul 2009 01:22:31 -0400 From: grarpamp <grarpamp@gmail.com> To: freebsd-stable@freebsd.org Subject: Re: Cannot rm files when ZFS is full Message-ID: <d2e731a10907292222t6f4c02ebn3895ba9efc0d4f01@mail.gmail.com> In-Reply-To: <14989d6e0907290025i499c71fbn289b64a7da0e4b97@mail.gmail.com> References: <d2e731a10907282029rd17ca1ag892c3c9615e76140@mail.gmail.com> <14989d6e0907290025i499c71fbn289b64a7da0e4b97@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
Yep, the cp /dev/null <file> works to truncate. So I can deal with it. Yep, everything is snapshotted. Yep, this is a Sun issue not a FreeBSD one. FreeBSD should just stay current with the versions and the minimum needed to port... fbsd dev time is valuable elsewhere. I do remember reading about copy on write, d-oh :) ZFS should probably keep track of the largest extent needed to effect any given operation and reserve that behind the scenes. If it took n bytes to create something sans data, it'll probably take n bytes to modify it. Quotas and things might work though the user under quota might run into the same problem. Who knows. Thx CW, et al.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d2e731a10907292222t6f4c02ebn3895ba9efc0d4f01>