[Linux-NTFS-cvs] CVS: linux-ntfs/ntfstools ntfsresize.c,1.18,1.19

[? <sz...@us...>]

Changes by: szaka

Update of /cvsroot/linux-ntfs/linux-ntfs/ntfstools
In directory usw-pr-cvs1:/tmp/cvs-serv19478/ntfstools

Modified Files:
	ntfsresize.c 
Log Message:
Fix incorrect message if new volume size was given in [KMG]Byte 


Index: ntfsresize.c
===================================================================
RCS file: /cvsroot/linux-ntfs/linux-ntfs/ntfstools/ntfsresize.c,v
retrieving revision 1.18
retrieving revision 1.19
diff -U2 -r1.18 -r1.19
--- ntfsresize.c	17 Jul 2002 04:37:48 -0000	1.18
+++ ntfsresize.c	17 Jul 2002 05:59:57 -0000	1.19
@@ -767,5 +767,5 @@
 		advise_on_resize();
 
-	/* FIXME: check opt.size validity */
+	/* FIXME: check new_volume_size validity */
 	
 	/* Backup boot sector at the end of device isn't counted in NTFS 
@@ -777,6 +777,8 @@
 	if (new_volume_size > vol->nr_clusters)
 		err_exit("Volume enlargement not yet supported\n");
-	else if (new_volume_size == vol->nr_clusters)
+	else if (new_volume_size == vol->nr_clusters) {
+		printf("==> Nothing to do: NTFS volume size is already OK.\n");
 		exit(0);
+	}
 
 	for (i = new_volume_size; i < vol->nr_clusters; i++)
@@ -796,10 +798,10 @@
 	update_bootsector(new_volume_size);
 
-	/* FIXME: create backup boot sector -- if possible*/
+	/* We don't create backup boot sector because we don't know where the 
+	   partition will be split. The scheduled chkdsk will fix it anyway */
 
 	printf("==> NTFS had been successfully resized on device %s.\n"
-	       "==> New NTFS volume size is %lld MB.\n"
-	       "==> Now you can go on to resize/split the partition.\n",
-	       vol->dev_name, (((opt.size * vol->cluster_size) >> 20) + 1));
+	       "==> Now you can go on to resize/split the partition.\n", 
+	       vol->dev_name);
 
 	return 0;