loki@physics.mcgill.ca (Loki Jorgenson Rm421) (06/14/90)
We have a mixed IRIS/SUN environment (IRIX3.2.1/SUN OS3.5). When one does a "du" on an IRIS-owned NFS-mounted file system from a SUN, the number of bytes is wrong. Usually, it is only a small fraction of what is truly there. I am aware of the bytes/blocks distinction between the two machines. (ie. IRISes measure things in 512 byte blocks). This disparity is much worse than that. There is *definitely* something amiss. Is there a fix? Regards, Loki Jorgenson node: loki@physics.mcgill.ca Physics, McGill University fax: (514) 398-3733 Montreal Quebec CANADA phone: (514) 398-6531 << Waxing frees the mind and makes the legs smooth >>
paquette@cpsc.ucalgary.ca (Trevor Paquette) (06/15/90)
In article <9006141154.AA22997@frodo.Physics.McGill.CA>, loki@physics.mcgill.ca (Loki Jorgenson Rm421) writes: > > We have a mixed IRIS/SUN environment (IRIX3.2.1/SUN OS3.5). When > one does a "du" on an IRIS-owned NFS-mounted file system from a > SUN, the number of bytes is wrong. Usually, it is only a small fraction > of what is truly there. > ... stuff deleted ... > Loki Jorgenson node: loki@physics.mcgill.ca Try doing a 'du -k' on the Iris. This is undocumented and will give you the free space, space used, etc in Kbytes. This should make things a little more understandable. (Got this little tidbit from an SGI hardware guy that was upgrading our machine). Trev ___________________________________________/No man is a failure who has friends Trevor Paquette ICBM:51'03"N/114'05"W|I accept the challange, body and soul, {ubc-cs,utai,alberta}!calgary!paquette|to seek the knowledge of the ones of old paquette@cpsc.ucalgary.ca | - engraved on the Kersa Blade of Esalon