By using this option ntfsresize will determine the theoretically smallest
shrunken filesystem size supported. Most of the time the result is the space
already used on the filesystem. Ntfsresize will refuse shrinking to a
smaller size than what you got by this option and depending on several
factors it might be unable to shrink very close to this theoretical
size. Although the integrity of your data should be never in risk,
its still strongly recommended to make a test run by using the
--no-action option before real resizing.
Practically the smallest shrunken size generally is at around "used space" + (20-200 MB). Please also take into account that Windows might need about 50-100 MB free space left to boot safely.
This option never causes any changes to the filesystem, the partition is opened read-only.
|-s, --size SIZE[k|M|G]|
|Resize filesystem to SIZE[k|M|G] bytes. The optional modifiers k, M, G mean the SIZE parameter is given in kilo-, mega- or gigabytes respectively. Conforming to standards, k=10^3, M=10^6 and G=10^9. Use this option with --no-action first.|
Forces ntfsresize to proceed with the resize operation even if the filesystem
is marked for consistency check.
Please note, ntfsresize always marks the filesystem for consistency check before a real resize operation and it leaves that way for extra safety. Thus if NTFS was marked by ntfsresize then its safe to use this option. If you need to resize several times without booting into Windows between each resizing steps then you must use this option.
|Use this option to make a test run before doing the real resize operation. Volume will be opened read-only and ntfsresize displays what it would do if it were to resize the filesystem. Continue with the real resizing only if the test run passed.|
Support disks having hardware errors, bad sectors with those
ntfsresize would refuse to work by default.
Prior using this option, its strongly recommended to make a backup by ntfsclone(8) using the --rescue option, then running chkdsk /f /r volume: on Windows from the command line. If the disk guarantee is still valid then replace it. Its defected. Please also note, that no software can repair these type of hardware errors. The most what they can do is to work around the permanent defects.
This option doesnt have any effect if the disk is flawless.
|Dont show progress bars.|
|Print the version number of ntfsresize and exit.|
|-h, --help||Display help and exit.|
The exit code is 0 on success, non-zero otherwise.
No reliability problem is known. If you need help please try the Ntfsresize FAQ first (see below) and if you dont find your answer then send your question, comment or bug report to the development team:
There are a few very rarely met restrictions at present: filesystems having unknown bad sectors, relocation of the first MFT extent and resizing into the middle of a $MFTMirr extent arent supported yet. These cases are detected and resizing is restricted to a safe size or the closest safe size is displayed.
Ntfsresize schedules an NTFS consistency check and after the first boot into Windows you must see chkdsk running on a blue background. This is intentional and no need to worry about it. Windows may force a quick reboot after the consistency check. Moreover after repartitioning your disk and depending on the hardware configuration, the Windows message System Settings Change may also appear. Just acknowledge it and reboot again.
The disk geometry handling semantic (HDIO_GETGEO ioctl) has changed in an incompatible way in Linux 2.6 kernels and this triggered multitudinous partition table corruptions resulting in unbootable Windows systems, even if NTFS was consistent, if parted(8) was involved in some way. This problem was often attributed to ntfsresize but in fact its completely independent of NTFS thus ntfsresize. Moreover ntfsresize never touches the partition table at all. By changing the Disk Access Mode to LBA in the BIOS makes booting work again, most of the time. You can find more information about this issue in the Troubleshooting section of the below referred Ntfsresize FAQ.
ntfsresize was written by Szabolcs Szakacsits, with contributions from Anton Altaparmakov and Richard Russon.
Many thanks to Anton Altaparmakov and Richard Russon for libntfs, the excellent documentation and comments, to Gergely Madarasz, Dewey M. Sasser and Miguel Lastra and his colleagues at the University of Granada for their continuous and highly valuable help, furthermore to Erik Meade, Martin Fick, Sandro Hawke, Dave Croal, Lorrin Nelson, Geert Hendrickx, Robert Bjorkman and Richard Burdick for beta testing the relocation support, to Florian Eyben, Fritz Oppliger, Richard Ebling, Sid-Ahmed Touati, Jan Kiszka, Benjamin Redelings, Christopher Haney, Ryan Durk, Ralf Beyer, Scott Hansen, Alan Evans for the valued contributions and to Theodore Tso whose resize2fs(8) man page originally formed the basis of this page.
ntfsresize is part of the ntfsprogs package and is available from:
The manual pages are available online at:
Ntfsresize related news, example of usage, troubleshooting, statically linked binary and FAQ (frequently asked questions) are maintained at:
|ntfsprogs 2.0.0||NTFSRESIZE (8)||February 2006|