Control: found -1 1.3.4-2.5
Control: severity -1 grave
Hi all,
this bug causes kernel panics at least on i386 and x86-64 running
nfsv4 servers so set severity to grave.
* Hieu Luu <h...@vivu.asia> [2017-09-26 21:24 +0700]:
> Hello Stephen,
>
> I was able to resolve this by following these steps (after doing strace
> nfsdcltrack init to find out why it returned -13) **[1]**
>
> 1. `# mkdir /var/lib/nfs/nfsdcltrack`
> 2. `# nfsdcltrack init`
> 3. check if file `/var/lib/nfs/nfsdcltrack/main.sqlite` is present
> 4. check with `sqlite /var/lib/nfs/nfsdcltrack/main.sqlite`
> * querying `.tables` gives `clients` and `parameters`
> * querying `.schema clients` gives `CREATE TABLE clients (id BLOB PRIMARY
> KEY, time INTEGER, has_session INTEGER);`
> * querying `.schema parameters` gives `CREATE TABLE parameters (key TEXT
> PRIMARY KEY, value TEXT);`
> 5. `# systemctl restart nfs-server`
I can confirm that the above workaround doesn't cause kernel panics
anymore.
Thanks
Elimar
--
We all know Linux is great... it does infinite loops in 5 seconds.
-Linus Torvalds
