<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments for Weblog for Thomas S. Iversen</title>
	<atom:link href="http://zensonic.dk/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://zensonic.dk</link>
	<description>Life, Universe and everything</description>
	<lastBuildDate>Fri, 13 Aug 2010 04:31:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>Comment on Non-HP harddrives in an HP MSA20 by zensonic</title>
		<link>http://zensonic.dk/?p=96&#038;cpage=1#comment-18005</link>
		<dc:creator>zensonic</dc:creator>
		<pubDate>Fri, 13 Aug 2010 04:31:26 +0000</pubDate>
		<guid isPermaLink="false">http://zensonic.dk/?p=96#comment-18005</guid>
		<description>You can&#039;t. At least not from the MSA20 side of things. It has a stupid limitation about logical volumes not being larger than 2TB. So you have to slice the disks into LUNs of up to 2TB in size in the MSA and combine them into a single LV on the host. Annoying to say the least. 

Personally I took another approach at the customer site. Their data means everything to them, so redundancy and raidlevels are what really matters.

=&gt; ctrl ch=data show config

MSA20 in data                        (sn: PAAACABMQUEFDA, csn: E03KMLJ18F     )

   array A (SATA, Unused Space: 103320 MB)

      logicaldrive 1 (1.6 TB, RAID 6 (ADG), OK)
      logicaldrive 2 (1.6 TB, RAID 6 (ADG), OK)
      logicaldrive 3 (1.6 TB, RAID 6 (ADG), OK)
      logicaldrive 4 (1.6 TB, RAID 6 (ADG), OK)
      logicaldrive 5 (1.6 TB, RAID 6 (ADG), OK)

      physicaldrive 1:1 (box 1:bay 1, SATA, 1000.2 GB, OK)
      physicaldrive 1:2 (box 1:bay 2, SATA, 1000.2 GB, OK)
      physicaldrive 1:3 (box 1:bay 3, SATA, 1000.2 GB, OK)
      physicaldrive 1:4 (box 1:bay 4, SATA, 1000.2 GB, OK)
      physicaldrive 1:5 (box 1:bay 5, SATA, 1000.2 GB, OK)
      physicaldrive 1:6 (box 1:bay 6, SATA, 1000.2 GB, OK)
      physicaldrive 1:7 (box 1:bay 7, SATA, 1000.2 GB, OK)
      physicaldrive 1:8 (box 1:bay 8, SATA, 1000.2 GB, OK)
      physicaldrive 1:9 (box 1:bay 9, SATA, 1000.2 GB, OK)
      physicaldrive 1:10 (box 1:bay 10, SATA, 1000.2 GB, OK)
      physicaldrive 1:11 (box 1:bay 11, SATA, 1000.2 GB, OK)
      physicaldrive 1:12 (box 1:bay 12, SATA, 1000.2 GB, OK, spare)

