The linux-ntfs CVS now contains an adapted ntfsresize that restores the
old behiour where the volume is not modified until the user says "yes" to
begin modifications. That is a lot less work than changing the
documentation + output messages of ntfsresize and it is "least surprise"
for users who upgrade to new version.
The only difference to Szaka's version is that ntfsresize now only sets
the dirty flag if the volume is not already dirty and it only empties the
journal if it is not already empty. It seems silly to do things that are
already the case especially when they are things that can take a while
like emptying the journal.
Best regards,
Anton
On Sun, 3 Dec 2006, Anton Altaparmakov wrote:
> On Sun, 3 Dec 2006, Szakacsits Szabolcs wrote:
> > > El sábado, 2 de diciembre de 2006 20:44, Frans Pop escribió:
> > > > On Saturday 02 December 2006 14:36, Szakacsits Szabolcs wrote:
> > > > >
> > > > > I put a statically linked version here to ease the testing.
> > > > > http://www.ntfs-3g.org/ntfsresize-1.13.1.1.tgz
> > > >
> > > > This version makes Vista happy too. After reboot chkdsk is executed and
> > > > on second reboot Vista boots successfully.
> >
> > Thanks. So we know now the technical reason why ntfsresize didn't work
> > previously. Vista deliberately refuses to mount NTFS if it thinks it was
> > mounted by NT4. Though this wasn't very clear from the halt message :-)
>
> Yes there not being a halt message at all! Nice to know, thanks for
> working it out! It is very intersting that they no longer allow NT4 to
> access Vista NTFS volumes. I still wonder whether this may be a Vista bug
> rather than intentional...
>
> Interesting though, what happens when you present Vista with an NTFS 1.2
> version formatted volume? Will it refuse to boot, too or will it simply
> upgrade it like 2k/XP did? If it refuses to boot it is time to remove the
> mkntfs v1.2 support now so people can't by accident create old style
> volumes that will break Vista...
>
> > Anton was happy with the not understood fix which in fact was a bug in his
> > patch which made Vista to boot by pure luck. To be honest, I've been
>
> I object to it being called a bug. I very consicously removed the mounted
> by NT4 flag setting as linux-ntfs operates like NT5 not NT4 so it is silly
> to set the flag. I have even been considering removing support for NT4
> volumes and upgrading them on mount like Win2k/XP do, perhaps with an
> option to disable (or enable) this behaviour...
>
> The only place the NT4 flag has is to be set by ntfsfix on volumes after
> being written to with the old ntfs driver which hopefully is no longer in
> use so ntfsfix does not need to set that flag either any more... Remember
> that this was what I wrote ntfsfix for in the first place: to make writing
> with the old driver at least a little bit less broken...
>
> Best regards,
>
> Anton
>
Best regards,
Anton
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer, http://www.linux-ntfs.org/
