> there's an issue in the 1.6.0 fileserver > okay, good to know about the 1.6.0 server. i'll be moving volumes off of these servers then.
> but if you are also having it on 1.4.14 that's new > that got me thinking: looking at our logs more closely, i see that at the time when the file corruption was noticed the volume was on the 1.6.0 server, but it has since moved to a 1.4.14 server (a whole batch of volumes was moved off the 1.6.0 server for an unrelated reason). sorry about that; looks like 1.4.14 is probably out of this equation. -- Jonathan.Nilsson at uci dot edu Social Sciences Computing Services SSPB 1265 | 949.824.1536
