<div dir="ltr">Hi，Robert<br><br>Now the node status is ok, but integration zfs is still a problem, so I still need your help.<br><br>Here are my steps:<br><br>[root@node-1 linstor-server]# linstor list-node<br>╭─────────────────────────────────────────╮<br>┊ Node ┊ NodeType ┊ IPs ┊ State ┊<br>╞┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄╡<br>┊ node-1 ┊ COMBINED ┊ 10.10.0.72 ┊ ok ┊<br>┊ node-4 ┊ SATELLITE ┊ 10.10.0.75 ┊ ok ┊<br>╰─────────────────────────────────────────╯<br><br>I hava a zfs pool named linstorpool.<div><br>[root@node-1 linstor-server]# zfs list<br>NAME USED AVAIL REFER MOUNTPOINT<br>linstorpool 384K 1.76T 96K /linstorpool</div><div><br></div><div>Then I create a storage-pool, I don't understand the args 'driver_device' means what?</div><div>Is a zfs zvol name? or zvol device name? like zd0...<br></div><div><br></div><div>usage: linstor create-storage-pool [-h]<br>name node_name {lvm,lvmthin,zfs}<br>driver_device</div><div><br></div><div>Here I am free to use a name 'test1'.<br><br>linstor create-storage-pool zfs node-1 zfs test1<br>[root@node-1 linstor-server]# linstor list-storage-pool<br>╭─────────────────────────────────────────────────────────────────────╮<br>┊ StoragePool ┊ Node ┊ Driver ┊ DriverDevice ┊ SupportsSnapshots ┊<br>╞┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄╡<br>┊ zfs ┊ node-1 ┊ ZfsDriver ┊ test1 ┊ true ┊<br>╰─────────────────────────────────────────────────────────────────────╯<br>root@node-1 linstor-server]# linstor create-resource-definition rstdfn<br>[root@node-1 linstor-server]# linstor list-resource-definition<br>╭─────────────────────────────╮<br>┊ ResourceName ┊ Port ┊ State ┊<br>╞┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄╡<br>┊ rstdfn ┊ 7000 ┊ ok ┊<br>╰─────────────────────────────╯<br>[root@node-1 linstor-server]# linstor create-resource -s zfs -d rstdfn node-1<br>[root@node-1 linstor-server]# linstor create-resource -s zfs -d rstdfn node-4<br>[root@node-1 linstor-server]# linstor list-resource<br>╭─────────────────────────────────────────────────╮<br>┊ ResourceName ┊ Node ┊ Port ┊ Device ┊ State ┊<br>╞┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄╡<br>┊ rstdfn ┊ node-1 ┊ 7000 ┊ DISKLESS ┊ ok ┊<br>┊ rstdfn ┊ node-4 ┊ 7000 ┊ DISKLESS ┊ ok ┊<br>╰─────────────────────────────────────────────────╯<br><br>Why this Device is DISKLESS?<br><br>[root@node-1 linstor-server]# linstor create-volume-definition -d 2 rstdfn 30G<br>SUCCESS:<br>New volume definition with number '0' of resource definition 'rstdfn' created.<br>WARNING:<br>Description:<br>Satellite reported an error during fullSync. This change will NOT be delivered to satellte 'node-4' until the error is resolved. Reconnect the satellite to the controller to remove this blockade.<br>Details:<br>Resource definition: rstdfn, Volume number: 0<br><br>[root@node-1 ~]# tailf /var/log/messages<br>Feb 23 17:38:52 node-1 Satellite: Adjusting resource rstdfn<br>Feb 23 17:38:52 node-1 kernel: drbd rstdfn: Starting worker thread (from drbdsetup [4730])<br>Feb 23 17:38:52 node-1 kernel: drbd rstdfn node-4: Starting sender thread (from drbdsetup [4735])<br>Feb 23 17:38:52 node-1 kernel: drbd rstdfn node-4: conn( StandAlone -> Unconnected )<br>Feb 23 17:38:52 node-1 kernel: drbd rstdfn node-4: Starting receiver thread (from drbd_w_rstdfn [4731])<br>Feb 23 17:38:52 node-1 kernel: drbd rstdfn node-4: conn( Unconnected -> Connecting )<br><br>[root@node-1 linstor-server]# linstor list-volume<br>╭──────────────────────────────────────────────────────╮<br>┊ Node ┊ Resource ┊ VolumeNr ┊ MinorNr ┊ State ┊<br>╞┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄╡<br>┊ node-1 ┊ rstdfn ┊ 0 ┊ 1000 ┊ not present ┊<br>┊ node-4 ┊ rstdfn ┊ 0 ┊ 1000 ┊ unknown ┊<br>╰──────────────────────────────────────────────────────╯<br><br>[root@node-1 linstor-server]# drbdadm status<br>rstdfn role:Secondary<br>disk:Diskless<br>node-4 connection:Connecting<br><br>[root@node-4 opt]# drbdadm status<br># No currently configured DRBD found.<br><br>[root@node-4 opt]# cat /etc/drbd.d/rstdfn.res<br>cat: /etc/drbd.d/rstdfn.res: No such file or directory</div><div><br></div>I do not know where is the problem. Is it network communication problems? But I `telnet node-4 3366` is no problem.<br></div><div class="gmail_extra"><br><div class="gmail_quote">2018-02-22 19:02 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
On 02/22/2018 11:35 AM, yang zhenyu wrote:<br>
> [...]<br>
<span class="">><br>
> The following is my understanding:<br>
><br>
> 1. The LINSTOR Controller node corresponds to the drbdmanage pure<br>
> controller, there is no storage.<br>
> 2. The LINSTOR Combined node corresponds to the drbdmanage controller<br>
> with storage.<br>
> 3. The LINSTOR Satellites node corresponds to the drbdmanage<br>
> satellites with storage.<br>
<br>
</span>LINSTOR comprises two modules, the controller and the satellite.<br>
<br>
Only the controller manages the configuration, e.g., all resource<br>
definitions, storage pools, network interfaces of nodes, etc. are<br>
defined on the controller.<br>
<br>
Only the satellites deal with actual storage, with DRBD, etc., and the<br>
satellites obtain information about the configuration of their resources<br>
from the active controller (the controller contacts all registered<br>
satellites).<br>
<br>
Only one controller is active at a time, but multiple installations of<br>
the controller may be provided so that if the active controller node<br>
crashes, the controller can be started on another node. This kind of<br>
failover is managed by a cluster manager such as Pacemaker.<br>
<br>
A combined node is a node that can run the controller module and the<br>
satellite module. This is required if one of the storage nodes is also<br>
running the controller module. In this case, the controller module and<br>
the satellite module will be running on that node at the same time, and<br>
the controller will connect to the satellite on the local node the same<br>
way it connects to remote satellites.<br>
<br>
The controller can also be installed on platforms that do not support<br>
the kind of storage that the satellites support, or that do not support<br>
DRBD (e.g., you could run the controller on an AIX or HP/UX box and have<br>
it control satellites that run on Linux, and in the future also Windows<br>
with DRBD for Windows).<br>
<span class=""><br>
> 4. The LINSTOR Auxiliary node corresponds to the drbdmanage client node?<br>
<br>
</span>Auxiliary nodes are more or less disabled nodes, they do not run the<br>
LINSTOR software. They are needed for future features, as of now, they<br>
are not very useful for anything.<br>
<span class=""><br>
> 5. Only the control node to access the database?<br>
<br>
</span>Only one controller is connected to the database at any time.<br>
<span class=""><br>
> Currently linstor only use the derby database? So I need a shared storage for multiple<br>
> control nodes.<br>
<br>
</span>Technically, the controller is able to connect to a<br>
centralized/networked database (we run one of our development systems<br>
with such a configuration), but normally it runs an Apache Derby<br>
embedded database in the controller module's process. The database layer<br>
is exchangable, but Derby is the only driver that is implemented as of<br>
today.<br>
<span class=""><br>
> But I do not understand what is the ues of cluster manage software at here? For example pacemaker.<br>
<br>
</span>It can be used for automatic failover to another controller if the<br>
active controller node fails.<br>
<br>
best regards,<br>
<div class="HOEnZb"><div class="h5">--<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>