to at least consider adding it.
There is also ESOS (http://www.esos-project.com/) what is basically SCST
(and ZFS if built with it) that is very stable and really painless to
setup and maintain.
--
Mit freundlichen Grüßen,
*Alexander Schmid*
*Anschrift:*
Alexander Schmid
Modula Shop Systems
___
pve-devel mailing list
pve-devel@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
--
Mit freundlichen Grüßen,
*Alexander Schmid*
*Anschrift:*
Alexander Schmid
Modula Shop Systems
Roßmarkt 2
87700 Memmingen
Germany
Tel: +49 - (0)8331 - 6408716
Mobile: +49
ext4 on mdraid would be really nice alternative
proven to work for decades now and small footprint
Yes! EXT4 for are very stable, but leak something advanced tools such as
compression, dedup and RAID... Well AFAIK, the ext4 doesn't has this
features... Perhaps am I wrong?
mdadm will do
ext4 on mdraid would be really nice alternative
proven to work for decades now and small footprint
Am 22.02.2018 um 17:55 schrieb Dietmar Maurer:
I have here a bounce of friends complain about ZFS, which is a memory eater
- and killer!
So, I wonder if Proxmox consider others alternatives,
at the traffic.
Alex
Just in the process of getting
Am 20.09.17 um 12:04 schrieb Thomas Lamprecht:
Hi,
On 09/20/2017 11:55 AM, Alexander Schmid wrote:
Hello,
i just noticed that CONFIG_MLX4_EN_VXLAN, what is important for vxlan
hw offload with ConnectX-3, is not set anymore.
The reason
Hello,
i just noticed that CONFIG_MLX4_EN_VXLAN, what is important for vxlan hw
offload with ConnectX-3, is not set anymore.
I see it on kernel 4.4.15-1-pve:
# uname -a
Linux cl1-1-s0c1 4.4.15-1-pve #1 SMP Thu Jul 28 10:54:13 CEST 2016
x86_64 GNU/Linux
# cat /boot/config-`uname -r`|grep
For the Custom Storage Plugins it would be great to have a way for the
plugin to inject some ExtJS.
So, the Plugin could add a Controller that registers with some component
queries to events in the GUI and i.e. show a meaninful dialog in
Datacenter / Storage.
Of course, the Plugin-Developer
for the qemu commands.
Alex
Am 17.05.2017 um 07:32 schrieb Alexander Schmid:
Hello,
i just noticed (after finally sniffing iscsi-traffic) that qemu-img
uses a default initiator name of iqn.2008-11.org.linux-kvm rather than
the value from /etc/iscsi/initiatorname.iscsi
Guess this should either
Hello,
i just noticed (after finally sniffing iscsi-traffic) that qemu-img uses
a default initiator name of iqn.2008-11.org.linux-kvm rather than the
value from /etc/iscsi/initiatorname.iscsi
Guess this should either be in the docs that acces to both initiators on
the target must be
to the zfsplugin in general.
I think it should work with the bundled iscsi-targets, too.
Best regards,
Alex
Am 13.01.17 um 10:55 schrieb Alexander Schmid:
Am 13.01.17 um 10:44 schrieb Dietmar Maurer:
I also extended ZFSPlugin to allow access to Snapshots (via zfs
snapshot
+ clone + iSCISI
I have implemented a PlugIn for ZFS on SCST and know of an
implementation for ZFS on FreeNAS via it`s Rest-API.
I think it`s best to inherit from Plugin.pm or a subclass, i.e.
ZFSPlugin.pm
If there is any interest i could provide the SCST - Plugin as Sample,
and maybe also the FreeNAS (had
Hello,
another option for 2-Node HA would be what HA-Lizzard for XenServer does.
Basically they test if some external ip`s (e.g. storage/switches) can be
reached to ensure quorum/majority in the two-node setup. This is maybe
not the best solution but way better than running into split-brain.
12 matches
Mail list logo
