Very Computer

:Hi there: I always have the SuperBlock problem. Every time I run fsck and
:returns FILE SYSTEM STATE IN SUPERBLOCK IS WRONG; FIX? I choose yes. Next time
:the error message come up again. It seems nothing effect me, but always bother
:me.

Are you running fsck on a mounted file system?  If so, you probably don't
want to do that.

: I even tried to change the size of the superblock and no effect at all.

Oh my.

:The other problem is that I got a statement: line in vfstab has too few
:entries. I checked the vfstab file for couple of times and can not find
:anything wrong. I had manually added 4 lines there. I deleted them one by
:one, and even deleted all of them, still get the same message. Any ideas?

I've found that suprisingly easy to mess up.  I usually resort to
checking my edits with a litte nawk command, something like

nawk '{NF != 7}' < /etc/vfstab

That should print lines that don't have seven fields.
--
Jim Davis              | "Professor!  You turned it down again!!"

I imagine you are applying fsck to a mounted (and not read-only) filing system.
Be extremely cautious about allowing fsck to make changes in such situations
(although the above change is probably harmless).

Quote:>The other problem is that I got a statement: line in vfstab has too few
>entries. I checked the vfstab file for couple of times and can not find
>anything wrong. I had manually added 4 lines there. I deleted them one by
>one, and even deleted all of them, still get the same message. Any ideas?

Without a copy of your /etc/vfstab it's not easy to diagnose. Look for white
space that isn't :-) Every non-comment non-empty line should have exactly
7 white-space-seperated fields. If you are still at a loss, knock up a
program to call getvfsent(3c) yourself and see just when it is returning
VFS_TOOFEW.

Chris Thompson
Email: cet1 [at] cam.ac.uk

I have a similar problem, but the superblock error occurs already during booting
on /usr, i.e. when it is not mounted.  As a result of this block error is that I
end up
having occasional writing-to-disk problems. Using the alternative block I seems
to be better. And here is my question. Where can I instruct fsck to use the
alternative
superblock (32) *during* boot. I checked the boot scripts but I couldn't quite
find my
way through.

Thanks

Iead

:And here is my question. Where can I instruct fsck to use the
:alternative
:superblock (32) *during* boot.

I'd look at the /sbin/mountall shell script.

Well actually I'd look at identifying the real problem with that disk
or filesystem and fixing it properly, instead of trying some boot time
kludge around.
--
Jim Davis              | "Professor!  You turned it down again!!"