Date: Wed, 22 Mar 2006 14:27:44 -0500 From: Mikhail Teterin <mi+mx@aldan.algebra.com> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Kostik Belousov <kostikbel@gmail.com>, alc@freebsd.org, stable@freebsd.org Subject: flushing "anonymous" buffers over NFS is rejected by server (more weird bugs with mmap-ing via NFS) Message-ID: <200603221427.45219.mi%2Bmx@aldan.algebra.com> In-Reply-To: <200603221903.k2MJ37Iq013571@apollo.backplane.com> References: <200603211607.30372.mi%2Bmx@aldan.algebra.com> <200603221312.38502.mi%2Bmx@aldan.algebra.com> <200603221903.k2MJ37Iq013571@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
середа 22 березень 2006 14:03, Matthew Dillon Ви написали: > I consider it a bug. I think the only way to reliably fix the problem > is to give the client the ability to specify the uid to issue RPCs with > in the NFS mount command, to match what the export does. So, the problem is, the dirtied buffers _sometimes_ lose their owner and thus become root-owned. When the NFS client tries to flush them out, the NFS server (by default suspecting remote roots of being evil) rejects the flushing, which brings the client to its weak knees. 1. Do the yet unflushed buffers really have to be anonymous? 2. Can't the client's knees be strengthened in this regard? Thanks! -mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200603221427.45219.mi%2Bmx>