<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: An error message in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/an-error-message/m-p/4475648#M37861</link>
    <description>/dev/oracleasm, /proc and /sys are virtual filesystems. &lt;BR /&gt;&lt;BR /&gt;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. &lt;BR /&gt;&lt;BR /&gt;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. &lt;BR /&gt;&lt;BR /&gt;See "man find"; search for "-noleaf" and read the full description of the option from there.&lt;BR /&gt;&lt;BR /&gt;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?&lt;BR /&gt;&lt;BR /&gt;MK</description>
    <pubDate>Sat, 08 Aug 2009 07:28:05 GMT</pubDate>
    <dc:creator>Matti_Kurkela</dc:creator>
    <dc:date>2009-08-08T07:28:05Z</dc:date>
    <item>
      <title>An error message</title>
      <link>https://community.hpe.com/t5/operating-system-linux/an-error-message/m-p/4475647#M37860</link>
      <description>I was running the find command and found the following error message:&lt;BR /&gt;&lt;BR /&gt;# find / -name dsmerror.log&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;Can some one please give me some clue.</description>
      <pubDate>Fri, 07 Aug 2009 16:58:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/an-error-message/m-p/4475647#M37860</guid>
      <dc:creator>Waqar Razi</dc:creator>
      <dc:date>2009-08-07T16:58:35Z</dc:date>
    </item>
    <item>
      <title>Re: An error message</title>
      <link>https://community.hpe.com/t5/operating-system-linux/an-error-message/m-p/4475648#M37861</link>
      <description>/dev/oracleasm, /proc and /sys are virtual filesystems. &lt;BR /&gt;&lt;BR /&gt;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. &lt;BR /&gt;&lt;BR /&gt;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. &lt;BR /&gt;&lt;BR /&gt;See "man find"; search for "-noleaf" and read the full description of the option from there.&lt;BR /&gt;&lt;BR /&gt;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?&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Sat, 08 Aug 2009 07:28:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/an-error-message/m-p/4475648#M37861</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2009-08-08T07:28:05Z</dc:date>
    </item>
  </channel>
</rss>

