shang3000
asked on
what is the bug in my filesystem
hi all,
I'm trying to find apr-config
but I got this error and I do not konw if there is a bug on my box or what to do
[root@shang ~]# find / -name apr-config
find: WARNING: Hard link count is wrong for /proc: this may be a bug in your filesystem driver. Automatically turning on find's -noleaf option. Earlier results may have failed to include directories that should have been searched.
/usr/bin/apr-config
best regards
HG
I'm trying to find apr-config
but I got this error and I do not konw if there is a bug on my box or what to do
[root@shang ~]# find / -name apr-config
find: WARNING: Hard link count is wrong for /proc: this may be a bug in your filesystem driver. Automatically turning on find's -noleaf option. Earlier results may have failed to include directories that should have been searched.
/usr/bin/apr-config
best regards
HG
ASKER
hi psyclown-,
thanks for reply
but I have a simple question from where do I get the linux rescue
please execuse my ignorance
best regards
HG
thanks for reply
but I have a simple question from where do I get the linux rescue
please execuse my ignorance
best regards
HG
Try this: http://rescuecd.pld-linux.org/
Otherwise your distributer of the linux you are using, probably have some kind of rescue tool on one of their cd's.
Otherwise your distributer of the linux you are using, probably have some kind of rescue tool on one of their cd's.
Hi,
It has nothing to do with with fsck!!!! This is not a problem of /proc filesystem or your fsck program!!! You should never use find against your /proc filesystem. /proc filesystem is directly managed by the kernel and *should not* be modified. /proc entries are created when the kernel runs a porcess or deleted when the kernl stops the porcess. When you do ls you'll see lots of 0 byte files but yet when you cat them they contain data this is because kernel manages them.
The command says that it is enabling the noleaf option and it is giving you a result if you dont want to see this error message siply use the alias command such as:
alias find='find -noleaf'
and to make it permanent add this command to your ~/.bashrc
You should never try to fix /proc filesystem using fsck !!!!!!!!!!!!!!!
It has nothing to do with with fsck!!!! This is not a problem of /proc filesystem or your fsck program!!! You should never use find against your /proc filesystem. /proc filesystem is directly managed by the kernel and *should not* be modified. /proc entries are created when the kernel runs a porcess or deleted when the kernl stops the porcess. When you do ls you'll see lots of 0 byte files but yet when you cat them they contain data this is because kernel manages them.
The command says that it is enabling the noleaf option and it is giving you a result if you dont want to see this error message siply use the alias command such as:
alias find='find -noleaf'
and to make it permanent add this command to your ~/.bashrc
You should never try to fix /proc filesystem using fsck !!!!!!!!!!!!!!!
Please ignore psyclone's comments. I'm sure he did not notice that yr talking about the /proc filesystem for a moment!
oh he did my bad did not read the second paragraph :)
My bad, i guess i misunderstood the question, i'll take that one on my cape
ASKER
hi KeremE,
thanks for reply
I did what you said and here is the result
[root@shang ~]# alias find='find -noleaf'
[root@shang ~]# find / -name apr-config
find: paths must precede expression
Usage: find [-H] [-L] [-P] [path...] [expression]
can you please guide me what is going wrong
best regards
HG
thanks for reply
I did what you said and here is the result
[root@shang ~]# alias find='find -noleaf'
[root@shang ~]# find / -name apr-config
find: paths must precede expression
Usage: find [-H] [-L] [-P] [path...] [expression]
can you please guide me what is going wrong
best regards
HG
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thanks alot man,
best regards
HG
best regards
HG
Yr welcome :)
1. Use "linux rescue" after putting in the first CD, rather than an
install. This way the OS is booted from the CD, and you can fsck any
partition, just remember to "umount" it first.
2. Never run fsck (or e2fsck) on /proc. It's a virtual filesystem, so
not only doesn't exist it doesn't get corrupted.
got it from:
http://mailman.lug.org.uk/pipermail/peterboro/2005-August/002767.html