Re: crash: umount_nfs: Current

2017-03-24 Thread Rick Macklem
riday, March 24, 2017 11:21:39 AM To: Rick Macklem; freebsd...@freebsd.org Cc: freebsd-current@FreeBSD.org Subject: Re: crash: umount_nfs: Current I tried my test (umount –t nfs –a && mount –t nfs –a) and no crash. (with ~84G inact cached NFS data). I suspect it helped. -- L

Re: crash: umount_nfs: Current

2017-03-24 Thread Larry Rosenman
I tried my test (umount –t nfs –a && mount –t nfs –a) and no crash. (with ~84G inact cached NFS data). I suspect it helped. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, T

Re: crash: umount_nfs: Current

2017-03-23 Thread Larry Rosenman
Patch applied and running – I’ll try the repro here in a day or 2. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 On 3/23/17, 1:20 PM, "Larry Rosenman" wrot

Re: crash: umount_nfs: Current

2017-03-23 Thread Larry Rosenman
Ok, I think I have a repro scenario. I just repro’d it without this patch. I’ll apply it and try again. It takes about 2 days to get enough INACT data that the umount_nfs crashes. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail:

Re: crash: umount_nfs: Current

2017-03-22 Thread Larry Rosenman
It’s VERY intermittent ( I.E. not easy to reproduce. Sorry. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 On 3/22/17, 9:20 PM, "Rick Macklem" wrote:

Re: crash: umount_nfs: Current

2017-03-22 Thread Rick Macklem
Larry Rosenman wrote: > Err, I’m at r315289…. I think the attached patch (only very lightly tested by me) will fix this crash. If you have an easy way to test it, that would be appreciated, rick clntcrash.patch Description: clntcrash.patch ___ freebs

Re: crash: umount_nfs: Current

2017-03-17 Thread Rick Macklem
bsd-current@FreeBSD.org Subject: Re: crash: umount_nfs: Current Err, I’m at r315289…. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 On 3/16/17, 5:51 PM, "

Re: crash: umount_nfs: Current

2017-03-16 Thread Larry Rosenman
To: freebsd...@freebsd.org Cc: freebsd-current@FreeBSD.org Subject: crash: umount_nfs: Current Recent current, playing with new FreeNAS Corral, client is FreeBSD -CURRENT. Lovely crash: borg.lerctr.org dumped core - see /var/crash/vmcore.1 Wed Mar 15 21

Re: crash: umount_nfs: Current

2017-03-16 Thread Rick Macklem
eebsd...@freebsd.org Cc: freebsd-current@FreeBSD.org Subject: crash: umount_nfs: Current Recent current, playing with new FreeNAS Corral, client is FreeBSD -CURRENT. Lovely crash: borg.lerctr.org dumped core - see /var/crash/vmcore.1 Wed Mar 15 21:38:53 CDT 2017 FreeBSD borg.lerctr.org 12.0-CU

crash: umount_nfs: Current

2017-03-15 Thread Larry Rosenman
Recent current, playing with new FreeNAS Corral, client is FreeBSD -CURRENT. Lovely crash: borg.lerctr.org dumped core - see /var/crash/vmcore.1 Wed Mar 15 21:38:53 CDT 2017 FreeBSD borg.lerctr.org 12.0-CURRENT FreeBSD 12.0-CURRENT #11 r315289: Tue Mar 14 20:55:36 CDT 2017 r...@borg.lerctr