L
LASuV
Hi there,
i have a realy mysterious problem.
My fileserver (Vmware-virtual Windows Server 2012 R2 a Domain-Member) says in System-Log Source "srv" warns about low disk space on drive c:
Some days later source "NETLOGON" can't write on \system32\config\netlogon.ftl because of disk space.
And Veeam Backup can't backup the server because it can't copy some Agent Files on die Fileserver because of low disk space.
Deduplication role is installed for Data-Volume F: but of course not activated for drive c:
Quotas are activated for Home-Volume H: but no Deduplication.
Because I had this problem earlier, a few weeks before I did run chkdsk /R on drive c:. Result was a few "unfreed" cluster. I deleted some files to increase free space from 6 GB free to 21 GB free. For a while all was ok. But now problem repeats.
BUT:I can copy an 5 GB File to drive c: without any problem.
Properties of drive C: says 21 GB free.
Also TreeSize says 21 GB free.
Any Ideas? (sorry for bad english) Thanks.
(I cant attach images actually)
Continue reading...
i have a realy mysterious problem.
My fileserver (Vmware-virtual Windows Server 2012 R2 a Domain-Member) says in System-Log Source "srv" warns about low disk space on drive c:
Some days later source "NETLOGON" can't write on \system32\config\netlogon.ftl because of disk space.
And Veeam Backup can't backup the server because it can't copy some Agent Files on die Fileserver because of low disk space.
Deduplication role is installed for Data-Volume F: but of course not activated for drive c:
Quotas are activated for Home-Volume H: but no Deduplication.
Because I had this problem earlier, a few weeks before I did run chkdsk /R on drive c:. Result was a few "unfreed" cluster. I deleted some files to increase free space from 6 GB free to 21 GB free. For a while all was ok. But now problem repeats.
BUT:I can copy an 5 GB File to drive c: without any problem.
Properties of drive C: says 21 GB free.
Also TreeSize says 21 GB free.
Any Ideas? (sorry for bad english) Thanks.
(I cant attach images actually)
Continue reading...