Solved

ldconfig breaks inode???

Posted on 1997-08-29
5
473 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 2

Expert Comment

by:nicademus
ID: 1629422
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
ID: 1629423
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
ID: 1629424
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
ID: 1629425
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
ID: 1629426
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

Enroll in May's Course of the Month

May’s Course of the Month is now available! Experts Exchange’s Premium Members and Team Accounts have access to a complimentary course each month as part of their membership—an extra way to increase training and boost professional development.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

The purpose of this article is to demonstrate how we can use conditional statements using Python.
Join Greg Farro and Ethan Banks from Packet Pushers (http://packetpushers.net/podcast/podcasts/pq-show-93-smart-network-monitoring-paessler-sponsored/) and Greg Ross from Paessler (https://www.paessler.com/prtg) for a discussion about smart network …
Learn how to get help with Linux/Unix bash shell commands. Use help to read help documents for built in bash shell commands.: Use man to interface with the online reference manuals for shell commands.: Use man to search man pages for unknown command…
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.

734 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