aarons@syma.sussex.ac.uk (Aaron Sloman) (11/21/90)
Have other users noticed this problem. I append some correspondence involving a "bug-report" from one of the users of our Poplog system. > From CJT(Edinburgh) > > > I find that, if there is insuficient disk space, writing a file in > > Poplog version 13.8 produces a file full of nulls and no complaint! Is it > > possible I have done something to cause this? Is it a feature? Is it a > > bug? From JG (Sussex - chief Poplog Programmer) | I did quite a lot of experimenting and (as I expected) the problem lies | with NFS. | | When writing to a local disk, there doesn't seem to be any problem. But | trying to write to a remote disk that's full seems to get into a funny | state where if the file being written is small enough it appears to work | (and doing "ls -l" on the file says it's there and the correct size), | but then you look at the file a little later, and it's become zero size. | | I made this happen just with "cp"; the problem has absolutely nothing | whatsoever to do with Poplog. So CJT, get your system support people to | complain to Sun (or get a bigger disk). Is this a recognized SunOS 4.1/NFS problem? If so it sounds very serious and should receive immediate attention from Sun. Aaron Sloman, School of Cognitive and Computing Sciences, Univ of Sussex, Brighton, BN1 9QH, England EMAIL aarons@cogs.sussex.ac.uk or: aarons%uk.ac.sussex.cogs@nsfnet-relay.ac.uk