Can't delete file

everal · 01-23-2007, 10:46 AM

Hey, I just can't delete a file...

System crash, and I get this error message repeated some times before all stops:

virtua kernel: [17180580.344000] Code: 24 18 50 ff 74 24 18 8d be 60 01
00 00 e8 ba fd ff ff 58 5a 85 f6 89 d8 0f 45 c7 68 e0 fe 7a c0 50 68 00 59
58 c0 e8 71 8a f7 ff <0f> 0b 6a 01 c9 48 57 c0 83 c4 0c 85 f6 68 e0 fe 7a
c0 0f 45 df

It is not the first time it happens, I had another file like this... well, I still have it... but now I'd like to discover how to resolve this.

MensaWater · 01-23-2007, 12:36 PM

Are you saying the system crashes when you try to delete the file?

Exactly what file are you attempting to delete?

Did you try running lsof against the file (or even fuser)?

everal · 01-23-2007, 01:18 PM

Hey...

the file is:
ResourceDatabase.dat.old
(something from a winz game,Anarchy ON Line, that I was trying to run under cedega)

and I have the same problem with another, DoctorWho.avi

I try to delete as user, as root... the same thing happens, total crash

I don't know how to user the lsof or the fuse... reading man pages... it seams that lsof does a lot of stuff with 2 hundred options... wills ee and then I post..

btw, I use reiserfs, they are in very different partitions, home and var, and belong to different users, me and root, ... so if the problem is the filesystem, I am f*ed...

MensaWater · 01-23-2007, 01:36 PM

lsof <filename>

Will show you any processes that have the file open. If a file is open by a process it shouldn't be deleted. In fact it never really is - only the name is - the inode stays active until the process that is holding it open goes away - like in a reboot.

Neither of those sound like critical system files so deleting them even with a running process shouldn't cause a crash.

It sounds as if you may be having a drive issue. Have you looked through /var/log/messages (messages.1, messages.2 etc...) at the time of the crash to see if any errors occurred at that point?

It might be worthwhile to reboot and run an fsck on the filesystem at boot. I wouldn't do that until I'd ruled out a drive issue though - it might make things worse. You may want to try backing up everything then doing it.