Ich hab zumindest bei dem Shop schon andere Hardware gekauft (Kühlkörper und Lüfter für Server).
ich wär mir bei denen auf jeden Fall sicherer als bei ebay :)
Das mit der Migration wird denke ich nicht so einfach.
Ich muss gestehen, bei dem...
AFAIU, you increased using PVE's GUI. If yes, the fs in the VM wasn't increased. Which is good :). Don't start the VM for now.
Now be warned: make yourself very sure which "giga"bytes are used by the GUI and which ones by the lvresize! Binary or...
There is a non-zero chance that deleting a chain of snapshots will break things.
I would also do an in-vm backup of the current disk state (bare metal) in case you need to restore it like a physical box. Veeam free agent is good for this if the...
Because I would not expect that vlan to be accessible to virtual machines. adjust that as appropriate.
Far be it from me to dissuade you from pursuing NIC level fault tolerance. Suffice it to say I dont; I care about path redundancy- a switch...
Sorry, I was not perfectly clear. The disk was 500GB and I wanted to reduce it to 200GB (there is 40GB data on it after 3 years), so initially I wanted a 300GB reduction. But I accidentally increased it (via the PVE Web GUI) by 200GB to 700GB...
I think Expectations are on the Floor right now :p.
You didn't read my Reply: What I provided is the Configuration of one Proxmox VE Host, but it's fairly representative across the Board with my other Servers.
Depending on which specific...
I'm confused. were you not asking for help troubleshooting this?
SQL performance is a function of two things- query efficiency and disk IO latency and IOPs. since we know your queries are the same, what remains is the storage.
How did you have...
@gctwnl
I'm quite confused by your story.
1) Disk was 500 GB. You increased it to 700 GB. Now you would like to shrink it by 300 GB. That would give 700-300=400 GB.
500 != 400.
2) BUT it the command you quote, you're trying to remove 500 GB.
300...
Hi,
please open a separate thread and provide more details. Is the upload done on the same node you are logged in or another one? Is there any information in the system logs/journal? Note that 9.1.2 is not the latest available version (anymore).
cite your sources please. 5 monitors are "suggested" with a high number of OSD nodes.
with a typical crush rule of 3:2, this only makes sense IF you have dedicated monitor nodes (eg, no OSD) AND you have environmental issues that take your nodes...