On Mon, Jun 23, 2008 at 10:23 PM, Jeff Blaine <[EMAIL PROTECTED]> wrote:
> We recently re-imaged a fileserver (Solaris 9). For > every slice of our old /vicep data, we are getting > the following error at boot time. Here's one example: > > # /usr/lib/fs/afs/fsck -o b=512272 /dev/dsk/c3t6006016012341600D86B14C >> 7E294DA11d0s0 >> >> ----Open AFS (R) openafs 1.4.6 fsck---- > > A change (fix) to parsing of alternate superblock arguments to fsck is in 1.4.7. >> Alternate super block location: 0 >> ** /dev/dsk/c3t6006016012341600D86B14C7E294DA11d0s0 >> 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). >> > > No matter what superblock alternate is specified... same error. > > The /usr/afs portion was selectively copied from another > fileserver of the same architecture after the host in question > was reimaged (no sysid, no logs, no fssync.sock, no salvage.lock). > > The fun part is, the partitions get mounted just fine and > everything is peachy. Lucky for us. > >
