Installing 101945-29 to clients seems to be the solution: simple, but
inconvenient. It relates to over-quota situations. There were no clues to
given to decode the error message.
Thanks to:
Adrian Lee <adrian@cs.uq.oz.au>
Casper Dik <casper@Holland.Sun.COM>
Original question:
We have a few diskless clients served by host metten. From time to time we
get from the client's syslog (not always the same client):
Aug 21 17:09:31 lauden unix: NFS write error on host metten: error 49.
Aug 21 17:09:31 lauden unix: (file handle:
Aug 21 17:09:31 lauden unix: 80000f
Aug 21 17:09:31 lauden unix: 2
Aug 21 17:09:31 lauden unix: a0000
Aug 21 17:09:31 lauden unix: 168619
Aug 21 17:09:31 lauden unix: 2a41e3ab
Aug 21 17:09:31 lauden unix: a0000
Aug 21 17:09:31 lauden unix: 2
Aug 21 17:09:31 lauden unix: 7710e3f5
Aug 21 17:09:31 lauden unix: )
and on and on.
What could be causing this and you can we fix it? (we now have to reboot
each time this happens). Can you tell from the message what partition is
causing the trouble?
We run 5.4 on Sparc systems. All recommended patches installed (kernel
patch 101945-27).
Thanks in advance,
Peter
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:32 CDT