On Fri, 12 Nov 2004, Douglas E. Engert wrote: > > However I'm still getting the following error: > > ----Open AFS (R) openafs 1.2.13 fsck---- > > ** /dev/rdsk/c1t0d0s3 > > BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST > > ALTERNATE > > USE AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; > > eg. fsck [-F ufs] -o b=# [special ...] > > where # is the alternate super block. SEE fsck_ufs(1M). > > We have not seen this, but it sounds like you have much larger partitions.
<snip...> First, thanks to Doug for the help and the patience. After re-installing Solaris and AFS, trying different hardware, and still getting the same behavior, I think I've finally got this solved. The solution was simple and I feel a bit foolish for not realizing it earlier: starting with Solaris 9 9/04, UFS logging is enabled by default on most UFS filesystems. >From http://docs.sun.com/app/docs/doc/817-5770/6ml72d6kd?a=view "Logging is now enabled by default for all UFS file systems except under the following conditions: o When logging is explicitly disabled o If insufficient file system space exists for the log In previous Solaris releases, you had to enable UFS logging manually." My other servers are Solaris 9 12/03, so they never experienced this problem. To turn off logging, specify the "nologging" mount option for the /vicepX partitions in /etc/vfstab. Perhaps something to add to the FAQ (or SAQ). Cheers, Stephen -- Is the main reason Santa is so jolly because he knows where all the bad girls live? _______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
