<?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: Mirror breaking in Integrity Servers</title>
    <link>https://community.hpe.com/t5/integrity-servers/mirror-breaking/m-p/4113267#M3045</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I dont think there is any difference for sas disks when it comes to breaking of mirror. &lt;BR /&gt;&lt;BR /&gt;#lvreduce -m 0 /dev/vgxx/lvolx /dev/dsk/cxtxd0&lt;BR /&gt;&lt;BR /&gt;#vgreduce /dev/vgxx /dev/dsk/cxtxd0&lt;BR /&gt;&lt;BR /&gt;But when you need to replace a failed disk the sasmgr comes into picture.&lt;BR /&gt;&lt;BR /&gt;When a disk fails, and a new disk is put into the same bay that the failed disk came out of, the SAS controller knows it is a different disk by its SAS address.  The O/S driver assigns the next available target for the hardware path (viewed with ioscan) and special device file if insf -e is executed.  The sasmgr(1M) command must be used with the â  replace_tgtâ   command to replace the special device file used by LVM with the hardware path to the new disk&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;Prashanth</description>
    <pubDate>Sat, 08 Dec 2007 09:59:37 GMT</pubDate>
    <dc:creator>Prashanth.D.S</dc:creator>
    <dc:date>2007-12-08T09:59:37Z</dc:date>
    <item>
      <title>Mirror breaking</title>
      <link>https://community.hpe.com/t5/integrity-servers/mirror-breaking/m-p/4113264#M3042</link>
      <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;We have a rx3600 server with p400 SAS controller ,configured hardware mirror.Now i want to break that hardware mirror and i want to use that hard disk to another VG.please give me the suggestion how to break  hardware mirroring in SAS controller.</description>
      <pubDate>Fri, 07 Dec 2007 08:50:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/mirror-breaking/m-p/4113264#M3042</guid>
      <dc:creator>Mirror breaking</dc:creator>
      <dc:date>2007-12-07T08:50:54Z</dc:date>
    </item>
    <item>
      <title>Re: Mirror breaking</title>
      <link>https://community.hpe.com/t5/integrity-servers/mirror-breaking/m-p/4113265#M3043</link>
      <description>LVM mirror that you mean ?&lt;BR /&gt;just lvreduce -m 0 /dev/vgxx/lvxx /dev/dsk/cxtxdx, vgreduce /dev/vgxx /dev/dsk/cxtxdx&lt;BR /&gt;&lt;BR /&gt;-yut-</description>
      <pubDate>Fri, 07 Dec 2007 08:55:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/mirror-breaking/m-p/4113265#M3043</guid>
      <dc:creator>yulianto piyut</dc:creator>
      <dc:date>2007-12-07T08:55:01Z</dc:date>
    </item>
    <item>
      <title>Re: Mirror breaking</title>
      <link>https://community.hpe.com/t5/integrity-servers/mirror-breaking/m-p/4113266#M3044</link>
      <description>The P400 is a smartarray controller that can do several RAID configs.&lt;BR /&gt;&lt;BR /&gt;I'm not aware of an option to reduce anything (except spares), but you can delete and recreate.&lt;BR /&gt;&lt;BR /&gt;run "saconfig" without any option to see all possibilities.</description>
      <pubDate>Fri, 07 Dec 2007 11:03:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/mirror-breaking/m-p/4113266#M3044</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2007-12-07T11:03:00Z</dc:date>
    </item>
    <item>
      <title>Re: Mirror breaking</title>
      <link>https://community.hpe.com/t5/integrity-servers/mirror-breaking/m-p/4113267#M3045</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I dont think there is any difference for sas disks when it comes to breaking of mirror. &lt;BR /&gt;&lt;BR /&gt;#lvreduce -m 0 /dev/vgxx/lvolx /dev/dsk/cxtxd0&lt;BR /&gt;&lt;BR /&gt;#vgreduce /dev/vgxx /dev/dsk/cxtxd0&lt;BR /&gt;&lt;BR /&gt;But when you need to replace a failed disk the sasmgr comes into picture.&lt;BR /&gt;&lt;BR /&gt;When a disk fails, and a new disk is put into the same bay that the failed disk came out of, the SAS controller knows it is a different disk by its SAS address.  The O/S driver assigns the next available target for the hardware path (viewed with ioscan) and special device file if insf -e is executed.  The sasmgr(1M) command must be used with the â  replace_tgtâ   command to replace the special device file used by LVM with the hardware path to the new disk&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;Prashanth</description>
      <pubDate>Sat, 08 Dec 2007 09:59:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/mirror-breaking/m-p/4113267#M3045</guid>
      <dc:creator>Prashanth.D.S</dc:creator>
      <dc:date>2007-12-08T09:59:37Z</dc:date>
    </item>
    <item>
      <title>Re: Mirror breaking</title>
      <link>https://community.hpe.com/t5/integrity-servers/mirror-breaking/m-p/4113268#M3046</link>
      <description>IMHO the previous message does not apply.&lt;BR /&gt;&lt;BR /&gt;The Smartarray P400 is a hardware RAID controller and you can  handle it by sautil and saconfig together with the controller device file like /dev/cissx.&lt;BR /&gt;&lt;BR /&gt;Each created logical drive is presented as a single disk device even it is a hardware mirrored RAID1 or RAID 5 or RAID 6 ... or whatever.</description>
      <pubDate>Mon, 10 Dec 2007 06:26:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/mirror-breaking/m-p/4113268#M3046</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2007-12-10T06:26:04Z</dc:date>
    </item>
  </channel>
</rss>

