Messages in this thread | | | Date | Tue, 14 Mar 2000 17:15:13 +0200 | From | Ville Herva <> | Subject | NTFS |
| |
Steve Dodd wrote: > > (Fixing NTFS for 2.4.0) > > I'm afraid I'm not going to volunteer because I don't have enough free > time to commit to doing it reliably. However, if people want to remind > of all the outstanding NTFS issues they know of, I'll collect them and > stick them on the web somewhere .. I may even get around to fixing some > of them, but no promises.
Steve, if you manage to begin compiling that bug lists, perhaps you should contact Jeff Merkey:
On 2000-03-02 16:20:21, Jeff V. Merkey <jmerkey@timpanogas.com> wrote: > > (OT)BTW - the NTFS driver (write) in Linux has data corruption on W2K. > I have reviewed the code, and the on-disk structures are WRONG in > several places, and several of the internal attribute records are making > incorrect assumptions about some of the record fields. What's there > will cause severe data-corruption if you are switching between the two > platforms with a single partition image, particularly with the later W2K > NTFS implementation (though NT 4.0 seemed to be OK -- some problems with > the journal). The NTFS driver we tested was using the earlier FS > implementation (n/2), not the newer W2K formats. The first time W2K > mounts an NTFS volume with 4.0 format, it will auto-convert the NTFS > volume to the W2K Volume Manager formats under Windows 2000, including > any stripe sets, and potentially make incorrect decisions about > attribute assignment if a journal is present and the volume has been > booted under NT 4.0 after Linux has written to it. > > Thought you might like to know. We contracturally cannot help fix the > NTFS driver in Linux, but we can point out potential problems and > explain them to the best of our understanding.
-- v --
v@iki.fi
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |