Re: [DRBD-user] Wrong free space calculation in python-drbdmanage 0.99.15-1

2018-03-20 Thread Roberto Resoli
Il 20/02/2018 12:31, Roberto Resoli ha scritto:
> Hello,
> 
> Just updated python-drbdmanage to 0.99.15-1; this one is just to report
> that drbdmanage free space calculation is still wrong in
> 
> drbdmanage.storage.lvm_thinlv.LvmThinLv plugin
> 
> on platforms using recent lvm2 (Proxmox 5, for instance).
> 
> For details:
> 
> http://lists.linbit.com/pipermail/drbd-user/2017-October/023737.html

python-drbdmanage 0.99.16-1 (just released) solves that.

Many tanks,
rob


___
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user


Re: [DRBD-user] Upgrade PVE 4.4 to 5.1 DRB9

2018-03-20 Thread Roland Kammerer
On Tue, Mar 20, 2018 at 01:24:09PM +, Yannis Milios wrote:
> >>  Do you get new headers automatically when there is a new Proxmox kernel?
> 
> My experience has been that, no, PVE does not install the pve-headers-
> automatically after each kernel upgrade (apt dist-upgrade).
> So, what I need to do is 2 additional steps:
> 
> - Install pve-headers- matching the new kernel.
> - Run apt install drbd-dkms --reinstall

Hm, for the latest metapackage + headers it looks like they match. I
mean "it has to be like that", otherwise they would also break every
other dkms package. So as long as not proven otherwise, I assume they do
the correct thing and they match.

Regards, rck
___
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user


Re: [DRBD-user] Upgrade PVE 4.4 to 5.1 DRB9

2018-03-20 Thread Yannis Milios
>>  Do you get new headers automatically when there is a new Proxmox kernel?

My experience has been that, no, PVE does not install the pve-headers-
automatically after each kernel upgrade (apt dist-upgrade).
So, what I need to do is 2 additional steps:

- Install pve-headers- matching the new kernel.
- Run apt install drbd-dkms --reinstall

Y
___
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user


Re: [DRBD-user] Upgrade PVE 4.4 to 5.1 DRB9

2018-03-20 Thread Shafeek Sumser
Yes its clear.  :-) thanks

A+
Shafeek

On Tue, Mar 20, 2018 at 2:49 PM, Roland Kammerer  wrote:

> On Tue, Mar 20, 2018 at 02:37:08PM +0400, Shafeek Sumser wrote:
> > Roland, No not the meta package.  Since the meta package point to another
> > version of the kernel.
> >
> > The user should install the package that corresponds to its actual kernel
> > version.  ie  apt-get install pve-headers-`uname -r`
> > After that the user installs the drbd-dkms.
>
> For the typical user I assume that she follows the latest kernel, then
> the meta package matches. Only if a user stays at an older version (for
> whatever reason), she has to install the specific version.
>
> I hope that is now clear enough[1]. Second paragraph in "Proxmox Plugin
> Installation".
>
> Enough hand holding for today ;-). If that is still unclear, patches
> welcome, in the end it is just how dkms works anyways...
>
> Regards, rck
>
> [1] https://github.com/LINBIT/linbit-documentation/blob/
> master/UG9/proxmox.adoc
> ___
> drbd-user mailing list
> drbd-user@lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user
>



-- 
Shafeek SUMSER
___
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user


Re: [DRBD-user] Upgrade PVE 4.4 to 5.1 DRB9

2018-03-20 Thread Roland Kammerer
On Tue, Mar 20, 2018 at 02:37:08PM +0400, Shafeek Sumser wrote:
> Roland, No not the meta package.  Since the meta package point to another
> version of the kernel.
> 
> The user should install the package that corresponds to its actual kernel
> version.  ie  apt-get install pve-headers-`uname -r`
> After that the user installs the drbd-dkms.

For the typical user I assume that she follows the latest kernel, then
the meta package matches. Only if a user stays at an older version (for
whatever reason), she has to install the specific version.

I hope that is now clear enough[1]. Second paragraph in "Proxmox Plugin
Installation".

Enough hand holding for today ;-). If that is still unclear, patches
welcome, in the end it is just how dkms works anyways...

Regards, rck

[1] https://github.com/LINBIT/linbit-documentation/blob/master/UG9/proxmox.adoc
___
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user


Re: [DRBD-user] Upgrade PVE 4.4 to 5.1 DRB9

