(Illustration by Gaich Muramatsu)
Steven, We never build Linux kernels in Coda, we always build Coda in Coda. I'm swamped today and away until next wednesday, but I want to try myself -- I'll probably ask Henry to give it a first shot. I have seen files truncated to 0 length -- I have never understood it. One suggestion I have is to make the local cache bigger (e.g. 40000, 40M). That's what we use here normally and it gives us little trouble. So in short: we'll come back to this and find out what's going on but not this week. - Peter - On Thu, 12 Feb 1998, Steven N. Hirsch wrote: > Peter, et al, > > My joy is short-lived. Two attempts at building a linux kernel on a coda > filesystem have failed with spurious truncated *.o files. Different files > both times. > > For another data point, a "make boot" insists upon rebuilding absolutely > everything from the beginning on a subsequent restart. Granted that the > kernel build process is a bit kludgy (though getting better), but it is > substantially smarter than this on an NFS or local filesystem. > > To my eyes, the datestamps look valid and I cannot understand why make > thinks it needs to rebuild everything. Is there a difference in how > stat() reports file information on a coda filesystem that could account > for this? > > What would you like me to try in pursuit of the file corruption issues? > > Steve > >Received on 1998-02-12 09:03:46