Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
My /var/spool/ and /var/lib/ directories have changed to unknown file types suddenly. I don't know what caused this. Any one please help me. This is the second time this is happening. Earlier this happened to /tmp directory. Then I removed the tmp and created another tmp directory and rebooted. This solved the problem. But nw I dont know what t do with this. Any one please help me....
?--------- 12 root root 4096 Nov 3 19:33 lib
?--------- 12 root root 4096 Nov 3 19:33 spool
I've had this happen with external drives. Powering them down and up again and remounting fixed the problem. For some reason they were being detected as "TI boot devices" whatever that is. I think internally, the external drives controller has a problem accessing one of the component drives.
Look in your logs and see if there are IO errors access the drive. If so, then you probably have a bad cable or a drive that is going bad. If the drive is going bad (as in bad blocks, not in the electronics) running the commercial program "spinrite" may be able to fix enough of the drive so that you can pull the data off of the drive before you replace 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.