opengnsys
/
ntfs-3g
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Rephrase mentioning "dirty" volumes so people hopefully won't think that 

Windows repairs what ntfsresize damaged. The real function of leaving
the volume dirty is to make Windows create the backup boot sector because
we can't know where the partitioner will exactly resizes (they optionally
round to some cylinder boundary, defined by ad hoc, arbitrariy rules).
edge.strict_endians
szaka 2005-07-10 23:09:02 +00:00
parent d37968ee84
commit 4c2cfb2583
2 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
ntfsprogs/ntfsresize.8.in
View File

@ -137,11 +137,12 @@ with
first.
.TP
.B -f, --force
Forces ntfsresize to proceed with the resize operation if the filesystem
is marked "dirty" for consistency check.
Forces ntfsresize to proceed with the resize operation even if the filesystem
is marked for consistency check.
Please note, ntfsresize always marks the filesystem
"dirty" before a real resize operation and it leaves that way for extra
for consistency check before a real resize operation
and it leaves that way for extra
safety. Thus if NTFS was marked by ntfsresize then it's safe to
use this option. If you need
to resize several times without booting into Windows between each

4
ntfsprogs/ntfsresize.c
View File

@ -2098,8 +2098,8 @@ static ntfs_volume *mount_volume(void)
if (vol->flags & VOLUME_IS_DIRTY)
if (opt.force-- <= 0)
err_exit("Volume is dirty. Run chkdsk /f and "
"please try again (or see -f option).\n");
err_exit("Volume is scheduled for check.\nRun chkdsk /f"
" and please try again, or see option -f.\n");
if (NTFS_MAX_CLUSTER_SIZE < vol->cluster_size)
err_exit("Cluster size %u is too large!\n",