HAST & NFS Feature Request

[discostur]

Hi nas4free Team,

i would like to suggest you two improvements for one of your next nas4free builds:

1. HAST
The possibility to set the hast level (primary or secondary) on the web-gui. Now you have to do that on the command line (hastctl role primary disk1 (secondary)). Additionally you can insert a button for initialize the hast disks (hastctl role init disk1, hastctl create disk1).
That would be nice and could save some time.

2. NFS
If you have a HAST & CARP failover configuration with two hosts, host a and host b and you want to share some folders via NFS, you should have the possibility to bind the NFS server to a special ip address (CARP ip address). I don't know if its right, but something like these must be the right way: http://doc.freenas.org/index.php/NFS
If host a goes down, the NFS share should be available under the same ip adress (CARP) on host b.

EDIT: Maybe like when you set up the cifs/smb share, you can select on which interface you like to share the service

I would appreciate to hear from you.
Thanks

[discostur]

@ 2. NFS

I did some further testing with the NFS & Carp stuff and you can mount the NFS share via the CARP-ip-adress without binding the nfs-server to a special ip address. the server listens on all ip addresses by default.

BUT

If you mount the share via the CARP-ip-address i got horrible slow read / write speeds (100-500kb / sec, GB-Lan). sometimes, if i only do "ls -l" on the share, the share doesn't respond for about 2-5 minutes.
If i mount the same share via the normal ip address of the node, everything works like it should. There must be some bugs or failure configuration with the nfs-server ...

Maybe you can test this scenario on our own and fix it in further versions of nas4free.

[discostur]

Update #3:

It is definitely the carp interface. if i try to ping the virtual interface, i got those statistics:

141 packets transmitted, 47 received, 66% packet loss, time 140393ms
rtt min/avg/max/mdev = 0.385/0.524/0.620/0.055 ms

This is if i try to ping the virtual carp interface from the second nas4free host, the backup host. Something seems to be wrong with the carp-interface in the actual #573 nas4free build...

my interface is configured as followed:

carp0: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
inet 192.168.xxx.xxx netmask 0xfffffc00
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
carp: MASTER vhid 1 advbase 1 advskew 0

[discostur]

Update #4

I think i finally fixed the problem! The two machines were virtualized on a Proxmox host system. Yesterday, i tested the setup on real hardware and it seemed to run smoothly. I'll do further testing...

Please don't forget my point number one in the first post, this is still a good feature request i think. Thanks