On Tue, 28 Nov 2006, Anton Altaparmakov wrote:
>
> Thank you for persisting with this.
Yes, thank you Frans and Andree for your help. We definitely found
something.
> I have now looked at the code and you are right it does not do the same
> thing. This is because when Yura ported my $LogFile code from the kernel
> for some unknown to me (or forgotten by me) reason he did not integrate
> clearing the journal into the mount process. He integrated the checking
> but not the clearing. This is a HUGE and VERY BAD bug in libntfs and
> means that all ntfs utilities are _DANGEROUS_ to run and can cause
> massive and very hard to detect data corruption. )-:
If the journal is not clean then the mount is refused. This detection was
added later, previously the journal cleaning was unconditional because we
didn't know if it's clean or not.
So, I don't see a big problem here. The reliability of ntfsresize and
ntfs-3g seems to confirm this. Nobody reported corruptions, in fact, people
are finding bad hardwares (RAM, disk, cable) and softwares during usage and
testing. Almost like ZFS :-)))
> No wonder Vista does not boot!!!
I still wonder why it doesn't boot. As I explained in my previous email,
ntfsresize resets the journal unless the empty journal detection fails.
> It is amazing it took so long to find this problem. I cannot believe we
> managed to get away with it for so long...
For me it seems it worked as it should have. If the journal is clean,
then theoretically it's pointless to empty. If unclean then mount is
unconditionally refused.
Szaka
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
