Date: Tue, 12 Apr 2016 07:10:45 +0000 From: "Poul-Henning Kamp" <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 Message-ID: <20379.1460445045@critter.freebsd.dk> In-Reply-To: <570C74CF.1080702@freebsd.org> 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%2Bq%2BTcpr8Dpo8E2WiQhFmD_nV_O8BA0PQ1O3a7%2B5kja%2BEYs4NA@mail.gmail.com> <723.1460154499@critter.freebsd.dk> <570B3604.8020500@freebsd.org> <16580.1460397200@critter.freebsd.dk> <570C74CF.1080702@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20379.1460445045>