HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- An error message
Operating System - Linux
1827862
Members
1624
Online
109969
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-07-2009 09:58 AM
08-07-2009 09:58 AM
An error message
I was running the find command and found the following error message:
# find / -name dsmerror.log
find: WARNING: Hard link count is wrong for /dev/oracleasm: 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.
Can some one please give me some clue.
# find / -name dsmerror.log
find: WARNING: Hard link count is wrong for /dev/oracleasm: 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.
Can some one please give me some clue.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2009 12:28 AM
08-08-2009 12:28 AM
Re: An error message
/dev/oracleasm, /proc and /sys are virtual filesystems.
If you are looking for a log file, it isn't going to be in any of them, so searching through them is just a waste of time.
In this particular case, /dev/oracleasm is an imperfect imitation of a normal filesystem, and the find command has just noticed the imperfection. The "-noleaf" option causes find to be extra careful, which is needed in some special filesystems. Unfortunately, that option is also going to make your search slower.
See "man find"; search for "-noleaf" and read the full description of the option from there.
The problem is in the oracleasm kernel module that creates the oracleasmfs virtual filesystem. Because /dev/oracleasm is essentially just another way to identify the disks controlled by Oracle ASM, the bug is not dangerous, just a nuisance. Maybe Oracle has already released a patch for ASM and/or asmlib that fixes it?
MK
If you are looking for a log file, it isn't going to be in any of them, so searching through them is just a waste of time.
In this particular case, /dev/oracleasm is an imperfect imitation of a normal filesystem, and the find command has just noticed the imperfection. The "-noleaf" option causes find to be extra careful, which is needed in some special filesystems. Unfortunately, that option is also going to make your search slower.
See "man find"; search for "-noleaf" and read the full description of the option from there.
The problem is in the oracleasm kernel module that creates the oracleasmfs virtual filesystem. Because /dev/oracleasm is essentially just another way to identify the disks controlled by Oracle ASM, the bug is not dangerous, just a nuisance. Maybe Oracle has already released a patch for ASM and/or asmlib that fixes it?
MK
MK
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP