Yes, this one works!
I tried it on 1 host on my staging environment... the second partition of the drive finally unfolds!
Is there some testing with it that needs to be done before it can be taken in production?
Martijn
Too bad, M$ did not release any recent ReFS info for a linux driver ...
Tried 3 different sizes ... all worked well... given I used only some txt files to use during restore testing.
Going to start over with dedup as well while throwing a few gb's of data on it as well...
Damn... this one works:
Created the VM from the same original template:
-add virtio device (TST 200GB), full (no discard) (later changed to discard)
-in windows: disk manager (old school NT4) selected gpt device
-format: NTFS from default to 16 KB allocation unit (quick format)
-made a...
Good morning,
i'll create a new machine (smaller one) with the same steps (they were manual but i think i can manage).
This will speed up the backup attempt.
Unfortuantely... after removing the windows roles, duplicating the data, making a new backup .... the file restore returns the error.
If i can help, i would be glad to do some extra tests.
regards, Martijn
It took almost 4 days to dedup the data on the clone VM.
https://learn.microsoft.com/en-us/answers/questions/1352079/turn-off-dedup-and-delete-chunkstore
Made a new backup from it... no success... even after a reboot.
So now making a fresh backup... back in a jiffy (20 hours or so on those...
Hmmz.. I have to upgrade again then, strange...
Did not see it coming, of course the machiine is in use... too many applications have a permanent mount to it :-(
By any chance, could windows dedup be the cause?
Found it, sorry ... was looking at another host than my browser was leaning focusing at.
It is the qemu.log as attached:
There is some complaining about a corrupt $MFT, but chkdsk cannot find anything.
After replacing our backup host (it got a corrupt controller) i finally managed to do the upgrade to 8.1.3 (PVE)
Unfortunately the message remains. (see attachment)
What could it be? Maybe the clustersize of 16KB?
Had to replace the backuphost (hardware failure). Initial backup has been made and problem still exists with PBS 3.1.2. Still going to research this after upgrading PVE to 8.1.3
Hi,
we just moved our biggest Windows fileserver from VMware to proxmox ..
Before moving 20+TB we discovered not to use REFS as this would give problems to restore files from it.
So we build an NTFS volume for it with clustersize 16KB to exceed the standard 16TB volume limit on 4KB size.
Now...
Many postings about this on the google result-pages but no clear solution.
It happens on most agents. Don't know if it happens after virtual migration(s).
systemctl restart qemu-guest-agent fixes it and now i'm thinking to get this scheduled on all our vm's if "dead".
What could be the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.