On Thu, Feb 22, 2018 at 8:34 PM, O. Hartmann wrote:
> Mateusz provided me with this patch, which solved the issue:
>
> Index: sys/kern/vfs_bio.c
> ===
> --- sys/kern/vfs_bio.c (revision 329832)
> +++
18 20:05:24 +0100
> > > "O. Hartmann" <o.hartm...@walstatt.org> schrieb:
> > >
> > > >
> > > > On CURRENT ( 12.0-CURRENT FreeBSD 12.0-CURRENT #196 r329679: Tue
> > > > Feb 20 23:06:15 CET
> > >
> > On CURRENT ( 12.0-CURRENT FreeBSD 12.0-CURRENT #196 r329679: Tue
> > > Feb 20 23:06:15 CET
> > > 2018 amd64) I'm honored by this nice bug when calling top:
> > >
> > > top: sysctl(vfs.bufspace...) expected 8, got 4
> > >
> > >
> >
gt; 2018 amd64) I'm honored by this nice bug when calling top:
> >
> > top: sysctl(vfs.bufspace...) expected 8, got 4
> >
> >
> > Regards,
> >
> > oh
> I still can not use "top", it quits with the error mentioned above.
> Whats is wrong with
23:06:15 CET
> > 2018 amd64) I'm honored by this nice bug when calling top:
> >
> > top: sysctl(vfs.bufspace...) expected 8, got 4
> >
> >
> > Regards,
> >
> > oh
>
> I still can not use "top", it quits with the error mentioned above. Whats
> is
Am Wed, 21 Feb 2018 20:05:24 +0100
"O. Hartmann" <o.hartm...@walstatt.org> schrieb:
> On CURRENT ( 12.0-CURRENT FreeBSD 12.0-CURRENT #196 r329679: Tue Feb 20
> 23:06:15 CET
> 2018 amd64) I'm honored by this nice bug when calling top:
>
> top: sysctl(vfs
On CURRENT ( 12.0-CURRENT FreeBSD 12.0-CURRENT #196 r329679: Tue Feb 20
23:06:15 CET 2018
amd64) I'm honored by this nice bug when calling top:
top: sysctl(vfs.bufspace...) expected 8, got 4
Regards,
oh
--
O. Hartmann
Ich widerspreche der Nutzung oder Übermittlung meiner Daten für