From 4c2cfb25836464be8cf60af65c4baab2f863e0f4 Mon Sep 17 00:00:00 2001 From: szaka Date: Sun, 10 Jul 2005 23:09:02 +0000 Subject: [PATCH] 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). --- ntfsprogs/ntfsresize.8.in | 7 ++++--- ntfsprogs/ntfsresize.c | 4 ++-- 2 files changed, 6 insertions(+), 5 deletions(-) diff --git a/ntfsprogs/ntfsresize.8.in b/ntfsprogs/ntfsresize.8.in index 452bdfdf..96b518a6 100644 --- a/ntfsprogs/ntfsresize.8.in +++ b/ntfsprogs/ntfsresize.8.in @@ -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 diff --git a/ntfsprogs/ntfsresize.c b/ntfsprogs/ntfsresize.c index 595ebf71..0e32185f 100644 --- a/ntfsprogs/ntfsresize.c +++ b/ntfsprogs/ntfsresize.c @@ -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",