home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.unix.admin:4582 comp.sys.hp:9401
- Newsgroups: comp.unix.admin,comp.sys.hp,ctp.it
- Path: sparky!uunet!mcsun!sun4nl!alchemy!prisma!fred
- From: fred@cv.ruu.nl (Fred Appelman)
- Subject: Re: 8 MUST BE 0
- Message-ID: <1992Aug18.182757.13827@cv.ruu.nl>
- Date: Tue, 18 Aug 1992 18:27:57 GMT
- References: <1992Aug18.133511.193@ctp.com>
- Organization: University of Utrecht, 3D Computer Vision Research Group
- Lines: 32
-
- In <1992Aug18.133511.193@ctp.com> jmay@ctp.com (Jason May) writes:
-
-
- >HP 9000/847, running HPUX 8.02.
- >
- >Our machine crashes from time to time, and during reboot we virtually
- >always see messages of the form
- >
- >/dev/rroot: INCORRECT BLOCK COUNT INODE = 12345 (8 MUST BE 0) (CORRECTED)
- >
- >We assume this comes from fsck doing its job, but what exactly does
- >'8 must be 0' mean? Eight blocks, presumably, but why should there
- >be zero of them?
-
- I am just guessing here: I think what that means is that just before
- crashing the filesystem allocated a inode and some blocks that belong
- to that inode. Somehow the number of blocks is administrated, but the
- block themselfs not. Make the INODE block count 0 is another
- way to tell that the inode is freed.
-
- I do remember that the error codes that are produces by fsck are in
- the manual. There is a seperate section that describes fsck.
-
- >It appears that /dev/root and /dev/rroot are special links to the
- >disk partition with the root file system. Why do both of these
- >exist? Could they ever be different? Who uses them?
-
- /dev/root is the block device, /dev/rroot is the raw device. Block devices
- are used if you access the disk via the filesystem. Raw devices bypass
- the filesystem and should therefore only be used on unmounted discs.
-
- Fred
-