Date: Mon, 27 Aug 2018 17:42:10 -0500 From: Rajil Saraswat <rajil.s@gmail.com> Cc: FreeBSD virtualization <freebsd-virtualization@freebsd.org> Subject: Re: Bhyve guest boot error, Buffer I/O error on dev vda1, logical block 0, lost async page write Message-ID: <69322b42-dc78-e2b0-d92d-e70cc37924d9@gmail.com> In-Reply-To: <c2842451-5077-0078-025a-b7cfaeb57cdf@nomadlogic.org> References: <ab6aab30-bbdc-9c81-1a71-1be29ce0f697@gmail.com> <114c2000-17ba-3cf6-1d4a-1354f42d8875@gmail.com> <CAEW%2BogbRC6hBe49GXr7vuC=pLcvdrtjhT25eh9U7%2BrbzE6tOPg@mail.gmail.com> <c2842451-5077-0078-025a-b7cfaeb57cdf@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 - | | |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?69322b42-dc78-e2b0-d92d-e70cc37924d9>