Search results

Great information (in particular the second bug report) thanks! rob

Maybe this chapter from drbd9 can add some information: https://www.drbd.org/en/doc/users-guide-90/s-drbdmanage-storage-plugins And also the previous: https://www.drbd.org/en/doc/users-guide-90/ch-drbdmanage-more#s-drbdmanage-free-space bye, rob

Check the source code: /usr/share/perl5/PVE/Storage/DRBDPlugin.pm It's not a GUI (pve perl code layer, actually) problem. You can get free space directly from drbdmanged, via "drbdmanage list-nodes" command, and see that pve is reporting what drbd is saying.

The new Gui does not load under ubuntu-touch native browser (webkit based)

Update: it turns out that it doesn't work so well: I had a lot of strange connection problems between drbd9 cluster nodes, and i ended up to connect them via a dedicated switch (no more interface-to-interface dedicated connection). My question reasoning about connection problems is: "To what...

I'm under pve-no-subscription, and received the new gui anyway. Was this intended? Wery well done, in any case. rob

Yes, I've done more or less the same: === node "uno" (10.1.1.1) === auto eth1 iface eth1 inet static address 10.1.1.1 netmask 255.255.255.255 up ip route add 10.1.1.2 via 10.1.1.1 dev eth1 auto eth2 iface eth2 inet static address 10.1.1.1 netmask 255.255.255.255 up ip route add 10.1.1.3 via...

Yes, i tried for instance: 1) Add ip to both eth0 and eth1 (removing the netmask, this implies /32 and suppress creation of network routing) ip addr add 192.168.0.1 dev eth2 ip addr add 192.168.0.1 dev eth3 2) Add explicit routes to 192.168.0.2, 192.168.0.3 (for instance): ip route add...

I have to think more on this, but probably it's both matter to remove automatic network routing and add some explicit one. Will try ... Thanks, rob

Ok, I have not explained clearly my intention: I want to avoid to use a dedicated switch to connect the six interfaces, providing a phisical path (cable) for every connection in the mesh (three cables). I don't know if this fits in your scenario, but on the Chapter 5.1.4 of DRBD9 docs they...

Hello, I would like to create a pve4 three-node setup with drbd9 storage. I have read the related proxmox wiki article, and the documentation about drbd9 on the Linbit website. If I understand well, the new drbdmanage tool is a way to simplfy drbd configuration, and involves the creation of...

Very interesting, thanks for sharing! rob

/dev/mapper/img1-vm--100--disk--1p1 /tmp/100 ext4 rw,relatime,barrier=0,data=ordered 0 0 # pveperf /tmp/100 CPU BOGOMIPS: 38397.44 REGEX/SECOND: 369248 HD SIZE: 9.39 GB (/dev/mapper/img1-vm--100--disk--1p1) BUFFERED READS: 179.24 MB/sec AVERAGE SEEK TIME: 7.58 ms...

nobarrier (or the equivalent barrier=0) makes a lot of difference, in terms of fsyncs/sec: with barrier=0, from /proc/mounts: /dev/mapper/pve-data /var/lib/vz ext3 rw,relatime,errors=continue,user_xattr,acl,barrier=0,data=ordered 0 0 # pveperf /var/lib/vz CPU BOGOMIPS: 38397.44...

Hello, I've recently read this article (found the link on this forum): "The end of block barriers" http://lwn.net/Articles/400541/ It explains fairly clearly why enabling barriers is so bad for fsync performance, (try pveperf on a filesystem with and without barriers enabled), and why...

Ok macday; I hope that with a little help you will be able to quickly overcome all the problems, and at the end no payment will be necessary :-) rob

Sorry for being so late; I think I can help you if you ask here specific questions, about problems found following the howto. Frankly, having my homework to do, I cannot afford providing you free "on site" support. By the way, the howto was repeatedly updated basing on daily usage by other...

Hello mac I will be glad to help; which part of the howto on the wiki is unclear? rob

Re: Low performance of data transfer over cifs mounts We did the same, being currently unable to upgrade that host to squeeze. rob

Re: Low performance of data transfer over cifs mounts I confirm, too. linux-image-3.2.0-0.bpo.3-amd64 from squeeze-backports does not exibit the issue. rob