Simplicity rulez, this patch eliminates the "resize by number of
clusters" feature. It was only used as a temporary helper for
development and on the long term it would be just an unneeded baggage.
advise_on_resize() reworked accordingly.
ntfsresize.c:
[Szaka] Simplicity rulez, this patch eliminates the "resize by number of
clusters" feature. It was only used as a temporary helper for
development and on the long term it would be just an unneeded baggage.
advise_on_resize() reworked accordingly.
BKrev: 3de2128fY-mA-GfH497dipyVBkcFbg
clusters" feature. It was only used as a temporary helper for
development and on the long term it would be just an unneeded baggage.
advise_on_resize() reworked accordingly.
(Logical change 1.19)
clusters" feature. It was only used as a temporary helper for
development and on the long term it would be just an unneeded baggage.
advise_on_resize() reworked accordingly.
(Logical change 1.19)
Hi,
This is important. kilo-, mega- or gigabytes prefixes use decimal, not
binary units according to biggest standards (SI, ATA, IEEE, disk
manufacturers, etc). Also only [kMG] accepted and [Kmg] not anymore.
Manual updated according to this. "Side-effect" of the patch: user
can't destroy his fs if uses the same or slightly bigger decimal unit
for disk partitioning (e.g. by cfdisk or recent fdisk) as he did for
ntfsresize [used binary units before]. From now on new/old volume
sizes are printed in bytes and MB's, not in clusters and MB's.
Cheers,
Szaka
BKrev: 3de111daUryDdizzKIb25cpern36zg
This is important. kilo-, mega- or gigabytes prefixes use decimal, not
binary units according to biggest standards (SI, ATA, IEEE, disk
manufacturers, etc). Also only [kMG] accepted and [Kmg] not anymore.
Manual updated according to this. "Side-effect" of the patch: user
can't destroy his fs if uses the same or slightly bigger decimal unit
for disk partitioning (e.g. by cfdisk or recent fdisk) as he did for
ntfsresize [used binary units before]. From now on new/old volume
sizes are printed in bytes and MB's, not in clusters and MB's.
Cheers,
Szaka
(Logical change 1.18)
into cantab.net:/usr/src/ntfs-progs
2002/11/18 16:16:35+00:00 cantab.net!aia21
Makefile.am:
autogen.sh doesn't work with automake 1.5 -- fix by Szaka
BKrev: 3dd914ebS77iNi1Z5xJQKqmZYV0AIA
Below patch includes:
- ntfsresize man page
- ntfsresize TODO update
- some spelling correction
- more usage() cleanup
- corrected misleading message after successful test-run
- syncing device after resize
- more verbose/correct hints after resize
I have some more testers but no feedback yet due to lack of their
time.
Cheers,
Szaka
BKrev: 3dd7c363eC7EpqUab5qjpcbq1eWfyw
Hi,
This patch adds the warning Anton requested,
---------------------------------------------------------->
WARNING: Every sanity checks passed and only the DANGEROUS
operations left. Please make sure all your important data
had been backed up in case of an unexpected failure!
Are you sure you want to proceed (y/[n])?
OK quitting. NO CHANGES has been made to your NTFS volume.
<----------------------------------------------------------
The question will be skipped if the -f (force) used [e.g. for
automatic testing]. This patch needs the earlier sent
ntfsresize-usage-cleanup.diff patch.
Szaka
BKrev: 3dd7bfe0ZRpIzFdMtWEQJhzZVnbwxQ
This patch adds the warning Anton requested,
-=------------------------=------------------------------->
WARNING: Every sanity checks passed and only the DANGEROUS
operations left. Please make sure all your important data
had been backed up in case of an unexpected failure!
Are you sure you want to proceed (y/[n])?
OK quitting. NO CHANGES has been made to your NTFS volume.
<----------------------------------------------------------The question will be skipped if the -f (force) used [e.g. for
automatic testing]. This patch needs the earlier sent
ntfsresize-usage-cleanup.diff patch. Szaka
(Logical change 1.11)
cantab.net!aia21
flatcap.org!flatcap