Solved

ldconfig breaks inode???

Posted on 1997-08-29
5
464 Views
Last Modified: 2013-12-15
Hi

I've found that on my Slackware system with 2.0.30 kernel, every time ldconfig is run (originally it was in rc.S) it 'breaks' and inode, causing a fsck to give the following message when check is forced:

Deleted inode n has zero dtime

The inode number(n) seems to be the inode number of ld.so.cache. I am wondering how to stop it from doing this.

My system in a P100MHz with 32MB RAM, 32MB swap, 1GB (windoze) and 3.1GB(linux and extra windoze) drives.
0
Comment
Question by:bungholio
  • 3
  • 2
5 Comments
 
LVL 2

Expert Comment

by:nicademus
Comment Utility
Are you really worried about this?  Does your system become unstable?

When you run idconfig, does this cause a crash, and when you re-boot and fsck runs it comes up with only that error message?

If you will notice ld.so.cache is just that, a cache once the system has gone down, it no longer needs this, and the next time ld.so is used it will build a new cache, relevent to it's current operations.  I have pretty much exactly the same setup as you, except I have stuck with 2.0.29 (although I am experimenting with 2.1.51 as the moment), because It has been noted that 2.0.30 does have some errors, this may just be one of them, but as I have said, unless your system is loosing data, and crashing, behaving weirdly, not able to compile things (within reason-i.e. 50% of all compiles fail due to little errors in configs.).  Just leave it as is.  By the way what version of ld.so do you have..?  check by doing "ldd -V"
0
 

Author Comment

by:bungholio
Comment Utility
No, it isn't crashing at all. I've heard that the deleted inode error is harmless, just a timing problem when 2 progs try to access the inode at the same time. Its just annoying me that I (used to) get these error messages and I'm trying to figure out why.

I am using v. 1.8.2. I will try upgrading and see if that helps (If I can find it). I don't think 2.0.30 is the problem 'cos it also happened with 2.0.0 and I know somebody with the problem who also uses 2.0.0
0
 
LVL 2

Expert Comment

by:nicademus
Comment Utility
SOmething you may have to watch out for when you upgrade is that when you gunzip and untar the ld.so into it's respective directory I have found this crashes my system, and one instance when I had to reboot (Reset switch) it told me that I had to do an fsck manually, because it couldn't do jack!  I had to go over it a couple of times, using my vmlinuz on my DOS partition, and such, and it kept coming up and fixing the summary info, and deleting whole bunches of inodes.  Just be careful, I think what I did was unzipped it all, etc, but in a different directory, then moved the files.  Good luck all the same, and I'll keep an eye out, to see how you go, and maybe I can think of something...
0
 

Author Comment

by:bungholio
Comment Utility
It seems to have worked. I got ldso 1.9.5, copied ldconfig, ldd, libdl, ld-linux and the man pages out of the archive and changed to symbolic links. Then I ran [the new] ldconfig to update the cache and it worked!

I don't how how to say that this question has been answered. Nicademus, you gave me the vital insight, so if you now "answer" the question I'll give you the credit and 200 points. Thanks
0
 
LVL 2

Accepted Solution

by:
nicademus earned 200 total points
Comment Utility
Well what to say, I suppose I'll just post the same answer again....
If you will notice ld.so.cache is just that, a cache once the system has gone down, it no longer needs this, and the next time ld.so is used it will build a new cache relevent to it's current operations. I have pretty much exactly the same setup as you, except I have stuck with 2.0.29 (although I am experimenting with 2.1.51 at the moment), because It has been noted that 2.0.30 does have some errors, this may just be one of them, but as I have said, unless your system is loosing data, and crashing, behaving weirdly, not able to compile things (within reason-i.e. 50%
of all compiles fail due to little errors in configs.). Just leave it as is. By the way what version of ld.so do you have..? check by doing "ldd -V"

Anyway Not a problem Bungholio, thanks...=)
0

Featured Post

Maximize Your Threat Intelligence Reporting

Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

Join & Write a Comment

Introduction We as admins face situation where we need to redirect websites to another. This may be required as a part of an upgrade keeping the old URL but website should be served from new URL. This document would brief you on different ways ca…
It’s 2016. Password authentication should be dead — or at least close to dying. But, unfortunately, it has not traversed Quagga stage yet. Using password authentication is like laundering hotel guest linens with a washboard — it’s Passé.
Learn several ways to interact with files and get file information from the bash shell. ls lists the contents of a directory: Using the -a flag displays hidden files: Using the -l flag formats the output in a long list: The file command gives us mor…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

14 Experts available now in Live!

Get 1:1 Help Now