blob: 686941399f40aadf0f5127a9a1e4d096a6d08cf5 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
|
fstrim not working with image mounted to path?
guest os: windows server standard 2016
qemu agent version 100.0.0
os supports trimming
path mounted image does not support trimming
C:\Users\Administrator>fsutil behavior query disabledeletenotify
NTFS DisableDeleteNotify = 0
ReFS DisableDeleteNotify = 1
[@ ~]# virsh qemu-agent-command vps-xxx '{"execute":"guest-fstrim"}'
{"return":{"paths":[{"path":"C:\\"},{"path":"C:\\Program Files\\Microsoft\\Exchange Server\\V15\\Mailbox\\xxxx\\","error":"The given volume path is invalid. (0x89000001)"}]}}
Looks like the fstrim does not like/check images mounted on a path? Nor detects if image trimming is supported. xxxx is a ReFS mounted image without trimming support.
If I enable trimming on the ReFS image, and configure it win2016, the result is still the same.
C:\Users\Administrator>fsutil behavior query disabledeletenotify
NTFS DisableDeleteNotify = 0
ReFS DisableDeleteNotify = 0
[root@c03 ~]# virsh qemu-agent-command vps-xxx '{"execute":"guest-fstrim"}'
{"return":{"paths":[{"path":"C:\\"},{"path":"C:\\Program Files\\Microsoft\\Exchange Server\\V15\\Mailbox\\xxxx\\","error":"The given volume path is invalid. (0x89000001)"}]}}
PS. tried this on a win 2016 std server with just one fs, no problems then.
|