From owner-freebsd-virtualization@freebsd.org Tue Aug 28 04:56:17 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 78CA310A1FF2 for ; Tue, 28 Aug 2018 04:56:17 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gate2.funkthat.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DCC7372663 for ; Tue, 28 Aug 2018 04:56:16 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id w7S4u8Ah063076 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 27 Aug 2018 21:56:09 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id w7S4u8MV063075; Mon, 27 Aug 2018 21:56:08 -0700 (PDT) (envelope-from jmg) Date: Mon, 27 Aug 2018 21:56:08 -0700 From: John-Mark Gurney To: Rajil Saraswat Cc: FreeBSD virtualization Subject: Re: Bhyve guest boot error, Buffer I/O error on dev vda1, logical block 0, lost async page write Message-ID: <20180828045608.GQ45503@funkthat.com> References: <114c2000-17ba-3cf6-1d4a-1354f42d8875@gmail.com> <69322b42-dc78-e2b0-d92d-e70cc37924d9@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <69322b42-dc78-e2b0-d92d-e70cc37924d9@gmail.com> X-Operating-System: FreeBSD 11.0-RELEASE-p7 amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Mon, 27 Aug 2018 21:56:09 -0700 (PDT) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Aug 2018 04:56:17 -0000 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."