Search results

With those settings I'm able to open the file directly from the browser, from nautilus or via xdg-open. If your system uses something else it ignores the xdg settings and does something funky. Not that that would be a big surprise for *buntu ;)

It just means that that *buntu cares more about magic numbers than filename extensions. Which is good, I guess. The stuff after xdg-open download tells you that you have a bunch of invalid files. You can see if they belong to any package and update the package, if possible, or delete them...

If you download the file and run file download what does it say? And what does xdg-open download do?

I think that only means that they haven't tested that setup and aren't obliged to help you with any issues you might encounter. You should be free to try, though.

I was under the impression that that is what's required. What a difference a single word can make :D Chrome lets xdg-open determine the default application. So either write a new entry in $XDG_CONFIG_HOME/mimeapps.list or add a respective entry in the spice-viewer.desktop file. Details here.

# pvesm help add […] -is_mountpoint <boolean> (default=no) Assume the directory is an externally managed mountpoint. If nothing is mounted the storage will be considered offline. […]

Would this help?

Great. Please don't forget to mark the thread as 'solved' so others with a similar problem may easily find a possible solution. That's enough storage for a few games, or whatever you're hoarding there ;)

Ok, you're getting a timeout. To check whether the storage is online we start showmount with a timeout of 2 seconds. So the next question is: "Why is that NFS so slow?" It may be DNS related. Could you make an entry in /etc/hosts for the client machine in the NFS server host?

Please post the output of # time pvesm nfsscan 192.168.0.3

The only thing I see is that you mount manually with vers=4 but configure the storage with vers=3. You probably want to use version 4.

What does # pvesm nfsscan show? You followed the wiki?

So yeah, at this point it may be easier to scrap and recreate. And keep in mind to keep you cluster quorate at all times. If you need to recreate monitors, do one at a time.

And I assume the injection as well as the createmon are executed on sys8?

It's basically telling you that the monitor doesn't exist. So you need to create it.

You really shouldn't run commands without understanding what they do. Your monmap contains two mons. 1 and sys8. So the IPs they are assigned should be the nodes that run those monitors.

If only mon@1 is running that's no surprise. mon@sys8 has to run too, for the cluster to be quorate.

USAGE: pveceph stop [<service>] Stop ceph services. <service> (mon|mds|osd|mgr)\.[A-Za-z0-9\-]{1,32} Ceph service name.

has it?

Did you destroy all monitors? Because then your cluster is no longer quorate. Then you have to extract the monmap, edit it to contain the monitors you want (at least a quorate amount) and inject it back into all nodes.