Summary: NFS Oddity.

Dear Managers,

It turned out that the problem was with the "date" on the files and dirs.

They were all before Epoch(2 were 1969, one was 1902)

Setting the dates to somedate in 2000, seemed to solve the problem. I
accidently did an ls -l and spotted it.

Many thanks to those who replied including Mark Hargrave who also
suggested the same could be a problem.

Could someone please shed some light on

* How this could happen ? (NFS Bug, bad battery)

* Steps that can be taken to prevent this.

Best Regards,

/dev/null

devnull@adc.idt.com

Original Post:
-------------
Dear Managers,

I have a strange NFS problem, and was hoping that ya'll would be able to
shed some light on what might be going on.

I have an Ultra-30 running Solaris 8, which acts as our Slave NIS server
and a NFS server. (lets call it slave)

I have a 50G partition on the machine(made some 4-5 years back by another
administrator), that has some NFS problem.

On all my client machines i am able to see all dir under that partition
except a few, and when i do an ls on those dir, i get the error  "Invalid
argument"

I am able to see these files and dir on "slave" from its UFS partition and
also when i browse to it through the NIS mount points(but only on that
machine).

I can all other files and dir on other client machines.

I ran fsck on the filesystem and there are no errors.

Any pointers will be greatly appreciated.

Regards.
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers