[comp.unix.ultrix] truncated inode

jv@mh.nl (Johan Vromans) (01/13/90)

After a system crash (VAXstation3100), fsck -p on one of my drives
(CDC94171) yields:

  PARTIALLY TRUNCATED INODE I=4 (CORRECTED)
  INCORRECT BLOCK COUNT I=4 (88296 SHOULD BE 88312) (CORRECTED)
  14376 BLOCKS MISSING
  BAD CYLINDER GROUPS (SALVAGED)
  FILE SYSTEM MODIFIED, VERIFYING
  PARTIALLY TRUNCATED INODE I=4 (CORRECTED)
  FILE SYSTEM MODIFIED, VERIFYING
  PARTIALLY TRUNCATED INODE I=4 (CORRECTED)
  3 files, 88321 used, 462708 free (12 frags, 57837 block)

(the amount of 3 files is correct, there was only one (big) file on
the disk at the time of the crash.)

However, after checking, the disk is still unclean, and a rerun of
fsck -p will result in another three attempts to repair the truncated
inode.
Has anyone any ideas what is happening here?

Thanks in advance.

Johan
--
Johan Vromans				       jv@mh.nl via internet backbones
Multihouse Automatisering bv		       uucp: ..!{uunet,hp4nl}!mh.nl!jv
Doesburgweg 7, 2803 PL Gouda, The Netherlands  phone/fax: +31 1820 62944/62500
------------------------ "Arms are made for hugging" -------------------------

grr@cbmvax.commodore.com (George Robbins) (01/13/90)

In article <JV.90Jan12102035@mhres.mh.nl> jv@mh.nl (Johan Vromans) writes:
> After a system crash (VAXstation3100), fsck -p on one of my drives
> (CDC94171) yields:
> 
>   PARTIALLY TRUNCATED INODE I=4 (CORRECTED)
...
>   3 files, 88321 used, 462708 free (12 frags, 57837 block)
> However, after checking, the disk is still unclean, and a rerun of
> fsck -p will result in another three attempts to repair the truncated
> inode.

Check your /etc/uerf -R output to see if there is any hardware error
being reported.  Do a "dcheck -i 4 /dev/..." to see which of files
it was.  You can then use "mount -o force ..." to mount the unclean
drive and look at the file or blow it away.  There's always newfs.

You might also try doing an plain "fsck" on the drive instead of the
"fsck -p".  This may give more information or options.  Finally, there
is a section on fsck in the System Administrators part of the "Ultrix
Supplementary Documentation" that tell something about what the errors
mean.


-- 
George Robbins - now working for,	uucp: {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)