X on sparc64?

[Kris Kennaway]

On Sat, Oct 11, 2003 at 07:48:37PM -0600, Tillman Hodgson wrote:
> On Sat, Oct 11, 2003 at 06:42:24PM -0700, Kris Kennaway wrote:
> > On Sat, Oct 11, 2003 at 07:38:36PM -0600, Tillman Hodgson wrote:
> > > On Sat, Oct 11, 2003 at 05:34:02PM -0700, Kris Kennaway wrote:
> > > > Be aware that 4.x's NFS code doesn't like talking to sparc64 clients -
> > > > it causes the i386 server to double fault.  5.x as a server is
> > > > perfectly happy though.
> > > 
> > > I have an Ultra 5 running a recent -current that uses an i386 -stable as
> > > it's NFS server ... I've never seen any problems with it. Is this an
> > > issue that is only affected via certain NFS options or is otherwise
> > > possible to (unknowingly) avoid?
> > 
> > It only occurs under load..if you've never put heavy (I mean heavy!)
> > loads on the server you've probably avoided it.  I was able to repeat
> > this on two separate networks.
> 
> Load on which end? I dump all filesystems on 4 servers to the -stable
> box out of daily.local (thus simultaneously), which should swamp the NFS
> server fairly regularly. 14 out of 16 of my nfsd's show significant CPU
> usage, considering that my uptime is 11 days (my last -stable upgrade).
> 
> I'm now somewhat nervous about the setup if you meant load on the NFS
> server rather than the sparc64 client :-)

The clients netboot from the server and do a lot of simultaneous
copying of packages.  This essentially means they keep a 100MB
ethernet operating at a good percentage of capacity.  The i386 server
would usually panic in less than 24 hours of this sustained load.
This did not happen with other architectures as clients of the same
machine, with the same usage patterns.

Search the archives from a year or so ago for more specific
information.

Kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-sparc64/attachments/20031011/059d21b2/attachment.bin