root@grumbly.UUCP (Superuser) (03/17/90)
I've been having some wierdness with my root filesystem.
1) Last night I suddenely had only 11 inodes according to df. I really had
about 10,000. When I fsck'd, it said the problem was fixed, but it still
only showed 11 inodes. After reading some books, I tried fsck and as soon
as it was done I powered down. I restarted the computer, cleaned the
power off mess and I had my 10000 inodes back - everything looked fine.
2) This afternoon, after working fine this morning, when I use df the root
filesystem isn't reported - only the /dev/u. But if I use
df /dev/root then it reports it ok, but it wont report
df /dev/rroot - which is normal??
What is afoot here - I'm paranoid some evil presence is at work in the
filesystem.
Something that is probably relevant --> I have an intermittent bad cylinder
on the hard drive
Anybody want to take a stab at this one.
I'm running SCO Unix 3.2.1 (Open Desktop ,but this happens in straight unix)
Mylex 20 Mhz w/ 80387
8 megs memory
Miniscience HH1090 --> /dev/root
Miniscribe 3085 --> /dev/u
Western Digital 1006
Thank you for your great wisdom
davidsen@sixhub.UUCP (Wm E. Davidsen Jr) (03/22/90)
If ODT is like Xenix and most UNIX systems you get trouble when you
fsck a mounted filesystem. The usual way past this is to boot from
another device, but there is an alternate solution in Xenix (and
probably ODT) which is to use the -rr option (recover root). This
unmounts the filesystem, cleans it, and remounts it.
Before doing this you should run "fsck -n" first and be sure that the
filesystem is not badly blown, because if it can't be fixed, or
everything gets blownaway, the remount will fail. I found this out the
hard way, honest.
--
bill davidsen - davidsen@sixhub.uucp (uunet!crdgw1!sixhub!davidsen)
sysop *IX BBS and Public Access UNIX
moderator of comp.binaries.ibm.pc
"Getting old is bad, but it beats the hell out of the alternative" -anon