On Sun, Apr 22, 2018 at 04:55:13PM +0200, Tijl Coosemans wrote:
> On Sun, 22 Apr 2018 16:28:55 +0300 Konstantin Belousov
> wrote:
> > On Sun, Apr 22, 2018 at 03:15:00PM +0200, Tijl Coosemans wrote:
> >> Thanks for the review. There's just one concern I have. With this patch
> >> the bufspace_da
On Sun, 22 Apr 2018 16:28:55 +0300 Konstantin Belousov
wrote:
> On Sun, Apr 22, 2018 at 03:15:00PM +0200, Tijl Coosemans wrote:
>> Thanks for the review. There's just one concern I have. With this patch
>> the bufspace_daemon threads appear to shutdown after the buf_daemon and
>> after the sync
On Sun, Apr 22, 2018 at 03:15:00PM +0200, Tijl Coosemans wrote:
> On Sun, 22 Apr 2018 15:05:21 +0300 Konstantin Belousov
> wrote:
> > On Sat, Apr 21, 2018 at 11:49:34PM +0200, Tijl Coosemans wrote:
> >> On Sat, 21 Apr 2018 21:09:09 + Rick Macklem
> >> wrote:
> >>> With a recent head/curre
On Sun, 22 Apr 2018 15:05:21 +0300 Konstantin Belousov
wrote:
> On Sat, Apr 21, 2018 at 11:49:34PM +0200, Tijl Coosemans wrote:
>> On Sat, 21 Apr 2018 21:09:09 + Rick Macklem
>> wrote:
>>> With a recent head/current kernel (doesn't happen when running a Dec.
>>> 2017 one), when I do a hal
Konstantin Belousov wrote:
>On Sat, Apr 21, 2018 at 11:49:34PM +0200, Tijl Coosemans wrote:
>> On Sat, 21 Apr 2018 21:09:09 + Rick Macklem wrote:
>> > With a recent head/current kernel (doesn't happen when running a Dec.
>> > 2017 one), when I do a halt, it gets as far as:
>> >
>> > vnodes rem
On Sat, Apr 21, 2018 at 11:49:34PM +0200, Tijl Coosemans wrote:
> On Sat, 21 Apr 2018 21:09:09 + Rick Macklem wrote:
> > With a recent head/current kernel (doesn't happen when running a Dec.
> > 2017 one), when I do a halt, it gets as far as:
> >
> > vnodes remaining... 0 time out
> >
> > an
In message <201804212227.w3lmrp5w002...@slippy.cwsent.com>, Cy Schubert
writes:
> In message <20180421234934.10d7d...@kalimero.tijl.coosemans.org>, Tijl
> Cooseman
> s writes:
> > --MP_/TDsO+CDIra7UXGs=vVO3NTB
> > Content-Type: text/plain; charset=US-ASCII
> > Content-Transfer-Encoding: 7bit
> >
In message , Rick Macklem writes:
> Cy Schubert wrote:
> >In message <201804212227.w3lmrp5w002...@slippy.cwsent.com>, Cy Schubert
> writes:
> >> In message <20180421234934.10d7d...@kalimero.tijl.coosemans.org>, Tijl
> >> Cooseman
> >> s writes:
> >> > --MP_/TDsO+CDIra7UXGs=vVO3NTB
> >> > Content-Ty
Cy Schubert wrote:
>In message <201804212227.w3lmrp5w002...@slippy.cwsent.com>, Cy Schubert
writes:
>> In message <20180421234934.10d7d...@kalimero.tijl.coosemans.org>, Tijl
>> Cooseman
>> s writes:
>> > --MP_/TDsO+CDIra7UXGs=vVO3NTB
>> > Content-Type: text/plain; charset=US-ASCII
>> > Content-Tran
In message <20180421234934.10d7d...@kalimero.tijl.coosemans.org>, Tijl
Cooseman
s writes:
> --MP_/TDsO+CDIra7UXGs=vVO3NTB
> Content-Type: text/plain; charset=US-ASCII
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
>
> On Sat, 21 Apr 2018 21:09:09 + Rick Macklem wrote:
> > Wit
On 04/21/2018 23:09, Rick Macklem wrote:
With a recent head/current kernel (doesn't happen when running a Dec. 2017 one),
when I do a halt, it gets as far as:
vnodes remaining... 0 time out
and that's it (the time out appears several seconds after the first "0").
With a Dec. 2017 kernel there w
On Sat, 21 Apr 2018 21:09:09 + Rick Macklem wrote:
> With a recent head/current kernel (doesn't happen when running a Dec.
> 2017 one), when I do a halt, it gets as far as:
>
> vnodes remaining... 0 time out
>
> and that's it (the time out appears several seconds after the first "0").
> With
With a recent head/current kernel (doesn't happen when running a Dec. 2017 one),
when I do a halt, it gets as far as:
vnodes remaining... 0 time out
and that's it (the time out appears several seconds after the first "0").
With a Dec. 2017 kernel there would be several "0"s printed.
It appears th
13 matches
Mail list logo
