Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 20 Apr 2005 17:35:28 +0200
From:      Marc Olzheim <marcolz@stack.nl>
To:        Brian Fundakowski Feldman <green@freebsd.org>
Cc:        freebsd-current@freebsd.org
Subject:   Re: NFS client/buffer cache deadlock
Message-ID:  <20050420153528.GC77731@stack.nl>
In-Reply-To: <20050420152038.GI1157@green.homeunix.org>
References:  <20050419133227.GA11612@stack.nl> <20050419151800.GE1157@green.homeunix.org> <20050419160258.GA12287@stack.nl> <20050419160900.GB12287@stack.nl> <20050419161616.GF1157@green.homeunix.org> <20050419204723.GG1157@green.homeunix.org> <20050420140409.GA77731@stack.nl> <20050420142448.GH1157@green.homeunix.org> <20050420143842.GB77731@stack.nl> <20050420152038.GI1157@green.homeunix.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--iFRdW5/EC4oqxDHL
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Apr 20, 2005 at 11:20:38AM -0400, Brian Fundakowski Feldman wrote:
> Reads should be totally unaffected...

The server was misbehaving. Fixed. :-)

> > Btw.: I'm not sure write(),writev() and pwrite() are allowed to do short
> > writes on regular files... ?
>=20
> Our manpage is incorrect; POSIX states that they are (see earlier
> e-mail).  There really is no alternative -- we simply can't build
> an NFS transaction larger than our buffer cache can accomodate.
> Note that short wries won't happen for normal buffer sizes, only
> excessively large ones.  I really don't believe that writev() is meant
> to be used so that you can write gigantic data structures in a single
> transaction...

Ah, I was reading the SUSv2 page:

http://www.opengroup.org/onlinepubs/009695399/functions/write.html

instead of the POSIX version.

But in neither of those I can extrude the fact that it can return
with result < nbyte, without it being a permanent condition.
What phrase makes you conclude that it can ?

Marc

--iFRdW5/EC4oqxDHL
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)

iD8DBQFCZnbAezjnobFOgrERAqYEAJ9a25uCceVtDReKpiAUkMsNi0h5fACeJvTc
dpl7Dp6Sa4k3Bth3VKt/hR0=
=qmxF
-----END PGP SIGNATURE-----

--iFRdW5/EC4oqxDHL--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050420153528.GC77731>