On 25 Feb 2003, Adam Williamson wrote:
> On Tue, 2003-02-25 at 13:56, Mike Richardson wrote:
> >
> > Clean XP Pro install on a 20G drive, resized to 10G.
Unallocating maximum 50% is far the most general case. Windows puts
metadata in the middle of the filesystem that neither the
defragmenters (they shouldn't by definition) nor ntfsresize can move
around, yet. However there were several reports unallocating over 80%
of the disk space - probably some manufacturers made the Windows
images on a smaller disk and these were just expanded later on.
> > XP ran chkdsk on first boot but after that was fine.
>
> Yeah, the ntfs utils currently mark NTFS partitions "dirty" after doing
> almost anything to them, just so that if they do do something wrong,
> chkdsk / scandisk will run when you boot back to Windows and fix it
> before it gets any worse.
It starts with marking the volume dirty. Power outage is also possible ;)
Pixel, it may make sense to present this information to the user at
some point in some way not to scare them to death later on, e.g. (in
non-native English): "Please note, for extra safety NTFS consistency
check is scheduled to run when you boot Windows".
Szaka
