On Wed, September 22, 2010 21:25, Aleksandr Levchuk wrote:
I ran out of space, consequently could not rm or truncate files. (It
make sense because it's a copy-on-write and any transaction needs to
be written to disk. It worked out really well - all I had to do is
destroy some snapshots.)
@opensolaris.org
Subject: Re: [zfs-discuss] When Zpool has no space left and no snapshots
On Wed, September 22, 2010 21:25, Aleksandr Levchuk wrote:
I ran out of space, consequently could not rm or truncate files. (It
make sense because it's a copy-on-write and any transaction needs to
be written
On Wed, September 29, 2010 15:17, Matt Cowger wrote:
You can truncate a file:
Echo bigfile
That will free up space without the 'rm'
Copy-on-write; the new version gets written to the disk before the old
version is released, it doesn't just overwrite. AND, if it's in any
snapshots, the
Dear ZFS Discussion,
I ran out of space, consequently could not rm or truncate files. (It
make sense because it's a copy-on-write and any transaction needs to
be written to disk. It worked out really well - all I had to do is
destroy some snapshots.)
If there are no snapshots to destroy, how to
Preemptively use quotas?
On 9/22/10 7:25 PM, Aleksandr Levchuk alevc...@gmail.com wrote:
Dear ZFS Discussion,
I ran out of space, consequently could not rm or truncate files. (It
make sense because it's a copy-on-write and any transaction needs to
be written to disk. It worked out really
