Xref: utzoo comp.unix.ultrix:2525 comp.unix.wizards:20149 Path: utzoo!attcan!uunet!cbmvax!grr From: grr@cbmvax.commodore.com (George Robbins) Newsgroups: comp.unix.ultrix,comp.unix.wizards Subject: Re: truncated inode Message-ID: <9331@cbmvax.commodore.com> Date: 12 Jan 90 19:19:17 GMT References: Reply-To: grr@cbmvax.commodore.com (George Robbins) Organization: Commodore, West Chester, PA Lines: 27 In article 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)