Re: [zfs-discuss] When Zpool has no space left and no snapshots

2010-09-29 Thread David Dyer-Bennet

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.)

 If there are no snapshots to destroy, how to prepare for a situation
 when a ZFS pool looses it's last free byte?

Add some more space somewhere around 90%, or earlier :-).

If you do get stuck,  you can add another vdev when full, too. Just
remember that you're stuck with whatever you add forever, since there's
no way to remove a vdev from a pool.
-- 
David Dyer-Bennet, d...@dd-b.net; http://dd-b.net/
Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/
Photos: http://dd-b.net/photography/gallery/
Dragaera: http://dragaera.info

___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


Re: [zfs-discuss] When Zpool has no space left and no snapshots

2010-09-29 Thread Matt Cowger
You can truncate a file:

Echo   bigfile

That will free up space without the 'rm'

-Original Message-
From: zfs-discuss-boun...@opensolaris.org 
[mailto:zfs-discuss-boun...@opensolaris.org] On Behalf Of David Dyer-Bennet
Sent: Wednesday, September 29, 2010 12:59 PM
To: zfs-discuss@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 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 prepare for a situation
 when a ZFS pool looses it's last free byte?

Add some more space somewhere around 90%, or earlier :-).

If you do get stuck,  you can add another vdev when full, too. Just
remember that you're stuck with whatever you add forever, since there's
no way to remove a vdev from a pool.
-- 
David Dyer-Bennet, d...@dd-b.net; http://dd-b.net/
Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/
Photos: http://dd-b.net/photography/gallery/
Dragaera: http://dragaera.info

___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


Re: [zfs-discuss] When Zpool has no space left and no snapshots

2010-09-29 Thread David Dyer-Bennet

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 old version doesn't get released.

-- 
David Dyer-Bennet, d...@dd-b.net; http://dd-b.net/
Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/
Photos: http://dd-b.net/photography/gallery/
Dragaera: http://dragaera.info

___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


[zfs-discuss] When Zpool has no space left and no snapshots

2010-09-28 Thread Aleksandr Levchuk
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 prepare for a situation
when a ZFS pool looses it's last free byte?

Alex
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


Re: [zfs-discuss] When Zpool has no space left and no snapshots

2010-09-28 Thread Scott Meilicke
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 well - all I had to do is
 destroy some snapshots.)
 
 If there are no snapshots to destroy, how to prepare for a situation
 when a ZFS pool looses it's last free byte?
 
 Alex
 ___
 zfs-discuss mailing list
 zfs-discuss@opensolaris.org
 http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


--
Scott Meilicke | Enterprise Systems Administrator | Crane Aerospace 
Electronics | +1 425-743-8153 | M: +1 206-406-2670



We value your opinion!  How may we serve you better? 
Please click the survey link to tell us how we are doing:
http://www.craneae.com/ContactUs/VoiceofCustomer.aspx
Your feedback is of the utmost importance to us. Thank you for your time.

Crane Aerospace  Electronics Confidentiality Statement:
The information contained in this email message may be privileged and is 
confidential information intended only for the use of the recipient, or any 
employee or agent responsible to deliver it to the intended recipient. Any 
unauthorized use, distribution or copying of this information is strictly 
prohibited 
and may be unlawful. If you have received this communication in error, please 
notify 
the sender immediately and destroy the original message and all attachments 
from 
your electronic files.

___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss