From owner-freebsd-fs@freebsd.org  Mon Aug 27 16:50:28 2018
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@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 4CFE510901B9;
 Mon, 27 Aug 2018 16:50:28 +0000 (UTC)
 (envelope-from pete@nomadlogic.org)
Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org
 [IPv6:2607:f2f8:a098::2])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 9C4E479744;
 Mon, 27 Aug 2018 16:50:27 +0000 (UTC)
 (envelope-from pete@nomadlogic.org)
Received: from [192.168.1.106] (cpe-76-175-75-27.socal.res.rr.com
 [76.175.75.27])
 by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id dced2b94
 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO;
 Mon, 27 Aug 2018 09:50:25 -0700 (PDT)
Subject: Re: Bhyve guest boot error, Buffer I/O error on dev vda1, logical
 block 0, lost async page write
To: Sami Halabi <sodynet1@gmail.com>, Rajil Saraswat <rajil.s@gmail.com>,
 freebsd-fs@freebsd.org
Cc: FreeBSD virtualization <freebsd-virtualization@freebsd.org>
References: <ab6aab30-bbdc-9c81-1a71-1be29ce0f697@gmail.com>
 <114c2000-17ba-3cf6-1d4a-1354f42d8875@gmail.com>
 <CAEW+ogbRC6hBe49GXr7vuC=pLcvdrtjhT25eh9U7+rbzE6tOPg@mail.gmail.com>
From: Pete Wright <pete@nomadlogic.org>
Message-ID: <c2842451-5077-0078-025a-b7cfaeb57cdf@nomadlogic.org>
Date: Mon, 27 Aug 2018 09:50:23 -0700
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101
 Thunderbird/60.0
MIME-Version: 1.0
In-Reply-To: <CAEW+ogbRC6hBe49GXr7vuC=pLcvdrtjhT25eh9U7+rbzE6tOPg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Aug 2018 16:50:28 -0000



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

-- 
Pete Wright
pete@nomadlogic.org
@nomadlogicLA