Rajil Saraswat wrote this message on Mon, Aug 27, 2018 at 17:42 -0500:
> On 08/27/2018 11:50 AM, Pete Wright wrote:
> >
> >
> > On 8/26/18 10:07 PM, Sami Halabi wrote:
> >> Hi,
> >> IIRC pool shouldn't be above 90% used otherwise bad things happen..
> >> but at
> >> 69%????
> >> Can someone explain thid please?
> >
> > it's possible the filesystem was heavily fragmented? seems suspicious
> > - did scrubbing your pool find any errors?
> >
> > -pete
> >
>
> This is how the pool looked like,
>
> |# zpool list vmpool NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP
> HEALTH ALTROOT vmpool 372G 257G 115G - - 64% 69% 1.00x ONLINE - |
>
> Scrub did not show the errors. After deleting unused zvols, the guests
> started to work and pool looks like this,
> |
> |
>
> |# zpool list vmpool
> NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP
> HEALTH ALTROOT
> vmpool 372G 197G 175G - - 56% 53% 1.00x
> ONLINE -
There are a couple things that can happen.. you could have a quota
or refquota that prevents a dataset/zdev, or it's descendants from growing
larger, or you could have refreservation or reservation set which limits
the space that other datasets can consume..
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
_______________________________________________
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to
"freebsd-virtualization-unsubscr...@freebsd.org"
