lina wrote: > Bob Proulx wrote: > > Here is a wild guess. Are you copying files to or from a MS FAT > > filesystem? If so then the issue there is that FAT only stores > > No. I copied from (I don't know how to tell the filesysem. is it below > information?) > > Source: > $ df -h b1009a/ > Filesystem Size Used Avail Use% Mounted on > /dev/gpfs0 255T 38T 218T 15% /gpfs To get filesystem information add the -T option. Try this: df -hT It will add a new column with the type of the filesystem. (There is also a way to get this using 'find' too.) > ]$ df -h ../b1009a/ > Filesystem Size Used Avail Use% Mounted on > honeydewlocal:/vol/hpc_vol/HomeHPC > 2.5T 1.6T 917G 63% /home > ... > I tried, seems not the window reason. -u works. That looks to be an NFS mounted filesystem. Right? If so then time is almost certainly the problem. I am sure the problem is that the time is set different between the client and server. This is an often seen problem when the time is not correct on the different machines. Do you have access to see the time on honeydewlocal? I am sure the time is incorrect either on your system or on honeydewlocal. Or on both! Correct this and it will fix the problem. And it is important to do because other problems will be avoided too. I would check in a simple way like this: $ date -R ; ssh honeydewlocal date -R ; date -R When I use a machine here I see: Tue, 28 Feb 2012 10:33:20 -0700 Tue, 28 Feb 2012 10:33:20 -0700 Tue, 28 Feb 2012 10:33:20 -0700 If you see something wild then that is definitely the problem. I always install 'ntp'. Do this on *both* machines. # apt-get install ntp There are also some other tools that some people like better. They are okay too but ntp is very mature and what I always use. The most important thing to avoid is to never use cron to step the clock. This is a trap that people often fall into. For some reason people often create a cron task that periodically steps the clock to the right time. That is not the right way to to do it and creates additional problems that are even harder to figure out. So whatever you do don't step the clock with cron. Bob
Attachment:
signature.asc
Description: Digital signature