TopicWindows Server →
⌚ About 2 min read
Quickly display the space used and available on volumes of a Windows server.
Avant de commencer : adaptez toujours les commandes et manipulations à votre environnement. Sur un système de production, prévoyez une backup ou un retour arrière lorsque l’action peut modifier la configuration.
Étapes à suivre
-
1
Open Power Shell
Run Windows Terminal or Power Shell.
-
2
List Volumes.
Use the Beh-Volume.
-
3
View sizes in Go.
Use a Power Shell command with column calculation.
-
4
Identify critical volumes.
Watch system, log, base and backup volumes in particular.
Commands utiles
Well-Volume, How-Object DriveLetter, Select-Object DriveLetter, File (2003)Label,@{N='LibreGo';E={.[math]::Round($_.SizeRemaining/1GB,2)}},@{N='TailleGo';E={.[math]::Round($_.Size/1GB,2)}.
À retenir
- System disk saturation can cause many malfunctions.
- Identify the cause before deleting files.
Windows disk space: identify the volume, not just C:
Technical checkpoints
- Get-Volume distinguishes capacity, free space and health; mount points without drive letters can also be affected.
- VSS, logs, Windows Update, dumps and user profiles are frequent consumers to examine separately.
- A nearly full volume can trigger VSS, database, spooler or update failures before reaching exactly zero bytes.
Quick view
List all volumes then target the responsible directories instead of deleting randomly.
Get-Volume | Sort-Object DriveLetter
Get-PSDrive -PSProvider FileSystemTopic-specific pitfalls
- Manually cleaning WinSxS or deleting VSS files without a method can destabilize the system.
- Explore size does not always account for protected or reserved files.
How to validate
- The volume regains headroom appropriate to its workload and no storage alert persists.
- The growth cause is identified to prevent the volume filling again.