<?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: Linux filesystem i/o erros (URGENT) in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/linux-filesystem-i-o-erros-urgent/m-p/3817602#M24087</link>
    <description>I haven't done the analysis Stephen has, but if you are seeing path problems on all nodes, it would seem either a switch or MSA1000 controller may have a problem.</description>
    <pubDate>Wed, 05 Jul 2006 23:30:35 GMT</pubDate>
    <dc:creator>Serviceguard for Linux</dc:creator>
    <dc:date>2006-07-05T23:30:35Z</dc:date>
    <item>
      <title>Linux filesystem i/o erros (URGENT)</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-filesystem-i-o-erros-urgent/m-p/3817598#M24083</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Are there any known issues about the following?&lt;BR /&gt;Configuration is a 4 nodes HP ServiceGuard 1.11.15 on SUSE 8.0 (kernel 2.4.21-286-smp) with MSA1000 and SecurePath Workgroup 3.0C SP2.&lt;BR /&gt;&lt;BR /&gt;Jul  5 01:04:27 meditel4 cmcld: Failed to open /opt/cmcluster/run/.cm_start_time: No such file or directory &lt;BR /&gt;Jul  5 01:15:20 meditel4 kernel: ?cpqp: Path hsx_mod-1-0-0-2 Failed (LUN 600805F30016D060A5EB1FEB34000005 Controller P56350D9IPC075 Array 500805F30016D060 HBA 2300-1)&lt;BR /&gt;Jul  5 01:15:20 meditel4 kernel: cpqp: All paths for Target/LUN 0/1 (WWID=600805F30016D060A5EB1FEB34000005) on Controller P56350GX3RT0AT failed&lt;BR /&gt;Jul  5 01:15:20 meditel4 kernel: swspLDPrepFailover Lun has outstanding command &lt;BR /&gt;Jul  5 01:15:23 meditel4 kernel: swspLDDoFailover Going to call swspControllerStart &lt;BR /&gt;Jul  5 01:35:07 meditel4 kernel: hda: packet command error: status=0x51 { DriveReady SeekComplete Error }&lt;BR /&gt;Jul  5 01:35:07 meditel4 kernel: hda: packet command error: error=0x54&lt;BR /&gt;Jul  5 01:35:07 meditel4 kernel:   Error: Illegal request -- (Sense key=0x05)&lt;BR /&gt;Jul  5 01:35:07 meditel4 kernel:   The failed "Start/Stop Unit" packet command was: &lt;BR /&gt;Jul  5 01:35:07 meditel4 kernel: cdrom: open failed.&lt;BR /&gt;Jul  5 01:43:53 meditel4 kernel: SCSI disk error : host 2 channel 0 id 0 lun 1 return code = 10000&lt;BR /&gt;Jul  5 01:43:53 meditel4 kernel:  I/O error: dev 08:12, sector 317704664&lt;BR /&gt;Jul  5 01:43:53 meditel4 kernel: zam-7001: io error in reiserfs_find_entry&lt;BR /&gt;Jul  5 01:43:54 meditel4 kernel: SCSI disk error : host 2 channel 0 id 0 lun 1 return code = 10000&lt;BR /&gt;Jul  5 01:43:54 meditel4 kernel:  I/O error: dev 08:12, sector 317704664&lt;BR /&gt;Jul  5 01:43:54 meditel4 kernel: zam-7001: io error in reiserfs_find_entry&lt;BR /&gt;Jul  5 01:43:54 meditel4 kernel: SCSI disk error : host 2 channel 0 id 0 lun 1 return code = 10000&lt;BR /&gt;Jul  5 01:43:54 meditel4 kernel:  I/O error: dev 08:12, sector 317704664&lt;BR /&gt;Jul  5 01:43:54 meditel4 kernel: zam-7001: io error in reiserfs_find_entry&lt;BR /&gt;Jul  5 01:43:54 meditel4 kernel: SCSI disk error : host 2 channel 0 id 0 lun 1 return code = 10000&lt;BR /&gt;Jul  5 01:43:54 meditel4 kernel:  I/O error: dev 08:12, sector 317704664&lt;BR /&gt;Jul  5 01:43:54 meditel4 kernel: zam-7001: io error in reiserfs_find_entry&lt;BR /&gt;Jul  5 01:43:54 meditel4 kernel: SCSI disk error : host 2 channel 0 id 0 lun 1 return code = 10000&lt;BR /&gt;Jul  5 01:43:54 meditel4 kernel:  I/O error: dev 08:12, sector 317704664&lt;BR /&gt;Jul  5 01:43:54 meditel4 kernel: zam-7001: io error in reiserfs_find_entry&lt;BR /&gt;Jul  5 01:43:54 meditel4 kernel: SCSI disk error : host 2 channel 0 id 0 lun 1 return code = 10000&lt;BR /&gt;Jul  5 01:43:54 meditel4 kernel:  I/O error: dev 08:12, sector 317704664&lt;BR /&gt;Jul  5 01:43:54 meditel4 kernel: zam-7001: io error in reiserfs_find_entry&lt;BR /&gt;Jul  5 01:43:54 meditel4 kernel: SCSI disk error : host 2 channel 0 id 0 lun 1 return code = 10000&lt;BR /&gt;Jul  5 01:43:54 meditel4 kernel:  I/O error: dev 08:12, sector 317704664&lt;BR /&gt;Jul  5 01:43:54 meditel4 kernel: zam-7001: io error in reiserfs_find_entry&lt;BR /&gt;Jul  5 01:43:54 meditel4 kernel: SCSI disk error : host 2 channel 0 id 0 lun 1 return code = 10000&lt;BR /&gt;Jul  5 01:43:54 meditel4 kernel:  I/O error: dev 08:12, sector 317704664&lt;BR /&gt;Jul  5 01:43:54 meditel4 kernel: zam-7001: io error in reiserfs_find_entry&lt;BR /&gt;Jul  5 01:43:57 meditel4 kernel: ?cpqp: Path hsx_mod-0-0-0-2 Failed (LUN 600805F30016D060A5EB1FEB34000005 Controller P56350GX3RT0AT Array 500805F30016D060 HBA 2300-0)&lt;BR /&gt;Jul  5 01:43:57 meditel4 kernel: cpqp: All paths for Target/LUN 0/1 (WWID=600805F30016D060A5EB1FEB34000005) on Controller P56350D9IPC075 failed&lt;BR /&gt;Jul  5 01:43:57 meditel4 kernel: swspLDDoFailover Going to call swspControllerStart &lt;BR /&gt;Jul  5 01:58:51 meditel4 cmcld: Timed out node meditel1. It may have failed. &lt;BR /&gt;Jul  5 02:00:42 meditel4 kernel: ?cpqp: Path hsx_mod-1-0-0-1 Failed (LUN 600805F30016D060A6DB0FD3E9280004 Controller P56350D9IPC075 Array 500805F30016D060 HBA 2300-1)&lt;BR /&gt;Jul  5 02:00:42 meditel4 kernel: cpqp: All paths for Target/LUN 0/0 (WWID=600805F30016D060A6DB0FD3E9280004) on Controller P56350GX3RT0AT failed&lt;BR /&gt;Jul  5 02:00:42 meditel4 kernel: swspLDDoFailover Going to call swspControllerStart &lt;BR /&gt;Jul  5 02:09:08 meditel4 kernel: ?cpqp: Path hsx_mod-0-0-0-1 Failed (LUN 600805F30016D060A6DB0FD3E9280004 Controller P56350GX3RT0AT Array 500805F30016D060 HBA 2300-0)&lt;BR /&gt;Jul  5 02:09:08 meditel4 kernel: cpqp: All paths for Target/LUN 0/0 (WWID=600805F30016D060A6DB0FD3E9280004) on Controller P56350D9IPC075 failed&lt;BR /&gt;Jul  5 02:09:08 meditel4 kernel: swspLDDoFailover Going to call swspControllerStart &lt;BR /&gt;Jul  5 02:10:59 meditel4 kernel: ?cpqp: Path hsx_mod-1-0-0-1 Failed (LUN 600805F30016D060A6DB0FD3E9280004 Controller P56350D9IPC075 Array 500805F30016D060 HBA 2300-1)&lt;BR /&gt;Jul  5 02:10:59 meditel4 kernel: cpqp: All paths for Target/LUN 0/0 (WWID=600805F30016D060A6DB0FD3E9280004) on Controller P56350GX3RT0AT failed&lt;BR /&gt;Jul  5 02:10:59 meditel4 kernel: swspLDDoFailover Going to call swspControllerStart &lt;BR /&gt;Jul  5 02:18:15 meditel4 cmcld: Timed out node meditel2. It may have failed. &lt;BR /&gt;Jul  5 02:22:53 meditel4 kernel: ?cpqp: Path hsx_mod-0-0-0-1 Failed (LUN 600805F30016D060A6DB0FD3E9280004 Controller P56350GX3RT0AT Array 500805F30016D060 HBA 2300-0)&lt;BR /&gt;Jul  5 02:22:53 meditel4 kernel: cpqp: All paths for Target/LUN 0/0 (WWID=600805F30016D060A6DB0FD3E9280004) on Controller P56350D9IPC075 failed&lt;BR /&gt;Jul  5 02:22:53 meditel4 kernel: swspLDDoFailover Going to call swspControllerStart &lt;BR /&gt;Jul  5 02:23:07 meditel4 kernel: ?cpqp: Path hsx_mod-0-0-0-2 Failed (LUN 600805F30016D060A5EB1FEB34000005 Controller P56350GX3RT0AT Array 500805F30016D060 HBA 2300-0)&lt;BR /&gt;Jul  5 02:23:07 meditel4 kernel: cpqp: All paths for Target/LUN 0/1 (WWID=600805F30016D060A5EB1FEB34000005) on Controller P56350D9IPC075 failed&lt;BR /&gt;Jul  5 02:23:07 meditel4 kernel: swspLDDoFailover Going to call swspControllerStart &lt;BR /&gt;Jul  5 02:24:41 meditel4 kernel: ?cpqp: Path hsx_mod-1-0-0-1 Failed (LUN 600805F30016D060A6DB0FD3E9280004 Controller P56350D9IPC075 Array 500805F30016D060 HBA 2300-1)&lt;BR /&gt;Jul  5 02:24:41 meditel4 kernel: cpqp: All paths for Target/LUN 0/0 (WWID=600805F30016D060A6DB0FD3E9280004) on Controller P56350GX3RT0AT failed&lt;BR /&gt;Jul  5 02:24:41 meditel4 kernel: swspLDDoFailover Going to call swspControllerStart &lt;BR /&gt;Jul  5 02:39:44 meditel4 cmclconfd[22707]: Failed to get main daemon to connect out &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Wed, 05 Jul 2006 06:35:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-filesystem-i-o-erros-urgent/m-p/3817598#M24083</guid>
      <dc:creator>Benoît</dc:creator>
      <dc:date>2006-07-05T06:35:22Z</dc:date>
    </item>
    <item>
      <title>Re: Linux filesystem i/o erros (URGENT)</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-filesystem-i-o-erros-urgent/m-p/3817599#M24084</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Seems your alternate path, provided by securepath is not working.&lt;BR /&gt;&lt;BR /&gt;Could be the connection or the disk itself thats the problem.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 05 Jul 2006 08:06:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-filesystem-i-o-erros-urgent/m-p/3817599#M24084</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-07-05T08:06:29Z</dc:date>
    </item>
    <item>
      <title>Re: Linux filesystem i/o erros (URGENT)</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-filesystem-i-o-erros-urgent/m-p/3817600#M24085</link>
      <description>Hi Steven,&lt;BR /&gt;&lt;BR /&gt;Thanks for replying so fast.&lt;BR /&gt;&lt;BR /&gt;I have the same kind of problem on my 4 nodes.&lt;BR /&gt;&lt;BR /&gt;Do you it could be a problem on one of the disks of the MSA or on a LUN?&lt;BR /&gt;I don't have any errors on the MSA.&lt;BR /&gt;&lt;BR /&gt;Where should investigate?</description>
      <pubDate>Wed, 05 Jul 2006 08:51:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-filesystem-i-o-erros-urgent/m-p/3817600#M24085</guid>
      <dc:creator>Benoît</dc:creator>
      <dc:date>2006-07-05T08:51:01Z</dc:date>
    </item>
    <item>
      <title>Re: Linux filesystem i/o erros (URGENT)</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-filesystem-i-o-erros-urgent/m-p/3817601#M24086</link>
      <description>Could it be a problem from QLA Fibre Channel Driver? (qla2x00src-v7.05.00)</description>
      <pubDate>Wed, 05 Jul 2006 08:55:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-filesystem-i-o-erros-urgent/m-p/3817601#M24086</guid>
      <dc:creator>Benoît</dc:creator>
      <dc:date>2006-07-05T08:55:47Z</dc:date>
    </item>
    <item>
      <title>Re: Linux filesystem i/o erros (URGENT)</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-filesystem-i-o-erros-urgent/m-p/3817602#M24087</link>
      <description>I haven't done the analysis Stephen has, but if you are seeing path problems on all nodes, it would seem either a switch or MSA1000 controller may have a problem.</description>
      <pubDate>Wed, 05 Jul 2006 23:30:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-filesystem-i-o-erros-urgent/m-p/3817602#M24087</guid>
      <dc:creator>Serviceguard for Linux</dc:creator>
      <dc:date>2006-07-05T23:30:35Z</dc:date>
    </item>
    <item>
      <title>Re: Linux filesystem i/o erros (URGENT)</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-filesystem-i-o-erros-urgent/m-p/3817603#M24088</link>
      <description>I agree with Serviceguard. These messages are typical of a problem with storage.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 06 Jul 2006 01:03:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-filesystem-i-o-erros-urgent/m-p/3817603#M24088</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-07-06T01:03:49Z</dc:date>
    </item>
  </channel>
</rss>

