Date: Thu, 21 Mar 2013 19:59:25 +0100 From: Michael Landin Hostbaek <mich@FreeBSD.org> To: Konstantin Belousov <kostikbel@gmail.com> Cc: Jeremy Chadwick <jdc@koitsu.org>, Rick Macklem <rmacklem@uoguelph.ca>, freebsd-stable@FreeBSD.org, Andriy Gapon <avg@FreeBSD.org>, John Baldwin <jhb@FreeBSD.org> Subject: Re: Core Dump / panic sleeping thread Message-ID: <2D7E0213-C1BC-4CA8-BABD-256C17DD692D@FreeBSD.org> In-Reply-To: <20130321075847.GR3794@kib.kiev.ua> References: <20130320173100.GF3794@kib.kiev.ua> <223607151.4129243.1363828477555.JavaMail.root@erie.cs.uoguelph.ca> <20130321075847.GR3794@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 21, 2013, at 8:58 AM, Konstantin Belousov <kostikbel@gmail.com> = wrote: > On Wed, Mar 20, 2013 at 09:14:37PM -0400, Rick Macklem wrote: >> Well, read/write sharing of files over NFS is pretty rare, so I = suspect >> a truncation of a file by another client (or locally in the NFS = server) >> is a rare event. As such, not invalidating the buffers here doesn't = seem >> like a big issue? (The client uses np->n_size to determine EOF.) >>=20 >> Also, I think close-to-open consistency will typically throw away the >> buffers on the next open when it sees the mtime changed. (Yes, there >> won't necessarily be another open, but...) > nfs buffers are VMIO. Each VMIO buffer wires the pages it references. > Wired pages cannot be freed by vnode_pager_setsize() if the file is > truncated. Should I wait for a new patch, or should I give the one you sent = yesterday a try?=20 Thanks,=20 /mich
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2D7E0213-C1BC-4CA8-BABD-256C17DD692D>