On Wed, 8 Oct 2008, [utf-8] Nicolò Chieffo wrote:
> Do you think that sparse files are wrongly managed by ntfs-3g?
They are fine. But your case is more complex than the usual one.
It also could be a unique, subtle problem. Nobody else reported
this problem and I also can't reproduce it.
> This might be true, since when the file is completed (and though
> re-created) it does not cause any BSOD.
If the file caused BSOD but When it's ready and no problem then please run
ntfsinfo -fv -F file_name device
on Linux and sent th efull output.
> Do you know if amule can be set up to not create sparse files? if so we
> could also test if started files can be resumed by emule without any
> problems.
I don't know if amule suports this. But I think the issue is sparse file
related.
> I will also test the following: start the file in emule, resume in
> amule and test back what emule does
Ok.
> Wait: can't it be that emule does not use sparse file, and amule does?
> so emule accesses the file "normally" which causes the page fault!
Sparse file handling is transparent and a user space application definitely
shouldn't crash the OS. This is a serious Microsoft bug but we need to
figure out where the real problem is. A file system driver should never
crash, not even with corrupted files and data.
--
sharing amule temp files winth Vista in ntfs partition gives BSOD
https://bugs.launchpad.net/bugs/279017
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
