[EMAIL PROTECTED] said:
> I recently helped a customer who upgraded to a SPARCstation 10 without
> replacing his sun4c vfsck binary. When the fileserver started, tons
> of SCSI errors started showing up in the syslog file and the machine
> eventually went out to lunch. Using the sun4m version of vfsck
> corrected some superblock problems and the machine lived happily ever
> after!
>
> I had thought that vfsck would fall under the "application
> architecture" rules, but it apparently does not.
It's more likely the case that it's not the sun4c vs sun4m issue, but
the 4.1.1 vs. 4.1.2 (or 3) issue. Sun changed their 4.2 filesystems
around a bit between 4.1.1 and 4.1.2. (Which, added a clean bit among
other things. When is vfsck for sun4*_41[23] gonna support this?)
> Joe Jackson,
> AFS Product Support,
> Transarc Corp.
- Chris
--
Chris P. Ross University Of Maryland
[EMAIL PROTECTED] Engineering Computer Facility
Work#: (301)/405-3689 Project GLUE
"If we knew what we were doing, it wouldn't be called research."
