Date: Wed, 29 Jul 2009 09:45:27 +0200 From: Christian Walther <cptsalek@gmail.com> To: FreeBSD <freebsd-stable@freebsd.org> Subject: Re: Cannot rm files when ZFS is full Message-ID: <14989d6e0907290045j94bab06wb5d0114fe2af2331@mail.gmail.com> In-Reply-To: <d2e731a10907282029rd17ca1ag892c3c9615e76140@mail.gmail.com> References: <d2e731a10907282029rd17ca1ag892c3c9615e76140@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/7/29 grarpamp <grarpamp@gmail.com>: > One week old build... > > # df -i . > Filesystem =A0 1K-blocks =A0 =A0 =A0Used Avail Capacity iused ifree %iuse= d =A0Mounted on > ram01/mnt1 239465344 239465344 =A0 =A0 0 =A0 100% =A0 13163 =A0 =A0 0 =A0= 100% =A0 /mnt1 > # ls -aliT zero > 20797 -rw-r--r-- =A01 user user =A043515904 Jul 28 23:20:57 2009 zero > # rm -f zero > rm: zero: No space left on device > # :> zero > cannot create zero: File exists > # cp /dev/null zero > overwrite zero? (y/n [n]) y > # ls -aliT zero > 20797 -rw-rw-rw- =A01 root =A0wheel =A00 Jul 28 23:25:17 2009 zero > # rm -f zero > [gone] this is a known problem with the current version of ZFS. Due to the way ZFS handles access to the data it stores, even a rm causes a write, which requires some additional disk space in the beginning: Instead of simply unlinking what should be removed ZFS creates another tree without the removed data. Only if this new tree has been entirely written to disk the old information is removed. This is a rather rough explanation and probably not entirely correct, but I hope it suffices. Only hope: Make sure that not all disk space is used. Christian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14989d6e0907290045j94bab06wb5d0114fe2af2331>