Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
okay, as root i umount /home, did fsck /dev/hda7 (the home partition)
and here's what it said
openlight:~# fsck /dev/hda7
fsck 1.36-rc2 (11-Jan-2005)
e2fsck 1.36-rc2 (11-Jan-2005)
/home: clean, 1047/806400 files, 1144484/1611280 blocks
Aside from booting with a live-cd/rescue disk to run fsck, I don't know what else to tell you. Clearly, something is screwy with the filesystem. If you end up reformatting, I'd suggest ext3 instead of ext2. That would offer more protection against the filesystem getting "confused".
EDIT: Actually, e2fsck is used for ext3 filesystems isn't it? Oh well... I can't be sure it's ext2, but the suggestion for ext3 still stands
Last edited by Dark_Helmet; 01-22-2005 at 06:42 PM.
Just for laughs, what does stat heavenmissangel.mp3 have to say? You can also try to use emacs in directory edit mode (emacs /directory/file/is/in) to edit the directory listing and try to nuke the file. Do back your data up before trying that, though.
hey sorry i reformatted already, before i could read your post. if the thing comes back then I'll do the stat thing for kicks. why did this file, and another one as i later discover become device files? is it just hardware integrity issue? rootkit? ext3 random error? i'm using reiserfs for /home now, hopefully things will be good
I would think it was just a screw up in the filesystem. Unexpected loss of power during disk IO is one possible explanation. Ext3 is supposed to prevent that, but I don't think anything is 100%. In fact, I would go so far as to say it probably happened as the drive was writing the information for a new file. The OS had reserved an inode, had written some preliminary information, and then got cut off.Just enough information was written for the filesystem to think it was a valid entry, but not enough was written to create a coherent entry. Essentially, the filesystem knew where the file was supposed to start, and as it read the bytes on the disk at that location, it was reading somewhat random data, and interpreting it as best it could. When you tried to delete it, there were probably some sanity checks that failed, preventing any change to the disk information.
i have a file that i can't delete. it's not allowing me to mv it, chown it, chmod it, rm -f it, ... etc. as ROOT
what the hell do i do?
Originally Posted by Genesee
you might try chattr - see if that does anything
I ran into this same issue and was beginning to backup and re-format. But, then Genesee mentioned `chattr`. I, personally, had never used that tool before. So, I brought out `man lsattr` and found out that the file had the "a" flag set.
Originally Posted by man chattr
A file with the Ďaí attribute set can only be open in append mode for writing. Only the superuser or a process possessing the CAP_LINUX_IMMUTABLE capability can set or clear this attribute.
Well `chattr -a .secure.PayPal.com` as root did the trick. My old RH7.3 box was hit by a worm that setup a phishing site. It goes without saying, keep up with the updates!