2018-03-20 Thread Shafeek Sumser
Roland, No not the meta package.  Since the meta package point to another
version of the kernel.

The user should install the package that corresponds to its actual kernel
version.  ie  apt-get install pve-headers-`uname -r`
After that the user installs the drbd-dkms.

After all installation done, a simple list directory should have the below:

root@srv3:~# ls /lib/modules/`uname -r`/updates/dkms/
drbd.ko  drbd_transport_tcp.ko

If a restart of the drbd service does not work, then reboot the server.

Ok to add the this hint to the documentation, this will definitely help


A+
Shafeek


On Tue, Mar 20, 2018 at 2:24 PM, Roland Kammerer  wrote:

> On Tue, Mar 20, 2018 at 02:17:39PM +0400, Shafeek Sumser wrote:
> > In fact, what I did before was installed drbd-dkms and then I installed
> the
> > kernel headers.
> > So to rectify, I just did a removal of drbd-dkms and re-install it.  So
> the
> > proper way is to install the kernel-headers first then the drbd-dms
> > package.
> >
> > A search in the proxmox kernel packages, I found that there is the meta
> > package pve-headers but it uses the kernel pve-headers-4.10.5-1-pve.
> >
> > My actual kernel is on 4.13.13-6-pve.  So the meta package did not
> work.  I
> > need to install the proper kernel version apt-get install
> > pve-headers-`uname -r`
> >
> > Whenever there is a new kernel provided by pve, I think they provide
> their
> > respective kernel headers.
> >
> > I will watch this and whenever there is a kernel updates it should be
> > working from my point of view since it will also update its respective
> > kernel headers.
>
> Thanks for the explanation. Then the typical user has to install that
> meta package and then the rest should just work... I add that hint to
> the users guide.
>
> Regards, rck
> ___
> drbd-user mailing list
> drbd-user@lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user
>



-- 
Shafeek SUMSER
___
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user


Re: [DRBD-user] Upgrade PVE 4.4 to 5.1 DRB9

2018-03-20 Thread Roland Kammerer
On Tue, Mar 20, 2018 at 02:17:39PM +0400, Shafeek Sumser wrote:
> In fact, what I did before was installed drbd-dkms and then I installed the
> kernel headers.
> So to rectify, I just did a removal of drbd-dkms and re-install it.  So the
> proper way is to install the kernel-headers first then the drbd-dms
> package.
> 
> A search in the proxmox kernel packages, I found that there is the meta
> package pve-headers but it uses the kernel pve-headers-4.10.5-1-pve.
> 
> My actual kernel is on 4.13.13-6-pve.  So the meta package did not work.  I
> need to install the proper kernel version apt-get install
> pve-headers-`uname -r`
> 
> Whenever there is a new kernel provided by pve, I think they provide their
> respective kernel headers.
> 
> I will watch this and whenever there is a kernel updates it should be
> working from my point of view since it will also update its respective
> kernel headers.

Thanks for the explanation. Then the typical user has to install that
meta package and then the rest should just work... I add that hint to
the users guide.

Regards, rck
___
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user


Re: [DRBD-user] Upgrade PVE 4.4 to 5.1 DRB9

2018-03-20 Thread Shafeek Sumser
In fact, what I did before was installed drbd-dkms and then I installed the
kernel headers.
So to rectify, I just did a removal of drbd-dkms and re-install it.  So the
proper way is to install the kernel-headers first then the drbd-dms
package.

A search in the proxmox kernel packages, I found that there is the meta
package pve-headers but it uses the kernel pve-headers-4.10.5-1-pve.

My actual kernel is on 4.13.13-6-pve.  So the meta package did not work.  I
need to install the proper kernel version apt-get install
pve-headers-`uname -r`

Whenever there is a new kernel provided by pve, I think they provide their
respective kernel headers.

I will watch this and whenever there is a kernel updates it should be
working from my point of view since it will also update its respective
kernel headers.

A+
Shafeek



On Tue, Mar 20, 2018 at 1:20 PM, Roland Kammerer  wrote:

