From owner-freebsd-virtualization@freebsd.org  Tue Apr 12 07:10:49 2016
Return-Path: <owner-freebsd-virtualization@freebsd.org>
Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8F262B0CC68
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Tue, 12 Apr 2016 07:10:49 +0000 (UTC)
 (envelope-from phk@phk.freebsd.dk)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
 by mx1.freebsd.org (Postfix) with ESMTP id 58E6C1E5C;
 Tue, 12 Apr 2016 07:10:49 +0000 (UTC)
 (envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (unknown [192.168.55.3])
 by phk.freebsd.dk (Postfix) with ESMTP id 14FC54FB03;
 Tue, 12 Apr 2016 07:10:46 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
 by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id u3C7AjGb020380;
 Tue, 12 Apr 2016 07:10:46 GMT (envelope-from phk@phk.freebsd.dk)
To: Peter Grehan <grehan@freebsd.org>
cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org>
Subject: Re: -current host, 10.1 client loops
In-reply-to: <570C74CF.1080702@freebsd.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
References: <20918.1458052609@critter.freebsd.dk>
 <CAFgRE9HQyq9tsM8PNzCAzQ2AwKenstaELcn0VsYHG4wzK4fXsA@mail.gmail.com>
 <23329.1458077441@critter.freebsd.dk>
 <CAFgRE9HFVZFdA9f6itRQQAnKWvXPJi8ukFyhPxxsnNYk=d1pmg@mail.gmail.com>
 <28223.1458163559@critter.freebsd.dk>
 <CA+q+Tcpr8Dpo8E2WiQhFmD_nV_O8BA0PQ1O3a7+5kja+EYs4NA@mail.gmail.com>
 <723.1460154499@critter.freebsd.dk> <570B3604.8020500@freebsd.org>
 <16580.1460397200@critter.freebsd.dk> <570C74CF.1080702@freebsd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <20378.1460445045.1@critter.freebsd.dk>
Date: Tue, 12 Apr 2016 07:10:45 +0000
Message-ID: <20379.1460445045@critter.freebsd.dk>
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Apr 2016 07:10:49 -0000

--------
In message <570C74CF.1080702@freebsd.org>, Peter Grehan writes:


>  I'll try with a bit more CPU oversubscription and see if I can hit 
>this. Thanks for the info - this should help track it down.


For what its worth, I think the port being compiled was:

	/usr/ports/www/p5-Mozilla-CAnss

Another possibly relevant datapoint:

The actively being written to filesystem is UFS+SU+TRIM but no
journal and I think fsck sees more and worse corruption than it
should if writes happened in the order Kirk intended.  Specifically
it should never get fsck_ffs into the "please run fsck again" jungle.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.