<div dir="ltr">Hi，Robert<div>Now I use lvm storage pool to test. But there are still some problems. Is there any problem with my operation?</div><div><br></div><div><div>[root@node-4 proto]# linstor list-node</div><div>╭────────────────────────────────────────╮</div><div>┊ Node ┊ NodeType ┊ IPs ┊ State ┊</div><div>╞┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄╡</div><div>┊ node-1 ┊ COMBINED ┊ 10.10.0.72 ┊ ok ┊</div><div>┊ node-4 ┊ COMBINED ┊ 10.10.0.75 ┊ ok ┊</div><div>╰────────────────────────────────────────╯</div></div><div><br></div><div><div>[root@node-4 proto]# linstor list-resource</div><div>╭─────────────────────────────────────────────────╮</div><div>┊ ResourceName ┊ Node ┊ Port ┊ Device ┊ State ┊</div><div>╞┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄╡</div><div>┊ rstdfn ┊ node-1 ┊ 7000 ┊ drbdpool ┊ ok ┊</div><div>┊ rstdfn ┊ node-4 ┊ 7000 ┊ drbdpool ┊ ok ┊</div><div>╰─────────────────────────────────────────────────╯</div></div><div><br></div><div><div>[root@node-4 proto]# linstor list-storage-pool</div><div>╭─────────────────────────────────────────────────────────────────────╮</div><div>┊ StoragePool ┊ Node ┊ Driver ┊ DriverDevice ┊ SupportsSnapshots ┊</div><div>╞┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄╡</div><div>┊ lvm ┊ node-1 ┊ LvmDriver ┊ drbdpool ┊ false ┊</div><div>┊ lvm ┊ node-4 ┊ LvmDriver ┊ drbdpool ┊ false ┊</div><div>╰─────────────────────────────────────────────────────────────────────╯</div></div><div><br></div><div>[root@node-4 proto]# vgdisplay <br></div><div><br></div><div><div> --- Volume group ---</div><div> VG Name drbdpool</div><div> System ID </div><div> Format lvm2</div><div> Metadata Areas 1</div><div> Metadata Sequence No 1</div><div> VG Access read/write</div><div> VG Status resizable</div><div> MAX LV 0</div><div> Cur LV 0</div><div> Open LV 0</div><div> Max PV 0</div><div> Cur PV 1</div><div> Act PV 1</div><div> VG Size <30.00 GiB</div><div> PE Size 4.00 MiB</div><div> Total PE 7679</div><div> Alloc PE / Size 0 / 0 </div><div> Free PE / Size 7679 / <30.00 GiB</div><div> VG UUID QpdD46-Q4dh-qS7e-pSsX-JLos-gEJr-MX96EU</div></div><div><br></div><div>When I create volume, some error in log:</div><div><br></div><div><div>[root@node-4 proto]# linstor list-volume</div><div>╭──────────────────────────────────────────────────────╮</div><div>┊ Node ┊ Resource ┊ VolumeNr ┊ MinorNr ┊ State ┊</div><div>╞┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄╡</div><div>┊ node-1 ┊ rstdfn ┊ 0 ┊ 1000 ┊ not present ┊</div><div>┊ node-1 ┊ rstdfn ┊ 1 ┊ 1001 ┊ not present ┊</div><div>┊ node-4 ┊ rstdfn ┊ 0 ┊ 1000 ┊ not present ┊</div><div>┊ node-4 ┊ rstdfn ┊ 1 ┊ 1001 ┊ not present ┊</div><div>╰──────────────────────────────────────────────────────╯</div></div><div><br></div><div>Feb 24 15:09:16 node-4 Satellite: [MainWorkerPool_0009] ERROR LINSTOR/Satellite - Missing required namespace for backing storage [Report number A910AC3-000001]<br></div><div><br></div><div><div>[root@node-4 linstor-server]# vi logs/ErrorReport-A910AC3-000001.log </div><div><br></div><div>ERROR REPORT A910AC3-000001</div><div><br></div><div>============================================================</div><div><br></div><div>Application: LINBIT® LINSTOR</div><div>Module: Satellite</div><div>Version: 0.1.1</div><div>Build ID: b257fa2de27a92ee33a1d5a81f6da30ddca950e7</div><div>Build time: Wed Feb 14 12:49:01 UTC 2018</div><div>Error time: 2018-02-24 15:09:16</div><div><br></div><div>============================================================</div><div><br></div><div>Reported error:</div><div>===============</div><div><br></div><div>Category: Error</div><div>Class name: ImplementationError</div><div>Class canonical name: com.linbit.ImplementationError</div><div>Generated at: Method 'reconfigureStorageDriver', Source file 'StorPoolData.java', Line #304</div><div><br></div><div>Error message: Missing required namespace for backing storage</div><div><br></div><div>Call backtrace:</div><div><br></div><div> Method Native Class:Line number</div><div> reconfigureStorageDriver N com.linbit.linstor.StorPoolData:304</div><div> getVolumeStorageDriver N com.linbit.linstor.core.DrbdDeviceHandler:510</div><div> evaluateStorageVolume N com.linbit.linstor.core.DrbdDeviceHandler:589</div><div> createResource N com.linbit.linstor.core.DrbdDeviceHandler:756</div><div> dispatchResource N com.linbit.linstor.core.DrbdDeviceHandler:176</div><div> run N com.linbit.linstor.core.DeviceManagerImpl$DeviceHandlerInvocation:904</div><div> run N com.linbit.WorkerPool$WorkerThread:179</div><div><br></div><div><br></div><div>END OF ERROR REPORT.</div></div><div><br></div><div class="gmail_extra"><br><div class="gmail_quote">2018-02-23 18:15 GMT+08:00 Robert Altnoeder <span dir="ltr"><<a href="mailto:robert.altnoeder@linbit.com" target="_blank">robert.altnoeder@linbit.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">On 02/23/2018 10:55 AM, yang zhenyu wrote:<br>
><br>
> [root@node-1 linstor-server]# zfs list<br>
> NAME USED AVAIL REFER MOUNTPOINT<br>
> linstorpool 384K 1.76T 96K /linstorpool<br>
><br>
> Then I create a storage-pool, I don't understand the args<br>
> 'driver_device' means what?<br>
> Is a zfs zvol name? or zvol device name? like zd0...<br>
<br>
</span>The driver_device is the name of a zpool that will be used to create<br>
storage in.<br>
<br>
However, the ZFS driver does not yet work properly, and it will probably<br>
only be fixed a few weeks from now because other higher priority<br>
development tasks are scheduled before fixing it.<br>
It might work to some extent if a dummy volume is created in the zpool<br>
before trying to use the zpool with LINSTOR.<br>
<span class="gmail-"><br>
> [root@node-1 linstor-server]# linstor create-resource -s zfs -d rstdfn<br>
> node-1<br>
> [root@node-1 linstor-server]# linstor create-resource -s zfs -d rstdfn<br>
> node-4<br>
> [root@node-1 linstor-server]# linstor list-resource<br>
> ╭─────────────────────────────<wbr>────────────────────╮<br>
> ┊ ResourceName ┊ Node ┊ Port ┊ Device ┊ State ┊<br>
> ╞┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄<wbr>┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄╡<br>
> ┊ rstdfn ┊ node-1 ┊ 7000 ┊ DISKLESS ┊ ok ┊<br>
> ┊ rstdfn ┊ node-4 ┊ 7000 ┊ DISKLESS ┊ ok ┊<br>
> ╰─────────────────────────────<wbr>────────────────────╯<br>
><br>
> Why this Device is DISKLESS?<br>
<br>
</span>Because you set it to diskless by using the '-d' option on the<br>
create-resource command.<br>
<span class="gmail-"><br>
> [root@node-1 linstor-server]# linstor create-volume-definition -d 2<br>
> rstdfn 30G<br>
<br>
</span>-d (aka deploy) is a leftover from drbdmanage that is not implemented<br>
and does not belong in creation of volume definitions, this will be<br>
removed in future versions.<br>
(actually, the entire user interface will probably change significantly<br>
in future versions)<br>
<span class="gmail-"><br>
> I do not know where is the problem. Is it network communication<br>
> problems? But I `telnet node-4 3366` is no problem.<br>
<br>
</span>Information about most errors that occur can be found in LINSTOR's error<br>
reports in its "logs" directory.<br>
<div class="gmail-HOEnZb"><div class="gmail-h5"><br>
best regards,<br>
--<br>
Robert Altnoeder<br>
<a href="tel:%2B43%201%20817%2082%2092%200" value="+43181782920">+43 1 817 82 92 0</a><br>
<a href="mailto:robert.altnoeder@linbit.com">robert.altnoeder@linbit.com</a><br>
<br>
LINBIT | Keeping The Digital World Running<br>
DRBD - Corosync - Pacemaker<br>
f / t / in / g+<br>
<br>
DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.<br>
</div></div></blockquote></div><br></div></div>