I was not able to find what was keeping the target busy. I did a lazy unmount "umount -l", since then i have no new dmesg lines, but the memory isn`t freed. So i`m not sure, if this is/was the reason for the Problem. Other Servers in the pool have this same old mount, but do not use this much of RAM. But i will check cifs mounts, the next time i see this Problem. I`m still looking for a way how to find out what is using this memory, when there is no process visible which uses it. Even though this may be a common Linux question

@Danp yes it's the same on XOA in trial mode latest patched.

Hard to say from just a screenshot. What version of XO are you running? How long did you wait for the logs to load? Did you try refreshing the page? FWIW, I've noticed that XO seems to take longer to load this page than it did previously. P.S. Technically, you aren't running XOA (the pre-built XO appliance).

@Marc-pezin said in XCP-ng and Linbit alliance: @markhewitt1978 We are currently working on a new version of XOSAN but that won't be based on DRBD. It will likely be something completely new! Ah interesting, both good developments.

its still there ie the host is still atached to that vdi im thinking this is the issue why my backups wont run anymore if not i will do it on the xen server cli, but it would be nice to know why this isnt working

It's a bit less flexible than using a NFS share (because it's easier in case of XOA loss, to just reconnect to a NFS and fine all your backup), than having to reconnect the iSCSI to your XOA. But it will work, yes.

Same answer as the other topic, as I exactly said in my previous post here: you can solve this in XO, Dashboard/health view.

I've been spending some time on it for the last few nights, and my skills are improving little by little. I think Ubuntu desktop was the closest I got to functional, there is a custom image for the Rpi3b+ that I found and it was one of the attempts that got to trying to start the XO-server service and failed. I was never able to get the xo-server to start manually either and the log files didn't give me anything I understood. One of the versions that worked the least was CentOS 7 for RPi, node.js is not available for it in the normal repos. I have more experience with CentOS from a few years ago and more comfortable with it, may have to look into compiling all the dependencies from source to see if I can make it work. I think an RPi 4b with 2gb or 4gb of RAM might be a better choice, but I have the 3b+.

It's simple, you can't for now. It's the management network only. What you can do, is to add a network to XO that will be inside the network you want, so at least the link between XO and the storage/backup will be the one you want.

Have you refresh your broswer tab? Have you tried to disconnect/reconnect the pool in Settings/servers?

Hey! Thanks for the feedback Keep us posted if you have any issues!

@jmccoy555 Thanks, I was going mad.

@olivierlambert Thank you. All back to normal now

Oh yes, sorry I misread the question. Indeed, XCP-ng Center is another thing, feel free to ask on the Github repo: https://github.com/xcp-ng/xenadmin/

Thanks! Just needed to be 200% sure!

You need a space between the URL and the user name.

This guide shows an old UI of XO, but you can always set the HA for the VM in its Advanced Tab. HA at the pool level might be enabled using the command displayed in the blog post. So far enabling HA on the pool level isn't exposed in XO because HA is causing more issues than it solves in general. If you decide to enable it on the CLI, it means that you probably understand what you do. If you don't know where to find a SR UUID, using HA might expose you to VERY bad experience. BTW, you can find it in SR view, click on the SR you want to use as HA SR, you'll see the UUID just beneath the name. As someone said in this forum few weeks ago: Everybody wants HA but not everyone needs it

Also please note that's not a guarantee to boot the VM on this host. In fact, there's no way to be 100% sure it will. It's just than now XCP-ng will do its best to honor this. But eg, if there's not enough RAM on the host, then it will boot on another host of the pool.

I think, solution you are looking for is direct disk access. It's possible. I use it for my file server VM (FreeNAS) with five 4TB wd red drives (zfs). Passthrough entire PCI storage card is better, but even cheap server motherboards have 6 sata channels (one for dom0 ssd, and five for file server storage). This is my example (and my UUIDs) mkdir /srv/direct-sata_sr xe sr-create name-label=”Direct SATA SR” name-description=”SATA links to passthrough direct to VMs” type=udev content-type=disk device-config:location=/srv/direct-sata_sr New UUID generated on sr creation ba9b124c-c5ac-2c0b-7b1f-014d9cezzzzz ln -s /dev/disk/by-id/<disk id> /srv/direct-sata_sr/<disk id> ln -s /dev/disk/by-id/ata-WDC_WD5000BEVT-26A0RT0_WD-WXE1A10V7603 /srv/direct-sata_sr/ata-WDC_WD5000BEVT-26A0RT0_WD-WXE1A10V7603 xe sr-scan uuid=ba9b124c-c5ac-2c0b-7b1f-014d9cezzzzz xe vdi-list sr-uuid=ba9b124c-c5ac-2c0b-7b1f-014d9cezzzzz Good luck.

@olivierlambert Awesome and thank you for the follow-up.