free and used space on HD

[Bertoldino]

hi
how can i know via commandline how much space, for a volume, is...

total,
used,
free?



i thought to use "DU" from winternals, but there is a problem because runs
the EULA, so if i send a command remotely for the first time, process is
locked, waiting for a user to accept that @##! eula!

but maybe the system itself can give easily these informations

thanks for your time

 

[Edwin vMierlo [MVP]]

hi
how can i know via commandline how much space, for a volume, is...

total,
used,
free?

chkdsk will give you something like this:

36861110 KB total disk space.
14032492 KB in 166663 files.
39824 KB in 6857 indexes.
0 KB in bad sectors.
198570 KB in use by the system.
22496 KB occupied by the log file.
22590224 KB available on disk.

4096 bytes in each allocation unit.
9215277 total allocation units on disk.
5647556 allocation units available on disk.

any other tool will probably not be accurate if it uses File System access,
this due to folders/files which have security set, if you don't have the
security, then you cannot enumerate that file

HTH,
Edwin.

 

[Bertoldino]

chkdsk will give you something like this:

any other tool will probably not be accurate if it uses File System
access, this due to folders/files which have security set, if you
don't have the security, then you cannot enumerate that file

HTH,
Edwin.

thanks edwin!

 

[Bertoldino]

chkdsk will give you something like this:

is it a problem if i request a CHKDSK on a remote workstation regardless of
what is the user doing?

 

[Pegasus \(MVP\)]

is it a problem if i request a CHKDSK on a remote workstation regardless
of
what is the user doing?

Chkdsk.exe will report on local machines only. If you want to run
it on remote machines then you must use psexec.exe (www.sysinternals.com).
You can run this command without interfering with the user that is
currently logged on.

 

[Bertoldino]

Pegasus (MVP) wrote:

Chkdsk.exe will report on local machines only. If you want to run
it on remote machines then you must use psexec.exe
(www.sysinternals.com). You can run this command without interfering
with the user that is currently logged on.

yes pegasus, i meant to do that.
sorry, i wasn't clear

and thanks for your answer!

 

[Edwin vMierlo [MVP]]

You can run this command without interfering with the user that is
currently logged on.

It will obviously increase the load (IO) on the disk while checking, and IO
bound programs might experience a slight slow down in performance. I would
run this in a non-busy period on users machines, e.g. when they are at lunch
or in the evening.

rgds,
Edwin.