Solved Something's Gobbling my Disk space but can't see it

[jimbo45]

Hi all
something seems to have consumed a large amount of the "C" drive (23% of 72 GB) but I can't see what it is.

Any idea how to see what the files are

screenshot enc
all the other nodes in the tree expand OK so I can see what's in them but this one just says [files] and 23 %. the second screen shot shows the amount of space being used by these [files] ??


Cheers
jimbo

 

[Bill2]

Go through this first.

http://www.sevenforums.com/tutorials/129976-hard-disk-space-free-up-recover.html

 

[kado897]

There are a number of system files which take a lot of space. Some of these are. These are normally marked as Hidden and System.

1. Page File
2. Hibernation file
3. Filesystem metadata files.
4. Windows shadow storage.

 

[jimbo45]

Hi all
solved problem

Was copying with Windows explorer nearly 1 TB of music / audio files on to my local computer from a Network drive. Windows explorer needed a huge amount of workspace to copy these files --- not the best way of moving vast amounts of data -- but it's the weekend so I don't have to watch rhe screen.

Cheers

jimbo

 

[karlsnooks]

jimbo,
many thanks for getting back with the cause.

If you have such a massive copy ahead again, let me recommend using RoboCopy.

Despite the multitude of options, a simple straight-forward copy, as an example,:
Go to a cmd shell prompt and type
Robocopy R:\Music T:\Music /MIR

R and T are two drive letters I pulled out of the air and
Music is a folder I pulled out of the air.

After trying many things, I now use RoboCopy exclusively for data backups and transfers.

I've got a simple batch file that I run (last statement is pause) so I can take a quick look at the screen output.

I only use the /MIR when I want to make sure that all old is gone and the new copied over,otherwise, the /E option when I just want to transfer over the updated and new files.

 

[mjf]

I've been curious to know why a "high level" folder copy from one partition to another incurs so much overhead.

 

[karlsnooks]

probably because Microsoft employs neophyte programmers.

 

[kado897]

probably because Microsoft employs neophyte programmers.

:roflmao:

 

[Bare Foot Kid]

I thought Karl worked for MS.

 

[karlsnooks]

You really know how to hurt a guy.

 

[jimbo45]

Hi there
actually reserving a large amount of data for this type of operation is GOOD programming


Since Disk READ is fairly slow - you can speed up the process by reading HUGE chunks of data from the source drive and writing to the target drive "asynchronously".

You can also "re-block" the data to the optimum size for physical data transfer to the output device which might have a totally different specification from the source disk.

This means of course that the output disk can be written to INDEPENDENTLY of the data transfer rate from the source (once you've filled the "Buffer" of course).

If you didn't employ techniques like this you would have to wait to complete a READ from the input device before you could do a WRITE to the output device -- and then you would also have to wait for the OUTPUT device WRITE to have finished before getting the next READ request.

I'd hate to be using a Cash machine if you programmed the I/O to run totally sequentially !!!!!.
It would take from now until AFTER LONODON'S Olympic games in 2012 to just get some cash from a machine programmed like that. !!!!!


It's been DONKEYS YEARS since I did anything with Operating systems but the principle is still the same -- allow as much system throughput as possible CONCURRENTLY.

Cheers
jimbo

 

[karlsnooks]

the principle is correct. The implementation is evidently faulty. Hard to believe but the first time I programmed overlapped input, processing, output was back in 1962.

 

[Britton30]

Now if I knew what you were talking about...