E4500 with 24GB RAM
hrs at FreeBSD.org
Sat Jun 11 08:48:31 GMT 2005
Pyun YongHyeon <yongari at rndsoft.co.kr> wrote
in <20050611075451.GC19976 at rndsoft.co.kr>:
yo> On Sat, Jun 11, 2005 at 03:36:41AM -0400, Kris Kennaway wrote:
yo> > AFAICR I've never seen a problem with this (except with an i386 4.x
yo> > server, which can be panicked by a sparc64 client)..I don't rely on
yo> > NFS heavily in most cases, but I do use it on a number of machines
yo> > (including two package build machines that netboot and access their
yo> > ports trees over NFS, and have been in continuous operation with an
yo> > uptime of 110 days).
yo> Do you use NFS orver UDP? NFS over TCP has much better change of
yo> getting panic.
yo> If you copy a large file(> 100MB) from a NFS exported directory to
yo> its sub-directory you probably hit a panic. If my memory serve right
yo> there had been several NFS panic reports in current/sparc64 ML.
yo> And I don't think it was fixed since the root cause of panic is in
yo> nfsm_disct() and nfs_realign()(it was not touched for a long time.)
Well, I am using r/w NFS over TCP (IPv4) for /home. The server is
FreeBSD/i386 RELENG_4 and the client is FreeBSD/sparc64 RELENG_5.
I tried to copy an ISO image:
hrs at sparc64 % mount -v | grep /home
home-v4:/home on /home (nfs)
hrs at sparc64 % cd /home/hrs
hrs at sparc64 % ls -al 5.4-RELEASE-sparc64-disc2.iso
-rw-rw-r-- 1 hrs hrs 666693632 May 9 09:06 5.4-RELEASE-sparc64-disc2.iso
hrs at sparc64 % mkdir subdir
hrs at sparc64 % cp 5.4-RELEASE-sparc64-disc2.iso subdir
hrs at sparc64 % ls -al subdir/
-rw-rw-r-- 1 hrs hrs 666693632 Jun 11 17:20 5.4-RELEASE-sparc64-disc2.iso
hrs at sparc64 %
Just a report ;)
| Hiroki SATO
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-sparc64/attachments/20050611/7ff04ff7/attachment.bin
More information about the freebsd-sparc64