> On Mon, Mar 19, 2018 at 08:16:16PM +, Yannis Milios wrote:
> > A simple ‘apt install drbd-dkms —reinstall’ should work as well.
> > Remember repeating this task each time you upgrade your
> > kernel/headers.
>
> Really? DKMS should handle that, that is exactly it's job. So if that
> really does not work automatically (after getting it "kick started" by
> installing the headers the first time), then there is something wrong.
>
> Do you get new headers automatically when there is a new Proxmox kernel?
> In other words is there a meta package for the headers that is updated
> when they release a new kernel?
>
> This should be something like "linux-headers-amd64" (but likely with
> some "pve" in it's name). Or are there only pkgs for a specific release,
> like: linux-headers-4.14.0-3-common/linux-headers-4.14.0-3-amd64. Again,
> this is the output from a normal Debian box, Proxmox mixes in some "pve"
> IIRC.
>
> Or I'm holding my DKMS magic for the kernel wrong ;-).
>
> Feedback would be great.
>
> Thanks, rck
> ___
> drbd-user mailing list
> drbd-user@lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user
>



-- 
Shafeek SUMSER
___
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user


Re: [DRBD-user] Upgrade PVE 4.4 to 5.1 DRB9

2018-03-20 Thread Roland Kammerer
On Mon, Mar 19, 2018 at 08:16:16PM +, Yannis Milios wrote:
> A simple ‘apt install drbd-dkms —reinstall’ should work as well.
> Remember repeating this task each time you upgrade your
> kernel/headers.

Really? DKMS should handle that, that is exactly it's job. So if that
really does not work automatically (after getting it "kick started" by
installing the headers the first time), then there is something wrong.

Do you get new headers automatically when there is a new Proxmox kernel?
In other words is there a meta package for the headers that is updated
when they release a new kernel?

This should be something like "linux-headers-amd64" (but likely with
some "pve" in it's name). Or are there only pkgs for a specific release,
like: linux-headers-4.14.0-3-common/linux-headers-4.14.0-3-amd64. Again,
this is the output from a normal Debian box, Proxmox mixes in some "pve"
IIRC.

Or I'm holding my DKMS magic for the kernel wrong ;-).

Feedback would be great.

Thanks, rck
___
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user


Re: [DRBD-user] Unable to init a node

2018-03-20 Thread Roland Kammerer
On Mon, Mar 19, 2018 at 07:12:29PM +0100, Jdt wrote:
> 
> 
> Le 13/03/2018 à 17:05, Roland Kammerer a écrit :
> > On Tue, Mar 13, 2018 at 04:57:34PM +0100, Jdt wrote:
> >> Le 13/03/2018 à 16:21, Roland Kammerer a écrit :
> >>
> >>> On Tue, Mar 13, 2018 at 04:07:17PM +0100, Jdt wrote:
>  Hi,
> 
>  We had a three nodes Proxmox cluster in V4 (jessie) with drbd from 
>  Proxmox.
>  I choose to reinitialize this cluster with Proxmox V5 (stretch) with
>  drbd from Linbit.
> 
>  I install Proxmox from the ISO image on the three nodes. Proxmox nodes
>  are not associated yet in a cluster.
>  I install drbdmanage-proxmox as indicated in
>  https://docs.linbit.com/docs/users-guide-9.0/#ch-proxmox
>  My network interfaces are well configured for drbd.
>  On the first node I create the drbdpool volume group as indicated in
>  https://docs.linbit.com/docs/users-guide-9.0/#s-dm-init-cluster
> 
>  But it's failed in initialization :
>  root@dmz-pve1:~ # drbdmanage init 192.168.2.10
> 
>  You are going to initialize a new drbdmanage cluster.
>  CAUTION! Note that:
>    * Any previous drbdmanage cluster information may be removed
>    * Any remaining resources managed by a previous drbdmanage installation
>      that still exist on this system will no longer be managed by 
>  drbdmanage
> 
>  Confirm:
> 
>    yes/no: yes
>  Error: External command failed:
>  drbdsetup new-resource .drbdctrl 0
>  Command output:
>    (stdout)
>  Command exited with exit_code 20
> 
>  Initialization failed
> >>> Failing at that early stage usually means that the wrong module is
> >>> loaded. cat /proc/drbd
> >> root@dmz-pve1:~ # cat /proc/drbd
> >> version: 8.4.7 (api:1/proto:86-101)
> >> srcversion: 2DCC561E7F1E3D63526E90D
> > Then I was right. drbdmanage always was drbd9 only. There should be a
> > drbd-dkms module in our proxmox repo. Install that one and make sure it
> > is loaded.
> >
> Thanks. I add pve-headers and drbd-dkms and I can initialize the new
> drbdmanage cluster.
> It will be nice to include this in
> https://docs.linbit.com/docs/users-guide-9.0/#ch-proxmox chapter.
> But, I got a lot of messages on my syslog about PVE storage  about every
> ten seconds :
> > Mar 19 18:54:02 dmz-pve1 pvestatd[1984]: Use of uninitialized value in
> > split at /usr/share/perl5/PVE/Storage/Custom/DRBDPlugin.pm line 217.
> > Mar 19 18:54:02 dmz-pve1 pvestatd[1984]: Use of uninitialized value
> > $free_space in multiplication (*) at
> > /usr/share/perl5/PVE/Storage/Custom/DRBDPlugin.pm line 220.
> > Mar 19 18:54:02 dmz-pve1 pvestatd[1984]: Use of uninitialized value
> > $total_space in multiplication (*) at
> > /usr/share/perl5/PVE/Storage/Custom/DRBDPlugin.pm line 221.
> > Mar 19 18:54:12 dmz-pve1 pvestatd[1984]: Use of uninitialized value in
> > split at /usr/share/perl5/PVE/Storage/Custom/DRBDPlugin.pm line 217.
> > Mar 19 18:54:12 dmz-pve1 pvestatd[1984]: Use of uninitialized value
> > $free_space in multiplication (*) at
> > /usr/share/perl5/PVE/Storage/Custom/DRBDPlugin.pm line 220.
> > Mar 19 18:54:12 dmz-pve1 pvestatd[1984]: Use of uninitialized value
> > $total_space in multiplication (*) at
> > /usr/share/perl5/PVE/Storage/Custom/DRBDPlugin.pm line 221.
> > Mar 19 18:54:22 dmz-pve1 pvestatd[1984]: Use of uninitialized value in
> > split at /usr/share/perl5/PVE/Storage/Custom/DRBDPlugin.pm line 217.
> > Mar 19 18:54:22 dmz-pve1 pvestatd[1984]: Use of uninitialized value
> > $free_space in multiplication (*) at
> > /usr/share/perl5/PVE/Storage/Custom/DRBDPlugin.pm line 220.
> > Mar 19 18:54:22 dmz-pve1 pvestatd[1984]: Use of uninitialized value
> > $total_space in multiplication (*) at
> > /usr/share/perl5/PVE/Storage/Custom/DRBDPlugin.pm line 221.
> In proxmox interface I have no idea of free space on my drbdpool VG.
> Initialize the cluster create /dev/drbdpool/.drbdctrl_0 and
> /dev/drbdpool/.drbdctrl_1.
> For the moment no cluster are created for drbd and for proxmox.

Please do not start debugging in the GUI, start at the lowest level.

- You did add other nodes besides the initial node, didn't you?
- The control volume is happy and connected to the other nodes?
- Drbdmanage is started on the other nodes?
- "drbdmanage role" on all nodes shows something meaningful?
- You can create resources on the command line and assign them?

Regards, rck
___
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user


Re: [DRBD-user] Unable to init a node

2018-03-20 Thread Shafeek Sumser
Hi

Checked whether drbd9 module is loaded.  cat /proc/drbd.  It should say
drbd9.
I think you are still using the 8.4 version.

Shafeek





On Mon, Mar 19, 2018 at 10:12 PM, Jdt 
wrote:

>
>
> Le 13/03/2018 à 17:05, Roland Kammerer a écrit :
>
> On Tue, Mar 13, 2018 at 04:57:34PM +0100, Jdt wrote:
>
> Le 13/03/2018 à 16:21, Roland Kammerer a écrit :
>
>
> On Tue, Mar 13, 2018 at 04:07:17PM +0100, Jdt wrote:
>
> Hi,
>
> We had a three nodes Proxmox cluster in V4 (jessie) with drbd from Proxmox.
> I choose to reinitialize this cluster with Proxmox V5 (stretch) with
> drbd from Linbit.
>
> I install Proxmox from the ISO image on the three nodes. Proxmox nodes
> are not associated yet in a cluster.
> I install drbdmanage-proxmox as indicated 
> inhttps://docs.linbit.com/docs/users-guide-9.0/#ch-proxmox
> My network interfaces are well configured for drbd.
> On the first node I create the drbdpool volume group as indicated 
> inhttps://docs.linbit.com/docs/users-guide-9.0/#s-dm-init-cluster
>
> But it's failed in initialization :
> root@dmz-pve1:~ # drbdmanage init 192.168.2.10
>
> You are going to initialize a new drbdmanage cluster.
> CAUTION! Note that:
>   * Any previous drbdmanage cluster information may be removed
>   * Any remaining resources managed by a previous drbdmanage installation
> that still exist on this system will no longer be managed by drbdmanage
>
> Confirm:
>
>   yes/no: yes
> Error: External command failed:
> drbdsetup new-resource .drbdctrl 0
> Command output:
>   (stdout)
> Command exited with exit_code 20
>
> Initialization failed
>
> Failing at that early stage usually means that the wrong module is
> loaded. cat /proc/drbd
>
> root@dmz-pve1:~ # cat /proc/drbd
> version: 8.4.7 (api:1/proto:86-101)
> srcversion: 2DCC561E7F1E3D63526E90D
>
> Then I was right. drbdmanage always was drbd9 only. There should be a
> drbd-dkms module in our proxmox repo. Install that one and make sure it
> is loaded.
>
>
> Thanks. I add pve-headers and drbd-dkms and I can initialize the new
> drbdmanage cluster.
> It will be nice to include this in https://docs.linbit.com/docs/
> users-guide-9.0/#ch-proxmox chapter.
> But, I got a lot of messages on my syslog about PVE storage  about every
> ten seconds :
>
> Mar 19 18:54:02 dmz-pve1 pvestatd[1984]: Use of uninitialized value in
> split at /usr/share/perl5/PVE/Storage/Custom/DRBDPlugin.pm line 217.
> Mar 19 18:54:02 dmz-pve1 pvestatd[1984]: Use of uninitialized value
> $free_space in multiplication (*) at 
> /usr/share/perl5/PVE/Storage/Custom/DRBDPlugin.pm
> line 220.
> Mar 19 18:54:02 dmz-pve1 pvestatd[1984]: Use of uninitialized value
> $total_space in multiplication (*) at 
> /usr/share/perl5/PVE/Storage/Custom/DRBDPlugin.pm
> line 221.
> Mar 19 18:54:12 dmz-pve1 pvestatd[1984]: Use of uninitialized value in
> split at /usr/share/perl5/PVE/Storage/Custom/DRBDPlugin.pm line 217.
> Mar 19 18:54:12 dmz-pve1 pvestatd[1984]: Use of uninitialized value
> $free_space in multiplication (*) at 
> /usr/share/perl5/PVE/Storage/Custom/DRBDPlugin.pm
> line 220.
> Mar 19 18:54:12 dmz-pve1 pvestatd[1984]: Use of uninitialized value
> $total_space in multiplication (*) at 
> /usr/share/perl5/PVE/Storage/Custom/DRBDPlugin.pm
> line 221.
> Mar 19 18:54:22 dmz-pve1 pvestatd[1984]: Use of uninitialized value in
> split at /usr/share/perl5/PVE/Storage/Custom/DRBDPlugin.pm line 217.
> Mar 19 18:54:22 dmz-pve1 pvestatd[1984]: Use of uninitialized value
> $free_space in multiplication (*) at 
> /usr/share/perl5/PVE/Storage/Custom/DRBDPlugin.pm
> line 220.
> Mar 19 18:54:22 dmz-pve1 pvestatd[1984]: Use of uninitialized value
> $total_space in multiplication (*) at 
> /usr/share/perl5/PVE/Storage/Custom/DRBDPlugin.pm
> line 221.
>
> In proxmox interface I have no idea of free space on my drbdpool VG.
> Initialize the cluster create /dev/drbdpool/.drbdctrl_0 and
> /dev/drbdpool/.drbdctrl_1.
> For the moment no cluster are created for drbd and for proxmox.
>
> /etc/drbdmanaged.cfg contain :
>  [LOCAL]
> storage-plugin = drbdmanage.storage.lvm_thinlv.LvmThinLv
> force=1
>
> and /etc/pve/storage.cfg :
> dir: local
> path /var/lib/vz
> content iso,vztmpl,backup
>
> drbd: drbdstorage
> content images,rootdir
> redundancy 3
>
> Any Ideas ?
> Thanks in advance
>
> Regards, JdT
>
>
>
>
>
>
>
> ___
> drbd-user mailing list
> drbd-user@lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user
>
>


-- 
Shafeek SUMSER
___
drbd-user mailing list
drbd-user@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user