
It’s Monday morning, the caffeine from your morning coffee still hasn’t hit you yet, and like clockwork %USERNAME% calls with password issues…typical.
…Windows, Exchange, PowerShell, Batch, Servers, etc
1 2 3 4 5 6 7 | root@xen1~]# <strong><span style="color: #0000ff;">xe sr-list</span></strong> uuid ( RO) : b55e5f09-8fef-4b5d-8dae-9410d630f205 name-label ( RW): SATA_7.2K 20T name-description ( RW): Hardware HBA SR host ( RO): type ( RO): lvmohba content-type ( RO): |
1 2 | root@xen1 ~]# <strong><span style="color: #0000ff;">vgs | awk '{print $1}' | grep b55e5f09-8fef-4b5d-8dae-9410d630f205</span></strong> VG_XenStorage-b55e5f09-8fef-4b5d-8dae-9410d630f205 |
1 2 | root@xen1 ~]# <strong><span style="color: #0000ff;">lvcreate -L3T -n"LV-"$(uuidgen) VG_XenStorage-b55e5f09-8fef-4b5d-8dae-9410d630f205</span></strong> Logical volume "LV-4e3da1e4-9e1a-4e12-96a1-d3c233efc0d5" created |
1 | root@xen1 ~]# <span style="color: #0000ff;"><strong>xe sr-scan uuid=b55e5f09-8fef-4b5d-8dae-9410d630f205</strong></span> |
After scanning the SR, the new VDI magically appeared under the Storage tab for this SR in XenCenter.
I then gave it a name and description, and assigned it to a VM just like any other VDI.
This has to be one of the coolest PC’s I’ve ever built.
We were given the task to build the fastest PC for Video editing and rendering, with the most storage space we could fit, all without becoming a heater or jet engine for the user sitting in a cubical. The system had to be fault tolerant, so one OS hard drive could die and/or one drive from the RAID 5 array could die and still function. If the case could hold more drives I would have devoted another drive or two for a hot spare.