SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Location: Zona Leste, Sao Paulo, Brazil, South America, Alpha Quadrant, Milk Way
Distribution: Slackware 14.0
Posts: 140
Original Poster
Rep:
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...
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.