So raid-6, with a spare, that is 3 disks out of 12 is for redundancy purposes. The last 9 disks are sliced into 1.6TB LUNs and presented to the host. On the host side I use LVM to combine it directly. In a JBOD setup, it would use the md driver in linux. In my end:

    Finding volume group &quot;alt&quot;
  --- Volume group ---
  VG Name               alt
  System ID
  Format                lvm2
  Metadata Areas        5
  Metadata Sequence No  6
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                3
  Open LV               3
  Max PV                0
  Cur PV                5
  Act PV                5
  VG Size               8,11 TB
  PE Size               4,00 MB
  Total PE              2125000
  Alloc PE / Size       2073800 / 7,91 TB
  Free  PE / Size       51200 / 200,00 GB
  VG UUID               HChKy6-EKi7-uRzo-pFOi-uI9c-Qxn7-aAXJbU

  --- Logical volume ---
  LV Name                /dev/alt/data
  VG Name                alt
  LV UUID                9aeh2b-JG95-aA1F-SL35-iTlr-4ZUZ-k9yn3c
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                2,00 TB
  Current LE             524288
  Segments               2
  Allocation             inherit
  Read ahead sectors     0
  Block device           253:0

  --- Logical volume ---
  LV Name                /dev/alt/permanent_to_tape
  VG Name                alt
  LV UUID                BW3WMN-27Lu-GGH5-2Cox-eJuQ-rpQT-E8jYEc
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                200,00 GB
  Current LE             51200
  Segments               1
  Allocation             inherit
  Read ahead sectors     0
  Block device           253:1

  --- Logical volume ---
  LV Name                /dev/alt/home
  VG Name                alt
  LV UUID                F8m989-K1UI-ypiA-TLa8-T9nK-kl21-reLhlP
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                5,72 TB
  Current LE             1498312
  Segments               4
  Allocation             inherit
  Read ahead sectors     0
  Block device           253:2

  --- Physical volumes ---
  PV Name               /dev/cciss/c0d5
  PV UUID               eMkVxm-A792-ccvU-T8Kh-XfpB-yLEL-ZNZuPu
  PV Status             allocatable
  Total PE / Free PE    425000 / 0

  PV Name               /dev/cciss/c0d6
  PV UUID               qMFPjc-CQBf-tYa3-DeOF-1Q8m-5f0B-nZmRUf
  PV Status             allocatable
  Total PE / Free PE    425000 / 51200

  PV Name               /dev/cciss/c0d7
  PV UUID               ImjS25-M24u-o0pK-2Uss-2YMm-2RjY-xl5V4s
  PV Status             allocatable
  Total PE / Free PE    425000 / 0

  PV Name               /dev/cciss/c0d8
  PV UUID               bn9k8V-1ZVu-YvzT-B65R-UhzN-Hj8k-sKvwyQ
  PV Status             allocatable
  Total PE / Free PE    425000 / 0

  PV Name               /dev/cciss/c0d9
  PV UUID               vwCnyZ-qZ3G-sERD-mKr5-zFwP-SbNo-SHC6hY
  PV Status             allocatable
  Total PE / Free PE    425000 / 0

