Date: Thu, 9 Mar 2017 12:42:47 +0000 From: Dexuan Cui <decui@microsoft.com> To: Pete Wright <pete@nomadlogic.org>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: RE: input/output error @boot Message-ID: <MWHPR03MB266983F3C3FF3C6EF99BB70DBF210@MWHPR03MB2669.namprd03.prod.outlook.com> In-Reply-To: <77119d47-3c14-68ce-a0cc-ba7cc8f61598@nomadlogic.org> References: <CACnPvjLv_QhhxYvcbU44x=n0pk61xyFgUGWcTYh%2B6HaGUGJMFg@mail.gmail.com> <CANJ8om5Gri=%2B4Ju9BjdUONwQMW5zrzQhTpz2AzVWUKSVrSgdDA@mail.gmail.com> <CACnPvjJgLK-YtOTJOEE1Uad==pwzO39hSQ1Nk%2BnHND58EbTmvA@mail.gmail.com> <441BF371-53C4-4FE8-A39C-BFA8B25DE760@freebsd.org> <CACnPvjK%2Bb6x3SAD7Gu7uFTkx=iCm2afgt4boVquTT5BC_sF4Tg@mail.gmail.com> <MWHPR03MB2669AB5FFC455EE6BBAAE765BF2F0@MWHPR03MB2669.namprd03.prod.outlook.com> <CACnPvj%2BvrkYGR3b_CoDkORksB6ENZ5HLdzD6=ebJm1329LcfJQ@mail.gmail.com> <CACnPvj%2BQDZZjHzwU7VcsNFN784R4=gYe6qzhQb0NG0AQpov=5g@mail.gmail.com> <MWHPR03MB26699DF5E658361614D71A5EBF2E0@MWHPR03MB2669.namprd03.prod.outlook.com> <CACnPvjKW8di44raA=MxEbqfNPkYaoQ5uOCkgcT3tf1i733i1KA@mail.gmail.com> <CACnPvjJnTyxQu-4-MYB3rPWGZ4TJa%2B=niLkKdtaNTiO%2Bbw=hug@mail.gmail.com> <MWHPR03MB2669510547F2244091F676BCBF210@MWHPR03MB2669.namprd03.prod.outlook.com> <MWHPR03MB26696FB5963990FE4455609CBF210@MWHPR03MB2669.namprd03.prod.outlook.com> <77119d47-3c14-68ce-a0cc-ba7cc8f61598@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd- > current@freebsd.org] On Behalf Of Pete Wright > Sent: Thursday, March 9, 2017 14:04 > To: freebsd-current@freebsd.org > Subject: Re: input/output error @boot > On 3/8/17 10:00 PM, Dexuan Cui wrote: > > For now, I suggest we should only apply the idea "reduce the size of th= e > > staging area if necessary" to VM running on Hyper-V, we should restore = the > > old behavior on physical machines since that has been working for peopl= e > > for a long period of time, though it's potentially unsafe. > > > +1 >=20 > i'd like to see the old behaviour for physical machines to be restored > as well since this has rendered my drm-next test rig broken :( >=20 > -pete Eventually I committed 314956 for the issue: https://svnweb.freebsd.org/base?view=3Drevision&revision=3D314956 The old behaviour for physical machines are restored. PS, I understand usually I should put the patch on phabricator for review, before it's committed, but since the issue here is critical, I committed it directly to unblock people first. Sorry. Please comment on the patch if you think it needs rework -- I hope not. :-= )=20 Thanks, -- Dexuan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?MWHPR03MB266983F3C3FF3C6EF99BB70DBF210>