topic ghost file cannot be deleted in Operating System - HP-UX

ghost file cannot be deleted

Clara Rowe — Tue, 27 Feb 2001 18:57:30 GMT

First, I'd like to thank everyone that responds to this forum. I have found many solutions to problems and great advice.

I have a very weird problem. I seem to have a ghost file that I cannot delete. Please note:

root#> rm -r log1
rm: cannot stat log1/l421994.req: No such device or address
rm: directory log1 not removed. Directory not empty
root#> cd log1
root#> pwd
/vol23/tmp7/log1
root#> ls -l
./l421994.req not found
total 0
root#> ls -a
. .. l421994.req
root#> ls -b
l421994.req
root#> rm -r l421994.req
rm: cannot stat l421994.req: No such device or address
root#>

I have also noticed the following entries in my syslog:
Feb 24 03:07:04 hpd370 vmunix: vxfs: mesg 008: vx_direrr - /vol23 file system inode 40998 block 78930 error 6
Feb 24 04:32:57 hpd370 vmunix: vxfs: mesg 016: vx_ilisterr - /vol23 file system error reading inode 49535

I am assuming that somehow the file was deleted and not the inode. Can someone tell me how to remove it?

Thanx for help in advance.
Clara

Re: ghost file cannot be deleted

Andy Monks — Tue, 27 Feb 2001 19:12:04 GMT

it looks like you might want to fsck that filesystem. Umount at sometime and fsck with the -o full option (it will take quite a while depending on the size and number of files).

Re: ghost file cannot be deleted

Rita C Workman — Tue, 27 Feb 2001 19:13:14 GMT

Sounds to me like you need to run fsck on this file system. You'll need to umount the file system first then run fsck to repair. Since the filesystem does not appear to be o/s related you should be able to umount it once all the processes are stopped without rebooting into single user..

If fsck can not repair than you probably have a disk problem...

/rcw

Re: ghost file cannot be deleted

Patrick Wallek — Tue, 27 Feb 2001 19:18:23 GMT

I concur with the other responses in that you probably need to fsck this LV.

Here are a couple of documents from the ITRC that may help you as well:

http://us-support3.external.hp.com/cki/bin/doc.pl/sid=1689613b0237fafdb2/screen=ckiDisplayDocument?docId=200000024604001

http://us-support3.external.hp.com/cki/bin/doc.pl/sid=1689613b0237fafdb2/screen=ckiDisplayDocument?docId=200000041138793

Re: ghost file cannot be deleted

Clara Rowe — Tue, 27 Feb 2001 22:02:27 GMT

Hi guys,
I accidently hit new message instead of reply. This is the result:
root#> fsck -y /dev/vg304/lvol23
log replay in progress
pass0 - checking structural files
pass1 - checking inode sanity and blocks
fileset 999 inode 49520 marked bad, allocation flags 0001 clear? (ynq)y
fileset 999 inode 49521 marked bad, allocation flags 0001 clear? (ynq)y
fileset 999 inode 49522 marked bad, allocation flags 0001 clear? (ynq)y
fileset 999 inode 49523 marked bad, allocation flags 0001 clear? (ynq)y
fileset 999 inode 49524 marked bad, allocation flags 0001 clear? (ynq)y
fileset 999 inode 49525 marked bad, allocation flags 0001 clear? (ynq)y
fileset 999 inode 49526 marked bad, allocation flags 0001 clear? (ynq)y
fileset 999 inode 49527 marked bad, allocation flags 0001 clear? (ynq)y
fileset 999 inode 49528 marked bad, allocation flags 0001 clear? (ynq)y
fileset 999 inode 49529 marked bad, allocation flags 0001 clear? (ynq)y
fileset 999 inode 49530 marked bad, allocation flags 0001 clear? (ynq)y
fileset 999 inode 49531 marked bad, allocation flags 0001 clear? (ynq)y
fileset 999 inode 49532 marked bad, allocation flags 0001 clear? (ynq)y
fileset 999 inode 49533 marked bad, allocation flags 0001 clear? (ynq)y
fileset 999 inode 49535 marked bad, allocation flags 0001 clear? (ynq)y
pass2 - checking directory linkage
fileset 999 directory 40998 block 78930 offset 2 references free inode
ino 49535 remove entry? (ynq)y
fileset 999 directory 40998 block 78930 rebuild header? (ynq)y
pass3 - checking reference counts
rebuild structural files? (ynq)y
pass0 - checking structural files
pass1 - checking inode sanity and blocks
pass2 - checking directory linkage
pass3 - checking reference counts
pass4 - checking resource maps
fileset 999 au 3 imap incorrect - fix (ynq)y
fileset 999 au 6 imap incorrect - fix (ynq)y
incorrect CUT entry for fileset 999, fix? (ynq)y
au 101 emap incorrect - fix? (ynq)y
au 101 summary incorrect - fix? (ynq)y
fileset 999 iau 3 summary incorrect - fix? (ynq)y
fileset 999 iau 6 summary incorrect - fix? (ynq)y
fileset 999 iau 8 summary incorrect - fix? (ynq)y
fileset 999 iau 10 summary incorrect - fix? (ynq)y
fileset 999 iau 11 summary incorrect - fix? (ynq)y
free block count incorrect 2087159 expected 2087191 fix? (ynq)y
free extent vector incorrect fix? (ynq)y
OK to clear log? (ynq)y
set state to CLEAN? (ynq)y

I guess that means it worked. Thanx Patrick for your help on my "new Message" http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0x3fc06af52b04d5118fef0090279cd0f9,00.html

Thanx again everyone!
Clara