On Jan 8, 2006, at 7:19 PM, Daniel Berlin wrote:
On Sun, 2006-01-08 at 18:05 -0600, Bradley Lucier wrote:
OK, here are some details. Our server is a dual UltraSparc running
Solaris 10 attached to the SAN.
Working client situation: subversion 1.3.0 on Sparc Solaris 9, not
using Berkeley DB
Non-working client situation: subversion 1.3.0 on x86-64 RHEL 4.0,
using Berkeley DB
I think everything is running NFSv4 at this point.
Unless you are running a server locally, whether you've compiled in
BDB
or not doesn't matter.
Thank you all for your suggestions. I think we've isolated the
problem enough to hand it off to someone else, since we have hardware
and OS software support on all the machines involved.
File server: dual ultrasparc running Solaris 10, serves the file
system using either NFSv3 or NFSv4.
Operation:
svn -q checkout svn://gcc.gnu.org/svn/gcc/trunk gcc; cd gcc; contrib/
gcc_update
Results:
File system mounted as NFSv3 or NFSv4 on dual ultrasparc running
Solaris 9: works
File system mounted as NFSv3 on RHEL 4: works
File system mounted as NFSv4 on RHEL 4: reports seeming file system
corruption.
This is reproducible, so perhaps someone can find a fix for it.
Thanks again.
Brad
