Date: Wed, 04 Dec 2002 10:21:45 +0000 From: Pete French <pfrench@firstcallgroup.co.uk> To: cswiger@mac.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: NFS interoperability problem Message-ID: <E18JWf3-000NRe-00@mailhost.firstcallgroup.co.uk> In-Reply-To: <1A811F67-06F8-11D7-A933-000A27D85A7E@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> OPENSTEP 4.2 probably has a bug lurking from the NFS v2 sources, according > to an /etc/system tunable parameter under Solaris: Mmmm... very interesting, and well worth knowing! In this case the OS42 machine is the client, so its unlikely to be this, but it something Ihad never heard of before. > Try setting vers=2, or even add rsize=1024,wsize=1024 if that doesn't help. Neither of these help sadly. Whats even more exasperating is that I have discovered that the effect is only confined to one particular mounted drive from the FreeBSD machine ?! I have three drives mounted, all rougly the same size, all mounted with the same options and all shared with the same options from the FFreeBSD machine. The only difference is that the drive causing problems is a RAID-1 volume, whilst the others are all RAID-5. That should be completely invisible to the client though. On the FreeBSD machine: bash-2.05b$ cat /etc/exports /home -maproot=0 frenic drift maekong /mnt/shared -maproot=0 frenic drift maekong /mnt/music -maproot=0 frenic drift maekong bash-2.05b$ df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s2a 516062 42864 431914 9% / /dev/da0s2f 1032142 64 949508 0% /tmp /dev/da0s2g 11868928 2627394 8292020 24% /usr /dev/da0s2e 1032142 13072 936500 1% /var procfs 4 4 0 100% /proc /dev/idad0s1 8118 10 8108 0% /mnt/win-r1 /dev/idad0s2e 35342924 6854822 25660670 21% /home /dev/idad1s1 1017984 127940 890044 13% /mnt/win-r5 /dev/idad1s2e 39700529 24711471 11813016 68% /home/pete/r5 /dev/idad1s2f 39700529 11856108 24668379 32% /mnt/shared /dev/idad1s2g 39700529 15862674 20661813 43% /mnt/music So now I am really flummoxed. Its not to do with the size of the directory containing the file either, as I can move the file to other places - anywhere on that drive wont edit, though it will on the other drives. > It's also conceivable that installing the last set of Y2K patches for > OPENSTEP 4.2 (available from Apple) might include a kernel which fixed > this bug. I've got all the patches and sadly they dont help either. Thanks for the advice though. I shall keep looking to try and narrow down the probem further -pcf. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E18JWf3-000NRe-00>