<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
<channel>
<title>Openfiler Forums : Openfiler : Volume Management</title>
<link>https://forums.openfiler.com</link>
<description> Openfiler Forums</description>
<language>en</language>
<docs>http://backend.userland.com/rss</docs>
<item>
<title>Snapshot GUI issues in Openfiler : Volume Management</title>
<link>https://forums.openfiler.com/viewtopic.php?pid=22310#22310</link>
<guid isPermaLink="false">22310@https://forums.openfiler.com</guid>
<description>Topic: Snapshot GUI issues

Message: Sorry to resurrect an old post but this appears to still be an issue, at least in the case of volume names with hyphensWhen there's a hyphen in the volume name, the /dev/mapper file gets a double-hyphen instead, so when the snapshot management page looks for the device/dev/mapper/${VGNAME}-of.snapshot.${LVNAME}.${SNAPNAME}, it doesn't find it, and ignores it in the listIn my case, and this is specifically for hyphens in the volumename, not the snapshot name or the volume group name, I worked around it by changing /opt/openfiler/volumes_snapshots.html around line 1130 from
Code:   1127                 for ($i = 0; $i &#60; count($snapshots_lvname); $i++)
   1128                         if (($snapshots_lvname[$i] == $volume) &#38;&#38; ($snapshots_vgname[$i] == $vgname))
   1129                         {
   1130                                 if ($GLOBALS[&#34;lvm_version&#34;] == 1)
   1131                                         $snapshot_dev = &#34;/dev/&#34; . $snapshots_vgname[$i] . &#34;/of.snapshot.&#34; . $snapshots_lvname[$i] . &#34;.&#34; . $snapshots_id[$i];
   1132                                 else
   1133                                         $snapshot_dev = &#34;/dev/mapper/&#34; . $snapshots_vgname[$i] . &#34;-of.snapshot.&#34; . $snapshots_lvname[$i] . &#34;.&#34; . $snapshots_id[$i];
   1134
   1135                                 $snapshot_symlink_dev = &#34;/dev/&#34; . $snapshots_vgname[$i] . &#34;/of.snapshot.&#34; . $snapshots_lvname[$i] . &#34;.&#34; . $snapshots_
to something like
Code:   1127                 for ($i = 0; $i &#60; count($snapshots_lvname); $i++)
   1128                         if (($snapshots_lvname[$i] == $volume) &#38;&#38; ($snapshots_vgname[$i] == $vgname))
   1129                         {
   1130                                 $lvfixedname = preg_replace('/-/', '--', $snapshots_lvname[$i]);
   1131
   1132                                 if ($GLOBALS[&#34;lvm_version&#34;] == 1)
   1133                                         $snapshot_dev = &#34;/dev/&#34; . $snapshots_vgname[$i] . &#34;/of.snapshot.&#34; . $snapshots_lvname[$i] . &#34;.&#34; . $snapshots_id[$i];
   1134                                 else
   1135                                         $snapshot_dev = &#34;/dev/mapper/&#34; . $snapshots_vgname[$i] . &#34;-of.snapshot.&#34; . $lvfixedname . &#34;.&#34; . $snapshots_id[$i];
   1136
   1137                                 $snapshot_symlink_dev = &#34;/dev/&#34; . $snapshots_vgname[$i] . &#34;/of.snapshot.&#34; . $snapshots_lvname[$i] . &#34;.&#34; . $snapshots_
Something similar needs to be done in the code to execute a change in snapshot size too (about line 460) but I haven't actually done that yet :)It's bloody messy and only fixes the issue for volume names, but it seems to work. At least someone can write now a better fix than I can around the problem :)Thanks,-The1stImmortal
</description>
<pubDate>Tue,  7 Sep 2010 01:45:22 +0100</pubDate>
</item>
<item>
<title>Arrays greater than 5tb in Openfiler : Volume Management</title>
<link>https://forums.openfiler.com/viewtopic.php?pid=22306#22306</link>
<guid isPermaLink="false">22306@https://forums.openfiler.com</guid>
<description>Topic: Arrays greater than 5tb

Message: Hi all,Recently installed openfiler on a 5.5tb, raid 5 setup on an adaptec 5805 controller.To cut the long story short, what worked for me is to create within the controller 4 raid 5 drives as follows:drive a, 5gb, openfiler o/sdrive b, 2tb, openfiler Data adrive c, 2tb, openfiler Data bdrive d, 1.5tb, openfiler Data cThen created 3 volume groups for each of Data a, b &#38; c above although for a minute contemplated whether I should just create one volume group containing a,b &#38; c and then just split it into volumes.What is the optimum setup here? should i have done something differently?I am using this to present to a Vspere cluster storage in order to backup my vm's. (needless to say can NOT present more than 2tb).thanks.
</description>
<pubDate>Mon,  6 Sep 2010 20:33:29 +0100</pubDate>
</item>
<item>
<title>Software RAID-5, dead mobo. Data lost? in Openfiler : Volume Management</title>
<link>https://forums.openfiler.com/viewtopic.php?pid=22294#22294</link>
<guid isPermaLink="false">22294@https://forums.openfiler.com</guid>
<description>Topic: Software RAID-5, dead mobo. Data lost?

Message: Dude.Awesome! thank you so much! have a great labor day weekend!
</description>
<pubDate>Sat,  4 Sep 2010 01:34:19 +0100</pubDate>
</item>
<item>
<title>Software RAID-5, dead mobo. Data lost? in Openfiler : Volume Management</title>
<link>https://forums.openfiler.com/viewtopic.php?pid=22293#22293</link>
<guid isPermaLink="false">22293@https://forums.openfiler.com</guid>
<description>Topic: Software RAID-5, dead mobo. Data lost?

Message: the beauty of linux software raid:of course you can!replace the mobo, install the os without the data drives connected, update and configure, power down, plug in drives.&#160; there is a post on these forums about getting everything back without a backup.&#160; look for posts by najones
</description>
<pubDate>Sat,  4 Sep 2010 01:20:15 +0100</pubDate>
</item>
<item>
<title>Software RAID-5, dead mobo. Data lost? in Openfiler : Volume Management</title>
<link>https://forums.openfiler.com/viewtopic.php?pid=22292#22292</link>
<guid isPermaLink="false">22292@https://forums.openfiler.com</guid>
<description>Topic: Software RAID-5, dead mobo. Data lost?

Message: Hello all, I am a technician for a small family owned computer shop that does some work with large businesses for servers as well as a smattering of regular work.I am posting because one particular business has an Openfiler box with a software raid-5 array, but the motherboard has died. Would any of you know if the motherboard can be replaced without the raided data going away? I've tried exhaustive searches, and found nothing in particular on the subject.If it's possible in any way, that'd just make my day.Thank you for your time!PS, I am unable to replace the motherboard with an identical one, unfortunately.
</description>
<pubDate>Fri,  3 Sep 2010 23:19:10 +0100</pubDate>
</item>
<item>
<title>Reinstall openfiler, how to add old media raid in Openfiler : Volume Management</title>
<link>https://forums.openfiler.com/viewtopic.php?pid=22289#22289</link>
<guid isPermaLink="false">22289@https://forums.openfiler.com</guid>
<description>Topic: Reinstall openfiler, how to add old media raid

Message: A config backup should cover everything but LDAP authentication (which has it's own backup, if you use it), and your network settings.
</description>
<pubDate>Fri,  3 Sep 2010 18:07:00 +0100</pubDate>
</item>
<item>
<title>Reinstall openfiler, how to add old media raid in Openfiler : Volume Management</title>
<link>https://forums.openfiler.com/viewtopic.php?pid=22280#22280</link>
<guid isPermaLink="false">22280@https://forums.openfiler.com</guid>
<description>Topic: Reinstall openfiler, how to add old media raid

Message: litkaj wrote:For future reference, you should have made a config backup through the web GUI.
I am currently faced with the same task, but have total access to the old install (I am reinstalling the OS on a different hard drive). Are you saying that we should have a config backup in addition to what najones mentioned in that post, or would the config backup alone take care of the volumes?
</description>
<pubDate>Fri,  3 Sep 2010 00:33:12 +0100</pubDate>
</item>
<item>
<title>No create in Volume Management in Openfiler : Volume Management</title>
<link>https://forums.openfiler.com/viewtopic.php?pid=22278#22278</link>
<guid isPermaLink="false">22278@https://forums.openfiler.com</guid>
<description>Topic: No create in Volume Management

Message: Thanks! Has removed Logical Volume, has removed Volume Group. After through GUI all it was possible to make. Why it has from the first turned out I know.
</description>
<pubDate>Thu,  2 Sep 2010 20:07:14 +0100</pubDate>
</item>
<item>
<title>No create in Volume Management in Openfiler : Volume Management</title>
<link>https://forums.openfiler.com/viewtopic.php?pid=22258#22258</link>
<guid isPermaLink="false">22258@https://forums.openfiler.com</guid>
<description>Topic: No create in Volume Management

Message: Use lvremove, vgremove, etc. to wipe out the broken bits and then start over.
</description>
<pubDate>Tue, 31 Aug 2010 19:13:24 +0100</pubDate>
</item>
<item>
<title>No create in Volume Management in Openfiler : Volume Management</title>
<link>https://forums.openfiler.com/viewtopic.php?pid=22257#22257</link>
<guid isPermaLink="false">22257@https://forums.openfiler.com</guid>
<description>Topic: No create in Volume Management

Message: Removal Volume Group in WEB GUI is impossible. Attentively having looked at the data pvdisplay; vgdisplay; lvdisplay (allocated with red color), the following is visible  Physical Volume&#160; /dev/sdb1&#160; &#160; VG Name user-winVolume Group&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;VG Name user-winLogical Volume&#160; /dev/user-win/user-win&#160; &#160; VG Name user-winTo remove Volume Group it is impossible, as it contains Logical Volume. LVM it is collected correctly IMHO. To remove Volume Group it is possible, only if it is empty. But why WEb GUI doesn't display it, I don't know. Help who can - it is ready to give the additional information.
</description>
<pubDate>Tue, 31 Aug 2010 16:40:25 +0100</pubDate>
</item>
<item>
<title>No create in Volume Management in Openfiler : Volume Management</title>
<link>https://forums.openfiler.com/viewtopic.php?pid=22248#22248</link>
<guid isPermaLink="false">22248@https://forums.openfiler.com</guid>
<description>Topic: No create in Volume Management

Message: Try deleting and recreating the volume group.
</description>
<pubDate>Tue, 31 Aug 2010 13:36:31 +0100</pubDate>
</item>
<item>
<title>No create in Volume Management in Openfiler : Volume Management</title>
<link>https://forums.openfiler.com/viewtopic.php?pid=22247#22247</link>
<guid isPermaLink="false">22247@https://forums.openfiler.com</guid>
<description>Topic: No create in Volume Management

Message: please help !!!!
</description>
<pubDate>Tue, 31 Aug 2010 11:10:32 +0100</pubDate>
</item>
<item>
<title>No create in Volume Management in Openfiler : Volume Management</title>
<link>https://forums.openfiler.com/viewtopic.php?pid=22235#22235</link>
<guid isPermaLink="false">22235@https://forums.openfiler.com</guid>
<description>Topic: No create in Volume Management

Message: I have installed Openfiler 64 bit in ATA WDC WD5002ABYS-0In OpenFiler 3 disks are established&#160; (One disk RAID6 (4disk))On OpenFiler sections Volume Group are connected on ISCSI to ESXiIt is created 3 volumes groupvolumes group RAID6 - no problemvolumes group reserv - no problemvolumes group user-win - The basic problemOn the given disk the section of occupying 100 % of a free disk has been created and type ISCSI is chosen, but after creation it isn't become accessibleBut the problem in that that CLI shows other information on problem Volume Group 
[root@of ~]# pvdisplay&#160; --- Physical volume ---&#160; PV Name&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;/dev/sdc1&#160; VG Name&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;raid6&#160; PV Size&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;929.99 GB / not usable 18.19 MB&#160; Allocatable&#160; &#160; &#160; &#160; &#160; &#160;yes (but full)&#160; PE Size (KByte)&#160; &#160; &#160; &#160;32768&#160; Total PE&#160; &#160; &#160; &#160; &#160; &#160; &#160; 29759&#160; Free PE&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;0&#160; Allocated PE&#160; &#160; &#160; &#160; &#160; 29759&#160; PV UUID&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;vfxG0l-WiJG-ae3a-16A9-lzTI-HD8I-iPfuuR&#160; --- Physical volume ---&#160; PV Name&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;/dev/sdb1&#160; VG Name&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;user-win&#160; PV Size&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;1.36 TB / not usable 12.88 MB&#160; Allocatable&#160; &#160; &#160; &#160; &#160; &#160;yes (but full)&#160; PE Size (KByte)&#160; &#160; &#160; &#160;32768&#160; Total PE&#160; &#160; &#160; &#160; &#160; &#160; &#160; 44712&#160; Free PE&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;0&#160; Allocated PE&#160; &#160; &#160; &#160; &#160; 44712&#160; PV UUID&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;ZTtK4B-8SIj-nZRd-kXnI-Cozh-WQng-LxiiI0&#160; --- Physical volume ---&#160; PV Name&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;/dev/sda4&#160; VG Name&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;reserv&#160; PV Size&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;439.25 GB / not usable 28.62 MB&#160; Allocatable&#160; &#160; &#160; &#160; &#160; &#160;yes (but full)&#160; PE Size (KByte)&#160; &#160; &#160; &#160;32768&#160; Total PE&#160; &#160; &#160; &#160; &#160; &#160; &#160; 14055&#160; Free PE&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;0&#160; Allocated PE&#160; &#160; &#160; &#160; &#160; 14055&#160; PV UUID&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;dB3a21-H9AK-1nTz-eFd5-ztUk-dALC-cEekrc
[root@of ~]# vgdisplay&#160; --- Volume group ---&#160; VG Name&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;raid6&#160; System ID&#160; Format&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; lvm2&#160; Metadata Areas&#160; &#160; &#160; &#160; 1&#160; Metadata Sequence No&#160; 3&#160; VG Access&#160; &#160; &#160; &#160; &#160; &#160; &#160;read/write&#160; VG Status&#160; &#160; &#160; &#160; &#160; &#160; &#160;resizable&#160; MAX LV&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 0&#160; Cur LV&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 2&#160; Open LV&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;2&#160; Max PV&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 0&#160; Cur PV&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 1&#160; Act PV&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 1&#160; VG Size&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;929.97 GB&#160; PE Size&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;32.00 MB&#160; Total PE&#160; &#160; &#160; &#160; &#160; &#160; &#160; 29759&#160; Alloc PE / Size&#160; &#160; &#160; &#160;29759 / 929.97 GB&#160; Free&#160; PE / Size&#160; &#160; &#160; &#160;0 / 0&#160; VG UUID&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;O75D42-VcRr-lGHN-ceGd-P2md-UsQ3-61UGPP&#160; --- Volume group ---&#160; VG Name&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;user-win&#160; System ID&#160; Format&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; lvm2&#160; Metadata Areas&#160; &#160; &#160; &#160; 1&#160; Metadata Sequence No&#160; 2&#160; VG Access&#160; &#160; &#160; &#160; &#160; &#160; &#160;read/write&#160; VG Status&#160; &#160; &#160; &#160; &#160; &#160; &#160;resizable&#160; MAX LV&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 0&#160; Cur LV&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 1&#160; Open LV&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;0&#160; Max PV&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 0&#160; Cur PV&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 1&#160; Act PV&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 1&#160; VG Size&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;1.36 TB&#160; PE Size&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;32.00 MB&#160; Total PE&#160; &#160; &#160; &#160; &#160; &#160; &#160; 44712&#160; Alloc PE / Size&#160; &#160; &#160; &#160;44712 / 1.36 TB&#160; Free&#160; PE / Size&#160; &#160; &#160; &#160;0 / 0&#160; VG UUID&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;YX3Yj5-zbsZ-k4Bd-762B-ws6E-7tyd-up1uv1&#160; --- Volume group ---&#160; VG Name&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;reserv&#160; System ID&#160; Format&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; lvm2&#160; Metadata Areas&#160; &#160; &#160; &#160; 1&#160; Metadata Sequence No&#160; 2&#160; VG Access&#160; &#160; &#160; &#160; &#160; &#160; &#160;read/write&#160; VG Status&#160; &#160; &#160; &#160; &#160; &#160; &#160;resizable&#160; MAX LV&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 0&#160; Cur LV&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 1&#160; Open LV&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;1&#160; Max PV&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 0&#160; Cur PV&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 1&#160; Act PV&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 1&#160; VG Size&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;439.22 GB&#160; PE Size&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;32.00 MB&#160; Total PE&#160; &#160; &#160; &#160; &#160; &#160; &#160; 14055&#160; Alloc PE / Size&#160; &#160; &#160; &#160;14055 / 439.22 GB&#160; Free&#160; PE / Size&#160; &#160; &#160; &#160;0 / 0&#160; VG UUID&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;d8fvrm-9AYd-S5Ct-GxLn-u0qG-i44C-BKzfpE
[root@of ~]# lvdisplay&#160; --- Logical volume ---&#160; LV Name&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; /dev/raid6/win&#160; VG Name&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; raid6&#160; LV UUID&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; MQslR1-NhJR-H29C-pEm2-5Puq-ZGld-P4XT56&#160; LV Write Access&#160; &#160; &#160; &#160; read/write&#160; LV Status&#160; &#160; &#160; &#160; &#160; &#160; &#160; available&#160; # open&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;1&#160; LV Size&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 465.00 GB&#160; Current LE&#160; &#160; &#160; &#160; &#160; &#160; &#160;14880&#160; Segments&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;1&#160; Allocation&#160; &#160; &#160; &#160; &#160; &#160; &#160;inherit&#160; Read ahead sectors&#160; &#160; &#160;auto&#160; - currently set to&#160; &#160; &#160;256&#160; Block device&#160; &#160; &#160; &#160; &#160; &#160;253:0&#160; --- Logical volume ---&#160; LV Name&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; /dev/raid6/esx&#160; VG Name&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; raid6&#160; LV UUID&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; kwuAgv-jvLF-2xLh-BEMr-iDrb-maYp-2dKI4k&#160; LV Write Access&#160; &#160; &#160; &#160; read/write&#160; LV Status&#160; &#160; &#160; &#160; &#160; &#160; &#160; available&#160; # open&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;1&#160; LV Size&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 464.97 GB&#160; Current LE&#160; &#160; &#160; &#160; &#160; &#160; &#160;14879&#160; Segments&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;1&#160; Allocation&#160; &#160; &#160; &#160; &#160; &#160; &#160;inherit&#160; Read ahead sectors&#160; &#160; &#160;auto&#160; - currently set to&#160; &#160; &#160;256&#160; Block device&#160; &#160; &#160; &#160; &#160; &#160;253:1&#160; --- Logical volume ---&#160; LV Name&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; /dev/user-win/user-win&#160; VG Name&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; user-win&#160; LV UUID&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; eEQG6B-9t0D-lt7H-ToKC-yOLL-cc4u-1ngrjI&#160; LV Write Access&#160; &#160; &#160; &#160; read/write&#160; LV Status&#160; &#160; &#160; &#160; &#160; &#160; &#160; available&#160; # open&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;0&#160; LV Size&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 1.36 TB&#160; Current LE&#160; &#160; &#160; &#160; &#160; &#160; &#160;44712&#160; Segments&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;1&#160; Allocation&#160; &#160; &#160; &#160; &#160; &#160; &#160;inherit&#160; Read ahead sectors&#160; &#160; &#160;auto&#160; - currently set to&#160; &#160; &#160;256&#160; Block device&#160; &#160; &#160; &#160; &#160; &#160;253:2&#160; --- Logical volume ---&#160; LV Name&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; /dev/reserv/reserv&#160; VG Name&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; reserv&#160; LV UUID&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 2gKsuc-UyFS-4XuG-H7UN-YFOS-Tz9v-ivu8BH&#160; LV Write Access&#160; &#160; &#160; &#160; read/write&#160; LV Status&#160; &#160; &#160; &#160; &#160; &#160; &#160; available&#160; # open&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;1&#160; LV Size&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; 439.22 GB&#160; Current LE&#160; &#160; &#160; &#160; &#160; &#160; &#160;14055&#160; Segments&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;1&#160; Allocation&#160; &#160; &#160; &#160; &#160; &#160; &#160;inherit&#160; Read ahead sectors&#160; &#160; &#160;auto&#160; - currently set to&#160; &#160; &#160;256&#160; Block device&#160; &#160; &#160; &#160; &#160; &#160;253:3
[root@of ~]# fdisk -lDisk /dev/sda: 500.1 GB, 500107862016 bytes255 heads, 63 sectors/track, 60801 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytesDisk identifier: 0x000bdb63&#160; &#160;Device Boot&#160; &#160; &#160; Start&#160; &#160; &#160; &#160; &#160;End&#160; &#160; &#160; Blocks&#160; &#160;Id&#160; System/dev/sda1&#160; &#160;*&#160; &#160; &#160; &#160; &#160; &#160;1&#160; &#160; &#160; &#160; &#160; 13&#160; &#160; &#160; 104391&#160; &#160;83&#160; Linux/dev/sda2&#160; &#160; &#160; &#160; &#160; &#160; &#160; 14&#160; &#160; &#160; &#160; 3200&#160; &#160; 25599577+&#160; 83&#160; Linux/dev/sda3&#160; &#160; &#160; &#160; &#160; &#160; 3201&#160; &#160; &#160; &#160; 3461&#160; &#160; &#160;2096482+&#160; 82&#160; Linux swap / Solaris/dev/sda4&#160; &#160; &#160; &#160; &#160; &#160; 3462&#160; &#160; &#160; &#160;60801&#160; &#160;460583550&#160; &#160;8e&#160; Linux LVMDisk /dev/sdb: 1500.3 GB, 1500301910016 bytes255 heads, 63 sectors/track, 182401 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytesDisk identifier: 0x000b18fc&#160; &#160;Device Boot&#160; &#160; &#160; Start&#160; &#160; &#160; &#160; &#160;End&#160; &#160; &#160; Blocks&#160; &#160;Id&#160; System/dev/sdb1&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;1&#160; &#160; &#160; 182401&#160; 1465136001&#160; &#160;8e&#160; Linux LVMDisk /dev/sdc: 998.6 GB, 998569410560 bytes255 heads, 63 sectors/track, 121402 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytesDisk identifier: 0x000e0f20&#160; &#160;Device Boot&#160; &#160; &#160; Start&#160; &#160; &#160; &#160; &#160;End&#160; &#160; &#160; Blocks&#160; &#160;Id&#160; System/dev/sdc1&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;1&#160; &#160; &#160; 121402&#160; &#160;975161533+&#160; 8e&#160; Linux LVMDisk /dev/dm-0: 499.3 GB, 499289948160 bytes255 heads, 63 sectors/track, 60701 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytesDisk identifier: 0x00000000Disk /dev/dm-0 doesn't contain a valid partition tableDisk /dev/dm-1: 499.3 GB, 499256393728 bytes255 heads, 63 sectors/track, 60697 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytesDisk identifier: 0x00000000Disk /dev/dm-1 doesn't contain a valid partition tableDisk /dev/dm-2: 1500.3 GB, 1500285763584 bytes255 heads, 63 sectors/track, 182399 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytesDisk identifier: 0x00000000Disk /dev/dm-2 doesn't contain a valid partition tableDisk /dev/dm-3: 471.6 GB, 471607541760 bytes255 heads, 63 sectors/track, 57336 cylindersUnits = cylinders of 16065 * 512 = 8225280 bytesDisk identifier: 0x00000000Disk /dev/dm-3 doesn't contain a valid partition table
[root@of ~]# cat /etc/ietd.conf#####&#160; &#160;WARNING!!! - This configuration file generated by Openfiler. DO NOT MANUALLY EDIT.&#160; #####Target iqn.2006-01.com.openfiler:tsn.e10e24bf0958&#160; &#160; &#160; &#160; HeaderDigest None&#160; &#160; &#160; &#160; DataDigest None&#160; &#160; &#160; &#160; MaxConnections 1&#160; &#160; &#160; &#160; InitialR2T Yes&#160; &#160; &#160; &#160; ImmediateData No&#160; &#160; &#160; &#160; MaxRecvDataSegmentLength 131072&#160; &#160; &#160; &#160; MaxXmitDataSegmentLength 131072&#160; &#160; &#160; &#160; MaxBurstLength 262144&#160; &#160; &#160; &#160; FirstBurstLength 262144&#160; &#160; &#160; &#160; DefaultTime2Wait 2&#160; &#160; &#160; &#160; DefaultTime2Retain 20&#160; &#160; &#160; &#160; MaxOutstandingR2T 8&#160; &#160; &#160; &#160; DataPDUInOrder Yes&#160; &#160; &#160; &#160; DataSequenceInOrder Yes&#160; &#160; &#160; &#160; ErrorRecoveryLevel 0&#160; &#160; &#160; &#160; Lun 0 Path=/dev/reserv/reserv,Type=blockio,ScsiSN=2gKsuc-UyFS-4XuG,ScsiId=2gKsuc-UyFS-4XuG,IOMode=wtTarget iqn.2006-01.com.openfiler:tsn.2ba567d4f14e&#160; &#160; &#160; &#160; HeaderDigest None&#160; &#160; &#160; &#160; DataDigest None&#160; &#160; &#160; &#160; MaxConnections 1&#160; &#160; &#160; &#160; InitialR2T Yes&#160; &#160; &#160; &#160; ImmediateData No&#160; &#160; &#160; &#160; MaxRecvDataSegmentLength 131072&#160; &#160; &#160; &#160; MaxXmitDataSegmentLength 131072&#160; &#160; &#160; &#160; MaxBurstLength 262144&#160; &#160; &#160; &#160; FirstBurstLength 262144&#160; &#160; &#160; &#160; DefaultTime2Wait 2&#160; &#160; &#160; &#160; DefaultTime2Retain 20&#160; &#160; &#160; &#160; MaxOutstandingR2T 8&#160; &#160; &#160; &#160; DataPDUInOrder Yes&#160; &#160; &#160; &#160; DataSequenceInOrder Yes&#160; &#160; &#160; &#160; ErrorRecoveryLevel 0&#160; &#160; &#160; &#160; Lun 0 Path=/dev/raid6/win,Type=blockio,ScsiSN=MQslR1-NhJR-H29C,ScsiId=MQslR1-NhJR-H29C,IOMode=wtTarget iqn.2006-01.com.openfiler:tsn.2a9b9df0d9d2&#160; &#160; &#160; &#160; HeaderDigest None&#160; &#160; &#160; &#160; DataDigest None&#160; &#160; &#160; &#160; MaxConnections 1&#160; &#160; &#160; &#160; InitialR2T Yes&#160; &#160; &#160; &#160; ImmediateData No&#160; &#160; &#160; &#160; MaxRecvDataSegmentLength 131072&#160; &#160; &#160; &#160; MaxXmitDataSegmentLength 131072&#160; &#160; &#160; &#160; MaxBurstLength 262144&#160; &#160; &#160; &#160; FirstBurstLength 262144&#160; &#160; &#160; &#160; DefaultTime2Wait 2&#160; &#160; &#160; &#160; DefaultTime2Retain 20&#160; &#160; &#160; &#160; MaxOutstandingR2T 8&#160; &#160; &#160; &#160; DataPDUInOrder Yes&#160; &#160; &#160; &#160; DataSequenceInOrder Yes&#160; &#160; &#160; &#160; ErrorRecoveryLevel 0&#160; &#160; &#160; &#160; Lun 0 Path=/dev/raid6/esx,Type=blockio,ScsiSN=kwuAgv-jvLF-2xLh,ScsiId=kwuAgv-jvLF-2xLh,IOMode=wt
The main task - to connect section user-win on ISCSI to ESXi
</description>
<pubDate>Mon, 30 Aug 2010 11:06:46 +0100</pubDate>
</item>
<item>
<title>Reinstall openfiler, how to add old media raid in Openfiler : Volume Management</title>
<link>https://forums.openfiler.com/viewtopic.php?pid=22210#22210</link>
<guid isPermaLink="false">22210@https://forums.openfiler.com</guid>
<description>Topic: Reinstall openfiler, how to add old media raid

Message: For future reference, you should have made a config backup through the web GUI.For now:http://forums.openfiler.com/viewtopic.php?id=1036
</description>
<pubDate>Fri, 27 Aug 2010 19:09:16 +0100</pubDate>
</item>
<item>
<title>Reinstall openfiler, how to add old media raid in Openfiler : Volume Management</title>
<link>https://forums.openfiler.com/viewtopic.php?pid=22206#22206</link>
<guid isPermaLink="false">22206@https://forums.openfiler.com</guid>
<description>Topic: Reinstall openfiler, how to add old media raid

Message: My research so far indicates that I should be able to have my lvm running again by copying the files in /etc/lvm/backup/ from my backup into the system. And then use &#34;vgscan&#34;, &#34;pvscan&#34; and then &#34;vgchange media -a y&#34; to activate the volume. Not sure how to get this volume accepted by the openfiler GUI though?
</description>
<pubDate>Fri, 27 Aug 2010 12:06:48 +0100</pubDate>
</item>
</channel>
</rss>
