|
From: Szakacsits S. <sz...@si...> - 2004-03-05 18:09:50
|
On Fri, 5 Mar 2004, Anton Altaparmakov wrote: > On Fri, 2004-03-05 at 17:00, Szakacsits Szabolcs wrote: > > On Fri, 5 Mar 2004, Anton Altaparmakov wrote: > > I though about that also and I think that's also impossible today. Using a > > write enhanced driver in the _future_ it could be possible _if_ the driver > > allows to mount a dirty volume read-write. It should never allow, perhaps > > only read-only mount. > > Yes, that is certainly how the new driver would do it but the old ntfs Maybe we should call the "old" driver as "legacy" driver. The term "old" is always relative, but "legacy" is somehow narrowed down. Actually at present there is only 1 legacy ntfs driver we have. However I don't care about the legacy driver. Everybody knows very well that it corrupts data and actually write is disabled for w2k, xp, w2k3 and longhorn. > driver is still out there and there are several commercial ones and then > there is Captive-NTFS as well... If they allow dirty volumes to be blindly mounted then that's their bug. At present, if anybody left it dirty then ntfsresize and ntfsclone allow mount only if it's forced _and_ the built-in consistency check passes. Szaka |
