Of course the verification will still need to read data from the hdd and thus won't profit as much from the metadata on the special device as the garbage collection job (who mainly needs to read and write metadata). But it still profits from it...
When trying to migrate one of my VMs to another host, i somehow managed to lock the VM.
This is what i get when I try to migrate it to another host.
Any idea how to get it unlocked?
That's right I did not do those pings from my PVE host, and yes 10.0.0.21 is the laptop proxmox is running on.
(I meant to say a machine on my network my mistake.)
that’s right I originally didn’t ping these from the PVE host rather I did it...
You can do similar tests from your desktop. If you get different results, chances are that the port that a device is attached to, matters. You could then test to see which ports do not work as "LAN" ports - either, because they are defective or...
The tests should show connectivity on your LAN between proxmox and other targets, first to itself, then to the router, then to your desktop.
A successful ping to itself is indispensable, a ping to the router should be possible (because other...
The hardware tabwould also be cluttered as explained by Andreas Steinel in the bug ticket:
And since temperature monitoring is easily available by using a real monitoring software it's not even needed.
Did you try those pings from your PVE host? I assume not, since 10.0.0.21 is your proxmox (which is on the laptop?), so it must be able to ping itself, but you say it is unreachable.
I must assume you did this from your desktop at 10.0.0.19...
I believe my router isn’t seeing my proxmox machine and that’s why I can’t connect.
I tested all 4 ports on the back of the router, unless they’re all guest I’m unsure on how to change that.
Router is correct
The 10.0.0.19 is my desktop, I was just scanning all the devices on my network to check if anything has taken 10.0.0.21
Proxmox is correct
For the earlier post
10.0.0.21 is unreachable
10.0.0.1 had a successful ping
10.0.0.156...
Hope this helps:
I find using https://github.com/digitalocean/ceph_exporter
With Grafana Dashboards:
https://grafana.com/grafana/dashboards/926-ceph-pools/
https://grafana.com/grafana/dashboards/923-ceph-osd/...
Once you have verified that the machines on your network can see one another, you should also be able to open a browser on your laptop and entering the URL https://10.0.0.21:8006 (note the s in https) from there, regardless of any internet...
So, what are your IP addresses? I assume:
router 10.0.0.1
laptop 10.0.0.19 (from the sucessful network scan with nmap you posted)
proxmox 10.0.0.21 (from your ping test)
You should repeat the ping test to all three targets I quote in #11, plus...
My overall issue is that I can’t connect to the browser interface.
Those other devices can’t connect to the internet, I was just doing a test if it can even connect correctly.
I’m unsure if the router and laptop can connect to each other...
With the tunable verification settings we went from a 4 hour verification process to 30 mins. Quite the improvement! :)
5x 61.44TB Solidigm in a RAIDz1 - Which in the past a benchmark showed about 30GB/s reads.
I'm seeing crazy low performance in Ceph.
I've traced it to OSD's sometimes being very slow...see below.
In 3 tests, the first is fairly slow, then fast (as fast as I expect this OSD to be), then the 3rd is crazy slow.
root@pm3:~# ceph tell...
I've had more issues after leaving this with "gro-off". One day backup runs fine, the other day it runs slow (I found it dragging on for 2 days with no indication of ever finishing). So I changed MTU to 1500 and didn't have any issues with...