Date: Thu, 23 Mar 2017 13:20:57 -0500 From: Larry Rosenman <ler@lerctr.org> To: Rick Macklem <rmacklem@uoguelph.ca>, "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Cc: "freebsd-current@FreeBSD.org" <freebsd-current@FreeBSD.org> Subject: Re: crash: umount_nfs: Current Message-ID: <A29F641C-5F87-4C28-8D3A-2253253D2094@lerctr.org> In-Reply-To: <YTXPR01MB01890E5CFDB2C827F50B0991DD3F0@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM> References: <20170316024433.qiujcewz5bclbgq5@borg.lerctr.org> <YTXPR01MB0189ABA592F02FBB9FFC2C9DDD260@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM> <A5DCCD5C-F6DE-4C54-A9A6-2A3729808E67@lerctr.org> <YTXPR01MB01890E5CFDB2C827F50B0991DD3F0@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM>
index | next in thread | previous in thread | raw e-mail
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: ler@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 On 3/22/17, 9:20 PM, "Rick Macklem" <rmacklem@uoguelph.ca> wrote: 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, rickhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A29F641C-5F87-4C28-8D3A-2253253D2094>