Re: NFS 4.1 RECLAIM_COMPLETE FS failed error

is useless. (This hack just > assumes > the client meant to say "one_fs == false".) > There was also a case (I think it was after a server reboot) where the > client would > do one of these after doing a ReclaimComplete with "one_fs == false" and > that is >

Re: NFS 4.1 RECLAIM_COMPLETE FS failed error

Daniel Engel wrote: [stuff snipped] >I traced the commits that Rick has made since that thread and merged them >'head' >into 'stable': > >'svnlite checkout http://svn.freebsd.org/base/release/11.1.0/' >'svnlite merge -c 332790 http://svn.freebsd.org/base/head' >'svnlite merge -c

Re: NFS 4.1 RECLAIM_COMPLETE FS failed error

Daniel Engel wrote: >I am setting up an environment with FreeBSD 11.1 sharing a ZFS datastore to >vmware >ESXI 6.7. There were a number of errors with NFS 4.1 sharing that I >didn't >understand until I found the following thread. > >

Security patch SA-18:03 removed from 11.2 - why?

Release/update 11.1-p8 introduced so-called "mitigation for speculative execution vulnerabilities". In RElease 11.2 these "mitigation" have been removed. What is the reason for the removal, and specifically why is Security advisory 18:03 still mentioned in the release notes? Behaviour with

RE: NFS 4.1 RECLAIM_COMPLETE FS failed error

Hi, I am setting up an environment with FreeBSD 11.1 sharing a ZFS datastore to vmware ESXI 6.7. There were a number of errors with NFS 4.1 sharing that I didn't understand until I found the following thread.

Problem reports for sta...@freebsd.org that need special attention

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and

Re: Unable to boot memstick on APU2

Hi Stefan, On 07/08/2018 06:50 PM, Christoph Moench-Tegeder wrote: ## Stefan Bethke (s...@lassitu.de): I'm stumped by a weird error: loader loads the kernel, and the kernel probes the USB stick successfully, but da0 never shows up. I’ve tried with FreeBSD-11.1-RELEASE-amd64-memstick.img and

Re: Unable to boot memstick on APU2

## Stefan Bethke (s...@lassitu.de): > I'm stumped by a weird error: loader loads the kernel, and the kernel > probes the USB stick successfully, but da0 never shows up. I’ve tried > with FreeBSD-11.1-RELEASE-amd64-memstick.img and > FreeBSD-11.2-RELEASE-amd64-memstick.img. I've had this happen

Unable to boot memstick on APU2

I'm stumped by a weird error: loader loads the kernel, and the kernel probes the USB stick successfully, but da0 never shows up. I’ve tried with FreeBSD-11.1-RELEASE-amd64-memstick.img and FreeBSD-11.2-RELEASE-amd64-memstick.img. While at the mount root prompt, unplugging and replugging the

Re: lightly loaded system eats swap space

On 25/06/2018 18:28, tech-lists wrote: On 20/06/2018 06:08, Shane Ambler wrote: This review is aiming to fix this - https://reviews.freebsd.org/D7538 I have been running the patch on stable/11 and after eight days uptime I still have zero swap in use, I can't recall a time in the last few