<?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: domain panic in Operating System - Tru64 Unix</title>
    <link>https://community.hpe.com/t5/operating-system-tru64-unix/domain-panic/m-p/4760562#M15917</link>
    <description>We brought down the system and did fixfdmn and it took lot of time to recover.&lt;BR /&gt;But after that when we connect the disk array to different host, , the domain was coming inactive.&lt;BR /&gt;Hence tried mounting it and then could see our data finally.&lt;BR /&gt;&lt;BR /&gt;Thanx for your help.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 04 Mar 2011 09:55:04 GMT</pubDate>
    <dc:creator>admin1979</dc:creator>
    <dc:date>2011-03-04T09:55:04Z</dc:date>
    <item>
      <title>domain panic</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/domain-panic/m-p/4760558#M15913</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;We have a TRU64 system with "Digital UNIX V4.0F  (Rev. 1229)"&lt;BR /&gt;&lt;BR /&gt;We have came across a domain panic on one of the data domain in our system.&lt;BR /&gt;&lt;BR /&gt;Mar  2 16:16:23 delta vmunix: AdvFS Domain Panic; Domain data_domain Id 0x3f3e069d.00092a23&lt;BR /&gt;Mar  2 16:16:23 delta vmunix: An AdvFS domain panic has occurred due to either a metadata write error or an internal inconsistency. This domain is being ren&lt;BR /&gt;dered inaccessible.&lt;BR /&gt;Mar  2 16:16:23 delta vmunix: Please refer to guidelines in AdvFS Guide to File System Administration regarding what steps to take to recover this domain.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;All the disks are accessible via disklabel.&lt;BR /&gt;But can not mount the disks. Gets a I/O error.&lt;BR /&gt;&lt;BR /&gt;Kindly suggest how I should try filesystem check on this?&lt;BR /&gt;Unfortunately no backup data exists for this domain.  &lt;BR /&gt;&lt;BR /&gt;Thanx,&lt;BR /&gt;admin</description>
      <pubDate>Thu, 03 Mar 2011 06:57:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/domain-panic/m-p/4760558#M15913</guid>
      <dc:creator>admin1979</dc:creator>
      <dc:date>2011-03-03T06:57:38Z</dc:date>
    </item>
    <item>
      <title>Re: domain panic</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/domain-panic/m-p/4760559#M15914</link>
      <description>I tried verify on the data_domain,&lt;BR /&gt;&lt;BR /&gt;delta# ./verify data_domain&lt;BR /&gt;verify: can't get set info for domain 'data_domain'&lt;BR /&gt;verify: error = E_VD_DMNATTR_DIFF (-1079)&lt;BR /&gt;&lt;BR /&gt;+++ Domain verification +++&lt;BR /&gt;&lt;BR /&gt;main: unable to get info for domain 'data_domain'&lt;BR /&gt;    error: -1079, E_VD_DMNATTR_DIFF (-1079)&lt;BR /&gt;&lt;BR /&gt;What does it mean?</description>
      <pubDate>Thu, 03 Mar 2011 08:35:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/domain-panic/m-p/4760559#M15914</guid>
      <dc:creator>admin1979</dc:creator>
      <dc:date>2011-03-03T08:35:50Z</dc:date>
    </item>
    <item>
      <title>Re: domain panic</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/domain-panic/m-p/4760560#M15915</link>
      <description>The man page of advfs_err shows :&lt;BR /&gt;&lt;BR /&gt;(-1079)&lt;BR /&gt;      E_VD_DMNATTR_DIFF&lt;BR /&gt;      Some of the disks listed in fdmns directory for the file domain do not&lt;BR /&gt;      belong to the file domain.  The fdmns directory entry for this file&lt;BR /&gt;      domain is invalid.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;We have recreated the symlinks inside domain as there was a scsi id change after we connected the external disk array to different scsi port in the same host.&lt;BR /&gt;&lt;BR /&gt;Does that affect this behaviour?&lt;BR /&gt;</description>
      <pubDate>Thu, 03 Mar 2011 08:40:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/domain-panic/m-p/4760560#M15915</guid>
      <dc:creator>admin1979</dc:creator>
      <dc:date>2011-03-03T08:40:10Z</dc:date>
    </item>
    <item>
      <title>Re: domain panic</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/domain-panic/m-p/4760561#M15916</link>
      <description>I don't think so,&lt;BR /&gt;&lt;BR /&gt;On the  disk there is "metadata" present that describe to what domains the disk belongs (or previously was part of)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;It may simply mean the new domain name does not match the old domain-name.&lt;BR /&gt;Or I think when recreating the links, you cross linked disks from different old domains into the new domain.&lt;BR /&gt;&lt;BR /&gt;Instead of manually recreating the links you may try to "recover" te domains using advscan&lt;BR /&gt;&lt;BR /&gt;man advscan "You can run the advscan command to automatically rebuild all or part of&lt;BR /&gt;  your /etc/fdmns directory "</description>
      <pubDate>Fri, 04 Mar 2011 09:50:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/domain-panic/m-p/4760561#M15916</guid>
      <dc:creator>Pieter 't Hart</dc:creator>
      <dc:date>2011-03-04T09:50:32Z</dc:date>
    </item>
    <item>
      <title>Re: domain panic</title>
      <link>https://community.hpe.com/t5/operating-system-tru64-unix/domain-panic/m-p/4760562#M15917</link>
      <description>We brought down the system and did fixfdmn and it took lot of time to recover.&lt;BR /&gt;But after that when we connect the disk array to different host, , the domain was coming inactive.&lt;BR /&gt;Hence tried mounting it and then could see our data finally.&lt;BR /&gt;&lt;BR /&gt;Thanx for your help.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 04 Mar 2011 09:55:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-tru64-unix/domain-panic/m-p/4760562#M15917</guid>
      <dc:creator>admin1979</dc:creator>
      <dc:date>2011-03-04T09:55:04Z</dc:date>
    </item>
  </channel>
</rss>

