I tried using the command prompt as administrator to delete it. That said, we know what the file is, what the filename is, where it is, and how it got there. That file server VM never ran on this host, we just attempted to recover files here. The file name indicated a vhdx from a file server that we had attempted to recover a couple of years ago. It also did not show a context menu for that file: It showed the file name, date, and location in the directory. Unlike other files shown in WinDirStat, the context menu is all grey: It showed that only about 125 GB was in use, the same as the used space check.Īfter some digging on the Internet, I tried choosing "Show Unknown" in the WinDirStat options, it showed a large "" file. Certainly nothing that should add up to nearly 2 TB: I also checked the Recycle Bin for all users on the machine. When I looked at the contents of the drive, it looked like only 150 GB or so should be in use. Nothing else is on the LUN, and no other devices can connect to that LUN. The drive is connected via iSCSI to a QNAP LUN. The actual shared files are not in this folder. The drive holds the Hyper-V files and the C: drive of a file server. While looking at one of the Hyper-V servers, I noted that it had a drive that looked like it was "too full".
I set out to document disk space usage among the servers. The process will likely take a couple of moves of Hyper-V guests in order to accomplish. We were looking for a way to better allocate file system resources to these servers. A client of ours has 4 standalone Hyper-V servers.
0 kommentar(er)
