|
From: Anton A. <an...@us...> - 2001-06-13 19:01:00
|
Changes by: antona
Update of /cvsroot/linux-ntfs/linux-ntfs/ntfstools
In directory usw-pr-cvs1:/tmp/cvs-serv20956/ntfstools
Modified Files:
mkntfs.8.in mkntfs.c
Log Message:
More cleanups and man page final updates/polishing.
Index: mkntfs.8.in
===================================================================
RCS file: /cvsroot/linux-ntfs/linux-ntfs/ntfstools/mkntfs.8.in,v
retrieving revision 1.2
retrieving revision 1.3
diff -U2 -r1.2 -r1.3
--- mkntfs.8.in 2001/06/11 04:02:09 1.2
+++ mkntfs.8.in 2001/06/13 19:00:56 1.3
@@ -38,7 +38,8 @@
[
.B \-v
+]
[
-.B \-v
-]]
+.B \-vv
+]
[
.B \-F
@@ -155,6 +156,5 @@
to run, even if the specified
.I device
-is not a block special device, or
-appears to be mounted.
+is not a block special device, or appears to be mounted.
.TP
.B \-V
@@ -172,17 +172,18 @@
.I device
\. However, current versions of the Linux kernel (all versions up to and
-including todays 2.4.5) only report an even number of sectors when the sector
-size is below 1024 bytes,
-which is the case for most hard drives today (512 bytes sector size). This
-means that when a partition has an odd number of 512-byte sectors, the last
-sector is not reported to us and hence the created NTFS volume will have the
-backup boot sector placed one sector ahead of where it should be. For this
-reason,
+including todays 2.4.5) either only report an even number of sectors when the
+sector size is below 1024 bytes, which is the case for most hard drives today
+(512 bytes sector size) or they return the correct number but accessing the last
+sector fails. Either way, this means that when a partition has an odd number of
+512-byte sectors, the last sector is either not reported to us at all or it is
+not writable by us and hence the created NTFS volume will either have the backup
+boot sector placed one sector ahead of where it should be or it cannot be
+written at all. For this reason,
.B mkntfs
-marks the NTFS volume dirty, so that when you reboot into Windows, checkdisk
+marks the NTFS volume dirty, so that when you reboot into Windows, check disk
runs automatically and creates a copy of the backup boot sector in the correct
location. This also has the benefit of catching any bugs in
.B mkntfs
-as checkdisk would find any corrupt structures and repair them, as well as
+as check disk would find any corrupt structures and repair them, as well as
report them. - If you do see any problems reported, please report the messages
to the author.
Index: mkntfs.c
===================================================================
RCS file: /cvsroot/linux-ntfs/linux-ntfs/ntfstools/mkntfs.c,v
retrieving revision 1.35
retrieving revision 1.36
diff -U2 -r1.35 -r1.36
--- mkntfs.c 2001/06/13 18:07:00 1.35
+++ mkntfs.c 2001/06/13 19:00:56 1.36
@@ -2753,4 +2753,10 @@
"has\nto fit inside eight bits.\n");
Dprintf("cluster size = %i bytes\n", opt.cluster_size);
+ if (opt.cluster_size > 4096)
+ Qprintf("Warning: compression will be disabled on this volume "
+ "because it is not\nsupported when the cluster "
+ "size is above 4096 bytes. This is due to \n"
+ "limitations in the compression algorithm used "
+ "by Windows.\n");
/* If user didn't specify the number of clusters, determine it now. */
if (!opt.nr_clusters)
|
