|
From: Anton A. <ai...@ca...> - 2004-10-07 13:02:19
|
Hi, On Thu, 2004-10-07 at 00:00, mark wrote: > The problem I am experiencing was detected when I was making a Super Video CD > from a 5 minute video produced using Premiere under Windows NT4 SP6a. The > problem manifested itself as visual artefacts. I have traced the problem > back to the copying of a large *.avi file from an NTFS directory to an Ext3 > folder. The size of the file is the same, but the content differs. > Repeating the test generates errors in different parts of the file. If I > were to take a look at the detailed "cmp" output I would suspect that buffer > management is not properly managed across the interrupt/realtime part and the > user priority part... It looks as though a block has been added or removed (I > cannot fathom which). No, the blocks just get corrupted. > I don't know how to proceed analysing the problem any further. You shouldn't need to. > Linux version 2.6.3-16mdk (qa...@up...) (gcc version 3.3.2 > (Mandrake Linux 10.0 3.3.2-6mdk)) #1 Fri Aug 13 16:33:14 MDT 2004 > > Windows NT 4.0 Service Pack 6a + security patches upto April 2004 [snip] > ***** I conclude that file copy transactions from NTFS partition to Ext3 ***** > ***** are being corrupted. When I set the option to list the differences **** > ***** I get a feeling that read and write buffers are not being manged > correctly in the presence of interrupt driven/ realtime processing **** > > ***** Problem may therefore not lie within the scope of the NTFS driver ***** Correct. This has nothing to do with ntfs at all and it is a known early 2.6 kernel problem and has been fixed ages ago (well a month ago at least I think) but Mandrake seem to be using a very old 2.6 kernel which appears to still have the problem. Note that you are not actually using Mandrake's latest kernel so you might want to upgrade to that and try again. If the problem persists file a bug report with Mandrake and tell them to upgrade their kernel or find the bugfix and back port it. It is possible you are hitting a bug different to the one that was fixed that simply causes the file to be corrupted somehow. One possibility is if the file in Windows was compressed in which case you need at least NTFS driver version 2.1.12 to ensure that it is read correctly. 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 / IRC: #ntfs on irc.freenode.net WWW: http://linux-ntfs.sf.net/, http://www-stu.christs.cam.ac.uk/~aia21/ |
