Szaka wrote: "pointless to empty journal if clean"...
It is NOT pointless to empty. I think you do not understand how
journalling in Windows works (or I don't understand it... (-;). My
understanding is that regardless whether the journal is clean or not
Windows can/will parse the journal (at least in some cases, depends on the
exact state of the journal) and redo various things/undo others as parts
of its journalling startup. Normally this has no effect as it just writes
the same data over the existing data (unless a weird crash occurred in
which case it will repair the volume). However when you have modified the
volume underneath with another ntfs driver or with ntfsresize or whatever,
then doing such redo/undo operations are fatal. Well they can be fatal
anyway. I guess in most cases they will silently corrupt stuff that one
will not know about or even just write over now random locations on disk.
The problem is this is totally unpredictable. The only way to make not
emptying the journal safe is to do journalling and keep the journal
uptodate. But none of us know how to do that so we better empty it to
make sure everything is ok...
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/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