Hope you got some ideas on how to proceed. The short answer: the MSA20 is limited. You have to work around a 2TB LV limit. But hey, it is cheap storage ;-)</description>
		<content:encoded><![CDATA[<p>You can&#8217;t. At least not from the MSA20 side of things. It has a stupid limitation about logical volumes not being larger than 2TB. So you have to slice the disks into LUNs of up to 2TB in size in the MSA and combine them into a single LV on the host. Annoying to say the least. </p>
<p>Personally I took another approach at the customer site. Their data means everything to them, so redundancy and raidlevels are what really matters.</p>
<p>=> ctrl ch=data show config</p>
<p>MSA20 in data                        (sn: PAAACABMQUEFDA, csn: E03KMLJ18F     )</p>
<p>   array A (SATA, Unused Space: 103320 MB)</p>
<p>      logicaldrive 1 (1.6 TB, RAID 6 (ADG), OK)<br />
      logicaldrive 2 (1.6 TB, RAID 6 (ADG), OK)<br />
      logicaldrive 3 (1.6 TB, RAID 6 (ADG), OK)<br />
      logicaldrive 4 (1.6 TB, RAID 6 (ADG), OK)<br />
      logicaldrive 5 (1.6 TB, RAID 6 (ADG), OK)</p>
<p>      physicaldrive 1:1 (box 1:bay 1, SATA, 1000.2 GB, OK)<br />
      physicaldrive 1:2 (box 1:bay 2, SATA, 1000.2 GB, OK)<br />
      physicaldrive 1:3 (box 1:bay 3, SATA, 1000.2 GB, OK)<br />
      physicaldrive 1:4 (box 1:bay 4, SATA, 1000.2 GB, OK)<br />
      physicaldrive 1:5 (box 1:bay 5, SATA, 1000.2 GB, OK)<br />
      physicaldrive 1:6 (box 1:bay 6, SATA, 1000.2 GB, OK)<br />
      physicaldrive 1:7 (box 1:bay 7, SATA, 1000.2 GB, OK)<br />
      physicaldrive 1:8 (box 1:bay 8, SATA, 1000.2 GB, OK)<br />
      physicaldrive 1:9 (box 1:bay 9, SATA, 1000.2 GB, OK)<br />
      physicaldrive 1:10 (box 1:bay 10, SATA, 1000.2 GB, OK)<br />
      physicaldrive 1:11 (box 1:bay 11, SATA, 1000.2 GB, OK)<br />
      physicaldrive 1:12 (box 1:bay 12, SATA, 1000.2 GB, OK, spare)</p>
<p>So raid-6, with a spare, that is 3 disks out of 12 is for redundancy purposes. The last 9 disks are sliced into 1.6TB LUNs and presented to the host. On the host side I use LVM to combine it directly. In a JBOD setup, it would use the md driver in linux. In my end:</p>
<p>    Finding volume group &#8220;alt&#8221;<br />
  &#8212; Volume group &#8212;<br />
  VG Name               alt<br />
  System ID<br />
  Format                lvm2<br />
  Metadata Areas        5<br />
  Metadata Sequence No  6<br />
  VG Access             read/write<br />
  VG Status             resizable<br />
  MAX LV                0<br />
  Cur LV                3<br />
  Open LV               3<br />
  Max PV                0<br />
  Cur PV                5<br />
  Act PV                5<br />
  VG Size               8,11 TB<br />
  PE Size               4,00 MB<br />
  Total PE              2125000<br />
  Alloc PE / Size       2073800 / 7,91 TB<br />
  Free  PE / Size       51200 / 200,00 GB<br />
  VG UUID               HChKy6-EKi7-uRzo-pFOi-uI9c-Qxn7-aAXJbU</p>
<p>  &#8212; Logical volume &#8212;<br />
  LV Name                /dev/alt/data<br />
  VG Name                alt<br />
  LV UUID                9aeh2b-JG95-aA1F-SL35-iTlr-4ZUZ-k9yn3c<br />
  LV Write Access        read/write<br />
  LV Status              available<br />
  # open                 1<br />
  LV Size                2,00 TB<br />
  Current LE             524288<br />
  Segments               2<br />
  Allocation             inherit<br />
  Read ahead sectors     0<br />
  Block device           253:0</p>
<p>  &#8212; Logical volume &#8212;<br />
  LV Name                /dev/alt/permanent_to_tape<br />
  VG Name                alt<br />
  LV UUID                BW3WMN-27Lu-GGH5-2Cox-eJuQ-rpQT-E8jYEc<br />
  LV Write Access        read/write<br />
  LV Status              available<br />
  # open                 1<br />
  LV Size                200,00 GB<br />
  Current LE             51200<br />
  Segments               1<br />
  Allocation             inherit<br />
  Read ahead sectors     0<br />
  Block device           253:1</p>
<p>  &#8212; Logical volume &#8212;<br />
  LV Name                /dev/alt/home<br />
  VG Name                alt<br />
  LV UUID                F8m989-K1UI-ypiA-TLa8-T9nK-kl21-reLhlP<br />
  LV Write Access        read/write<br />
  LV Status              available<br />
  # open                 1<br />
  LV Size                5,72 TB<br />
  Current LE             1498312<br />
  Segments               4<br />
  Allocation             inherit<br />
  Read ahead sectors     0<br />
  Block device           253:2</p>
<p>  &#8212; Physical volumes &#8212;<br />
  PV Name               /dev/cciss/c0d5<br />
  PV UUID               eMkVxm-A792-ccvU-T8Kh-XfpB-yLEL-ZNZuPu<br />
  PV Status             allocatable<br />
  Total PE / Free PE    425000 / 0</p>
<p>  PV Name               /dev/cciss/c0d6<br />
  PV UUID               qMFPjc-CQBf-tYa3-DeOF-1Q8m-5f0B-nZmRUf<br />
  PV Status             allocatable<br />
  Total PE / Free PE    425000 / 51200</p>
<p>  PV Name               /dev/cciss/c0d7<br />
  PV UUID               ImjS25-M24u-o0pK-2Uss-2YMm-2RjY-xl5V4s<br />
  PV Status             allocatable<br />
  Total PE / Free PE    425000 / 0</p>
<p>  PV Name               /dev/cciss/c0d8<br />
  PV UUID               bn9k8V-1ZVu-YvzT-B65R-UhzN-Hj8k-sKvwyQ<br />
  PV Status             allocatable<br />
  Total PE / Free PE    425000 / 0</p>
<p>  PV Name               /dev/cciss/c0d9<br />
  PV UUID               vwCnyZ-qZ3G-sERD-mKr5-zFwP-SbNo-SHC6hY<br />
  PV Status             allocatable<br />
  Total PE / Free PE    425000 / 0</p>
<p>Hope you got some ideas on how to proceed. The short answer: the MSA20 is limited. You have to work around a 2TB LV limit. But hey, it is cheap storage <img src='http://zensonic.dk/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Non-HP harddrives in an HP MSA20 by Stephen Wagner</title>
		<link>http://zensonic.dk/?p=96&#038;cpage=1#comment-18000</link>
		<dc:creator>Stephen Wagner</dc:creator>
		<pubDate>Fri, 13 Aug 2010 00:17:31 +0000</pubDate>
		<guid isPermaLink="false">http://zensonic.dk/?p=96#comment-18000</guid>
		<description>Just curious, have you done any other tweeks or tricks on this MSA20 unit?

I&#039;m still trying to figure out how to get the host OS to see the disks as JBOD. I&#039;m still choked about the logical partition limit!</description>
		<content:encoded><![CDATA[<p>Just curious, have you done any other tweeks or tricks on this MSA20 unit?</p>
<p>I&#8217;m still trying to figure out how to get the host OS to see the disks as JBOD. I&#8217;m still choked about the logical partition limit!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Portforwarding on a zyxel device using the ZynOS cli by Dale Jackson</title>
		<link>http://zensonic.dk/?p=106&#038;cpage=1#comment-17987</link>
		<dc:creator>Dale Jackson</dc:creator>
		<pubDate>Thu, 12 Aug 2010 11:35:51 +0000</pubDate>
		<guid isPermaLink="false">http://zensonic.dk/?p=106#comment-17987</guid>
		<description>Brilliant. Thanks</description>
		<content:encoded><![CDATA[<p>Brilliant. Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How to use a broken IBM Thinkpad T43 for something useful using puppy linux. by zensonic</title>
		<link>http://zensonic.dk/?p=153&#038;cpage=1#comment-17625</link>
		<dc:creator>zensonic</dc:creator>
		<pubDate>Mon, 26 Jul 2010 09:36:09 +0000</pubDate>
		<guid isPermaLink="false">http://zensonic.dk/?p=153#comment-17625</guid>
		<description>2. I lost interest in it when I was done. Turned out, that it was the &lt;strong&gt;process&lt;/strong&gt; that was interesting. Surprised me as well ;-)</description>
		<content:encoded><![CDATA[<p>2. I lost interest in it when I was done. Turned out, that it was the <strong>process</strong> that was interesting. Surprised me as well <img src='http://zensonic.dk/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How to use a broken IBM Thinkpad T43 for something useful using puppy linux. by Rasmus</title>
		<link>http://zensonic.dk/?p=153&#038;cpage=1#comment-17624</link>
		<dc:creator>Rasmus</dc:creator>
		<pubDate>Mon, 26 Jul 2010 09:32:36 +0000</pubDate>
		<guid isPermaLink="false">http://zensonic.dk/?p=153#comment-17624</guid>
		<description>Very nice guide.

So now the question remains:

1. Will you use it?
or
2. Will it be stowed away on top of a wardrobe?</description>
		<content:encoded><![CDATA[<p>Very nice guide.</p>
<p>So now the question remains:</p>
<p>1. Will you use it?<br />
or<br />
2. Will it be stowed away on top of a wardrobe?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Linux (ubuntu Karmic Koala) on HP Elitebook 2530p by zensonic</title>
		<link>http://zensonic.dk/?p=47&#038;cpage=1#comment-16530</link>
		<dc:creator>zensonic</dc:creator>
		<pubDate>Wed, 19 May 2010 17:59:42 +0000</pubDate>
		<guid isPermaLink="false">http://zensonic.dk/?p=47#comment-16530</guid>
		<description>I no longer have the laptop, but it did. I only tested it briefly using a KDE application of some sort.</description>
		<content:encoded><![CDATA[<p>I no longer have the laptop, but it did. I only tested it briefly using a KDE application of some sort.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Linux (ubuntu Karmic Koala) on HP Elitebook 2530p by dani</title>
		<link>http://zensonic.dk/?p=47&#038;cpage=1#comment-16485</link>
		<dc:creator>dani</dc:creator>
		<pubDate>Wed, 12 May 2010 15:16:54 +0000</pubDate>
		<guid isPermaLink="false">http://zensonic.dk/?p=47#comment-16485</guid>
		<description>Does the webcam works????If it does how??</description>
		<content:encoded><![CDATA[<p>Does the webcam works????If it does how??</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Updating system firmware on an IBM Thinkpad T43 using pxeboot by Søren</title>
		<link>http://zensonic.dk/?p=120&#038;cpage=1#comment-16440</link>
		<dc:creator>Søren</dc:creator>
		<pubDate>Sat, 01 May 2010 05:56:44 +0000</pubDate>
		<guid isPermaLink="false">http://zensonic.dk/?p=120#comment-16440</guid>
		<description>PXE is very useful. In my new company we use this stuff to do imaging and installation: http://ping.windowsdream.com/
Simple setup, free, and flexible</description>
		<content:encoded><![CDATA[<p>PXE is very useful. In my new company we use this stuff to do imaging and installation: <a href="http://ping.windowsdream.com/" rel="nofollow">http://ping.windowsdream.com/</a><br />
Simple setup, free, and flexible</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Here we go again&#8230; by Another take on no coke. &#171; Weblog for Thomas S. Iversen</title>
		<link>http://zensonic.dk/?p=24&#038;cpage=1#comment-16417</link>
		<dc:creator>Another take on no coke. &#171; Weblog for Thomas S. Iversen</dc:creator>
		<pubDate>Sun, 22 Nov 2009 20:11:02 +0000</pubDate>
		<guid isPermaLink="false">http://zensonic.dk/?p=24#comment-16417</guid>
		<description>[...] have tried before. In 2004 I had a period of 1.5 year where I did not drink coke. I tried again in February 2008, but that did not last that long. Now I am at it again. I would really like to quit that habit. I [...]</description>
		<content:encoded><![CDATA[<p>[...] have tried before. In 2004 I had a period of 1.5 year where I did not drink coke. I tried again in February 2008, but that did not last that long. Now I am at it again. I would really like to quit that habit. I [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Enabling 32MB memory on the linksys WRT54G router (version 2.2 XH only!) by Linux (ubuntu Karmic Koala) on HP Elitebook 2530p &#171; Weblog for Thomas S. Iversen</title>
		<link>http://zensonic.dk/?p=19&#038;cpage=1#comment-16416</link>
		<dc:creator>Linux (ubuntu Karmic Koala) on HP Elitebook 2530p &#171; Weblog for Thomas S. Iversen</dc:creator>
		<pubDate>Sat, 24 Oct 2009 21:56:23 +0000</pubDate>
		<guid isPermaLink="false">http://zensonic.dk/?p=19#comment-16416</guid>
		<description>[...] the wireless would not work with my wrt54g. It worked with other wifi hotspots. Symptoms were that the laptop could not a dhcplease from the [...]</description>
		<content:encoded><![CDATA[<p>[...] the wireless would not work with my wrt54g. It worked with other wifi hotspots. Symptoms were that the laptop could not a dhcplease from the [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
