Oooops, some snapshots were using all the missing space.
While I played around with some commands I've read in the ZFS Administration
Guide and the ZFS FAQ, I stumbled over 6 or 7 snapshots of my opensolaris-7 be.
I wonder where they come from, because I've never worked with snapshots so far
zpool tells me the following details for my rpool:
SIZE=16G
ALLOC=14.5G
FREE=1.36G
CAP=91%
and zfs tells me these stats:
rpool
USED=15.1G
AVAIL=505M
REFER=83K
MOUNTPOINT=/rpool
rpool/ROOT
USED=14.3G
AVAIL=505M
REFER=21K
MOUNTPOINT=legacy
rpool/ROOT/opensolaris-7
USED=14.3G
AVAIL=505M
On 02/ 6/10 11:21 AM, Thorsten Hirsch wrote:
I wonder where ~10G have gone. All the subdirs in / use ~4.5G only
(that might be the size of REFER in opensolaris-7), and my $HOME uses
38.5M, that's correct. But since rpool has a size of 15G there must
be more than 10G somewhere.
Do you have
Uhmm... well, no, but there might be something left over.
When I was doing an image-update last time, my / ran out of space. I even
couldn't beadm destroy any old boot environment, because beadm told me that
there's no space left. So what I did was zfs destroy
/rpool/ROOT/opensolaris-6. After
On 02/06/10 08:38, Frank Middleton wrote:
AFAIK there is no way to get around this. You can set a flag so that pkg
tries to empty /var/pkg/downloads, but even though it looks empty, it
won't actually become empty until you delete the snapshots, and IIRC
you still have to manually delete the
On 02/ 6/10 11:50 AM, Thorsten Hirsch wrote:
Uhmm... well, no, but there might be something left over.
When I was doing an image-update last time, my / ran out of space. I
even couldn't beadm destroy any old boot environment, because beadm
told me that there's no space left. So what I did was
how can I delete obsolete BEs if I have run out of space and have to boot
from LiveCD?
On Sat, Feb 6, 2010 at 9:33 AM, Bill Sommerfeld sommerf...@sun.com wrote:
On 02/06/10 08:38, Frank Middleton wrote:
AFAIK there is no way to get around this. You can set a flag so that pkg
tries to empty
