<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>System Adm &#187; disk</title>
	<atom:link href="http://www.system.adm.br/tag/disk/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.system.adm.br</link>
	<description>Some IT Tips (Linux, Unix, HP-UX, AIX, Solaris, etc).</description>
	<lastBuildDate>Wed, 30 Nov 2011 17:59:40 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Identify PV device in HP-UX 11.31</title>
		<link>http://www.system.adm.br/2011/09/identify-pv-device-in-hp-ux-11-31/</link>
		<comments>http://www.system.adm.br/2011/09/identify-pv-device-in-hp-ux-11-31/#comments</comments>
		<pubDate>Thu, 08 Sep 2011 18:44:30 +0000</pubDate>
		<dc:creator>Lincoln Zuljewic Silva</dc:creator>
				<category><![CDATA[HP-UX]]></category>
		<category><![CDATA[disk]]></category>
		<category><![CDATA[ioscan]]></category>
		<category><![CDATA[storage]]></category>

		<guid isPermaLink="false">http://www.system.adm.br/?p=379</guid>
		<description><![CDATA[In HP-UX 11.31, LVM doesn’t use “ctd’ (ie: /dev/rdsk/c2t1d0), but DSF to balance the throughput between many device paths., so if you need identify what physical device represent that logical device, you can use ioscan, for example: server@root:/root # vgdisplay -v vg00 --- Volume groups --- VG Name                     /dev/vg00 VG Write Access             read/write VG Status                   [...]]]></description>
			<content:encoded><![CDATA[<p>In HP-UX 11.31, LVM doesn’t use “ctd’ (ie: /dev/rdsk/c2t1d0), but DSF to balance the throughput between many device paths., so if you need identify what physical device represent that logical device, you can use ioscan, for example:<br />
<code><span style="font-size: 12px;"><br />
server@root:/root # vgdisplay -v vg00<br />
--- Volume groups ---<br />
VG Name                     /dev/vg00<br />
VG Write Access             read/write<br />
VG Status                   available<br />
Max LV                      255<br />
Cur LV                      12<br />
Open LV                     12<br />
Max PV                      16<br />
Cur PV                      1<br />
Act PV                      1<br />
Max PE per PV               4385<br />
VGDA                        2<br />
PE Size (Mbytes)            16<br />
Total PE                    4375<br />
Alloc PE                    3998<br />
Free PE                     377<br />
Total PVG                   0<br />
Total Spare PVs             0<br />
Total Spare PVs in use      0<br />
VG Version                  1.0<br />
VG Max Size                 1122560m<br />
VG Max Extents              70160</span></code><br />
<code><span style="font-size: 12px;"><br />
--- Logical volumes ---<br />
LV Name                     /dev/vg00/lvol1<br />
LV Status                   available/syncd<br />
LV Size (Mbytes)            2000<br />
Current LE                  125<br />
Allocated PE                125<br />
Used PV                     1</span></code><br />
<code><span style="font-size: 12px;"><br />
LV Name                     /dev/vg00/lvol2<br />
LV Status                   available/syncd<br />
LV Size (Mbytes)            16384<br />
Current LE                  1024<br />
Allocated PE                1024<br />
Used PV                     1<br />
<code><span style="font-size: 12px;"><br />
(...)<br />
</span></code></span></code><code><span style="font-size: 12px;"><code><span style="font-size: 12px;"><code><span style="font-size: 12px;"><code><span style="font-size: 12px;"><code><span style="font-size: 12px;"><code><span style="font-size: 12px;"><code><span style="font-size: 12px;"><code><span style="font-size: 12px;"><code><span style="font-size: 12px;"><br />
LV Name                     /dev/vg00/lvol12<br />
LV Status                   available/syncd<br />
LV Size (Mbytes)            5120<br />
Current LE                  320<br />
Allocated PE                320<br />
Used PV                     1<br />
<code><span style="font-size: 12px;"><br />
--- Physical volumes ---<br />
PV Name                     <span style="color: #ff0000;">/dev/disk/disk4</span><br />
PV Status                   available<br />
Total PE                    4375<br />
Free PE                     377<br />
Autoswitch                  On<br />
Proactive Polling           On</span></code></span></code></span></code></span></code></span></code></span></code></span></code></span></code></span></code></span></code></p>
<p>Note that the pv name is “disk4”, not c2t1d3.</p>
<p>With ioscan you can reverse map it:<br />
<code><span style="font-size: 12px;"><br />
server@root:/root # ioscan -m dsf<br />
Persistent DSF           Legacy DSF(s)<br />
========================================<br />
/dev/rdisk/disk3         /dev/rdsk/c2t1d0<br />
<span style="color: #ff0000;">/dev/rdisk/disk4         /dev/rdsk/c2t0d0</span><br />
/dev/rdisk/disk5         /dev/rdsk/c0t0d0<br />
</span></code></p>
<p>Now we know that the &#8220;disk4&#8243; is the physical disk located in 12/0/1/1/0.0.0<br />
<code><span style="font-size: 12px;"><br />
root@brux0044:/root # ioscan -fnC disk<br />
Class I H/W Path Driver S/W State H/W Type Description<br />
========================================================================<br />
<span style="color: #ff0000;">disk 1298 12/0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 73.4GMAP3735NC</span><br />
<span style="color: #ff0000;">                         /dev/dsk/c2t0d0 /dev/rdsk/c2t0d0</span></p>
<p></span></code></p>
<p><code></code></p>
]]></content:encoded>
			<wfw:commentRss>http://www.system.adm.br/2011/09/identify-pv-device-in-hp-ux-11-31/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Updating partition table in Linux</title>
		<link>http://www.system.adm.br/2010/03/updating-partition-table-in-linux/</link>
		<comments>http://www.system.adm.br/2010/03/updating-partition-table-in-linux/#comments</comments>
		<pubDate>Mon, 15 Mar 2010 14:53:16 +0000</pubDate>
		<dc:creator>Lincoln Zuljewic Silva</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[admin]]></category>
		<category><![CDATA[disk]]></category>
		<category><![CDATA[hardware]]></category>

		<guid isPermaLink="false">http://www.system.adm.br/?p=232</guid>
		<description><![CDATA[When you use the &#34;fdisk&#34; to handle the partitions of a disk, depending on the disc, the &#34;fdisk&#34; will bring the following message: WARNING: Re-reading the partition table failed with error 22: Invalid argument. The kernel still uses the old table. The new table will be used at the next reboot. Syncing disks. No, you [...]]]></description>
			<content:encoded><![CDATA[<p>When you use the &quot;fdisk&quot; to handle the partitions of a disk, depending on the disc, the &quot;fdisk&quot; will bring the following message:</p>
<p><span style="font-size: 12px;"><code>WARNING: Re-reading the partition table failed with error 22: Invalid argument.<br />
	The kernel still uses the old table.<br />
	The new table will be used at the next reboot.<br />
	Syncing disks.</code></span></p>
<p>	No, you do not have to restart the server for the changes are applied, simply use the following command (example):<br />
	<span style="font-size: 12px;"><code>kpartx -a /dev/sda</code></span></p>
<p>	This will re-read the partition table on /dev/sda and create the mapping of the system partitions (/dev/sda1, /dev/sda2, etc).</p>
]]></content:encoded>
			<wfw:commentRss>http://www.system.adm.br/2010/03/updating-partition-table-in-linux/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

