filesystem's file limitation

[stephen peng]

dear all,
when i copy a file about 3g from an NFS, original mount on an AIX, it hangs when the local file size reaches about 10m and the copy procedure becomes no respons. what could cause this problem? how to set the local filesystem to largefile filesystem at tru64 UNIX?

thanks a lot

[Steven Schweda]

> how to set the local filesystem to
> largefile filesystem at tru64 UNIX?

I don't think that there's a small-file
option on Tru64. Can you create a large
file locally?

You might be seeing an NFS limitation (2GB
for v2?).

"AIX" is not a complete description of the
environment on that system, nor is "tru64" a
complete description of the environment on
that system. "uname -a", "oslevel",
"sizer -v", ...

What does "ls -l" say about this file, on
each system? There's probably some way to
find out which NFS protocol version is being
used, but I don't know it.

[stephen peng]

hi steven,
thank you for your reply.
bash-2.01# ls -l
total 32217072
-rw-r----- 1 root system 32990238720 Mar 25 09:19 data1.tar

bash-2.01# date
Thu Mar 26 11:33:37 CST 2009
bash-2.01# cp /data/data1/data1.tar /data1/

bash-2.01# ls -l
total 10120
drwx------ 2 root system 8192 Mar 26 10:38 .tags
-rw-r----- 1 root system 10321920 Mar 26 11:34 data1.tar
-rw-r----- 1 root operator 8192 Mar 26 10:38 quota.group
-rw-r----- 1 root operator 8192 Mar 26 10:38 quota.user

above is the ls -l output of the procedure, and /data is the NFS filesystem.

i'm not familiar with NFS version issue, if there is a limitation of NFS v2, why data1.tar at /data1 remains about 10m at that copy procedure and not increases?

thanks a lot

[Venkatesh BL]

can you post the 'du -k file_name' and 'cksum file_name' output for both the files?

[Rob Leadbeater]

Hi,

I would also check whether there are any underlying network issues, that could be causing the NFS copy to hang.

The output of "netstat -i" should show you that.

Cheers,

Rob

[Steven Schweda · Accepted solution]

> -rw-r----- 1 root system 32990238720 Mar 25 09:19 data1.tar

I read that "32990238720" as about 33GB, not
"about 3g".

> if there is a limitation of NFS v2, why
> data1.tar at /data1 remains about 10m at
> that copy procedure and not increases?

What is 32990238720 modulo 2^32?

If the file size is over the limit, I don't
know which bad things will happen.

> What does "ls -l" say about this file, on
> each system?

I was hoping to see "ls -l" run on both
systems (among other things).

A Web search for keywords like:
nfs 2gb
might be educational.

> I would also check whether there are any
> underlying network issues, that could be
> causing the NFS copy to hang.

A test involving a file smaller than 2GB
should reveal any fundamental network
problems.