Just wanted to add I had the same problem: eMule worked fine in Vista,
aMule in Ubuntu then worked fine using same temp files (on an NTFS
volume), but then running back in Vista again caused BSoD within a few
seconds of a download commencing. BSoD ceased occurring after I
cancelled all the
BTW, the error message on the blue screen was:
PAGE_FAULT_IN_NON_PAGED_AREA
Don't know if that helps anyone.
--
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,
This is a known Vista problem handling sparse files. Please contact
Microsoft. Good luck!
--
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
It's possible that this is a pure Windows bug. Either a Microsoft NTFS
or a device driver related. Google found many similar crashes but none
of them involved NTFS-3G, only for Windows recovery.
Here is an idea how we could prove and document this is a pure Windows
bug.
1. Install Cygwin (a
The ZIP package at
http://www.flexhex.com/docs/articles/download/sparse.zip contains a
CS.EXE file which is supposed to work similarly as the cygwin cp
--sparse=always command. The test could be simpler.
--
sharing amule temp files winth Vista in ntfs partition gives BSOD
I've found the below on
http://channel9.msdn.com/forums/Coffeehouse/256701-QuickTime-BSODs-
Vista-solution
That eMule had to remove all the sparse file support on Vista because
of Vista bugs
So, it's very well possible this is a pure Vista bug what any software
can trigger, not only NTFS-3G.
--
Cygwin cp --sparse=always doesn't work. The files are not sparse. CS.EXE
also doesn't work on my x64 because it's a 32-bit EXE file. Maybe you're
more lucky.
Of course it's also possible that Microsoft silently disabled sparse
file support because they had too many reliability problems with them.
Oh, I've understood. There should be the possibility on amule to
disable sparse file support. Or at least is there a mount option for
ntfs-3g to disable sparse files?
I don't want to do all those tests, now it's quite proved that the
problem is on vista...
--
sharing amule temp files winth
In fact I didn't have this problem on XP. Have you got XP?
--
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
No such problem was reported with XP. Sparse support can't be disabled
for NTFS-3G because it's part of the POSIX specification.
--
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
Ok, so let's mark it as invalid for now!
Thanks and sorry
** Changed in: ntfs-3g (Ubuntu)
Status: New = Invalid
--
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
I have done this sequence
1- start to download something in emule ~700Mb file
2- go to windows and start emule, after the hashing, when the file
started to be uploaded I got the BSOD
3- go to linux, the partition cannot be mounted because it was not
cleanly umounted by windows
4- create NTFS
Same error even with --force :( do you still want the result of the
error file?
Maybe I should before cleanly umount the device using linux... But
this process may hide the problem of the windows BSOD
--
sharing amule temp files winth Vista in ntfs partition gives BSOD
What are the outputs of
ntfs-3g.probe --readwrite /dev/sda5
ntfs-3g.probe --readonly /dev/sda5
Yes, the log file is important even if we can't create yet the NTFS
debug file. We will make a solution for you depending on the above
results.
--
sharing amule temp files winth Vista in ntfs
Storno the ntfs-3g.probe's. I just realized you use ntfsprogs-2.0.0 and
have problem with the image file, not the NTFS device.
Please use ntfsclone from ntfsprogs 1.13.1. ntfsprogs-2.0.0 has
problems.
--
sharing amule temp files winth Vista in ntfs partition gives BSOD
Well, if the journal file is unclean then ntfsclone-1.13.2-wip will fail
too.
There are two choices:
1. Run ntfsfix on /dev/sda5 before running ntfsclone (any version).
2. Run ntfsfix on ntfsmeta.img then ntfsclone ntfsmeta.img.
--
sharing amule temp files winth Vista in ntfs partition gives
mounted and umounted it. now the image creates successfully.
but bzip2 is sloow :D
I hope that the file produced will be of a reasonable size...
after that I will
- boot into windows
- chkdsk d: /f
- reboot into linux
- collect ntfs debug data
- reboot into windows
- test if BSOD again
- tell
Use the --force option.
--
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
Good job! :-)
Yes, bzip2 is unfortunately very slow. We will solve this issue in the
future by using a different NTFS debug image format.
The actions are correct.
I would also need the output of
egrep -3i 'ntfs|ata|sd|i/o' /var/log/daemon.log
and the name of the file which crashes Vista.
--
Please download http://ntfs-3g.org/download/ntfsclone-1.13.2-wip.tgz
Unpack it and use ntfsclone-1.13.2-wip instead of ntfsclone.
Thanks.
--
sharing amule temp files winth Vista in ntfs partition gives BSOD
https://bugs.launchpad.net/bugs/279017
You received this bug notification because you
Please also send the output of
egrep -i 'ntfs|ata|sd|I/O' /var/log/daemon.log
/var/log/daemon.log could be also /var/log/messages,
/var/log/messages.log, /var/log/syslog or something else distribution
specific.
--
sharing amule temp files winth Vista in ntfs partition gives BSOD
I'll make you an ntfsclone binary which you can use, please wait a bit.
--
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.
--
Yes, --force ntfs-3g mount and unmount should also fix it.
--
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
sudo ./ntfsclone-1.13.2-wip --ignore-fs-check -f -m -o ntfsmeta.img
/dev/sda5
gives the same output (extept from the version of course!). so
proceeding with probe.
sudo ntfs-3g.probe --readwrite /dev/sda5
$LogFile indicates unclean shutdown (0, 0)
sudo ntfs-3g.probe --readonly /dev/sda5
no
This produces lots of output, also not related to ntfs!
attaching
the filename which crashes vista is one of the files in this dir
d:\Nicolò\Downloads\mule\temp\
maybe 001.part or 002.part, which are the files created by amule and
in which amule writes the downloaded parts.
the file was created on
NTFS interoperates with several other subsytems and if one of them fails
then the problem appears as an NTFS bug but in fact it isn't. That's why
more, non-NTFS info is needed, to confine where the problem is.
The good news is that no sign of any hardware problem.
However it seems the NTFS
I hardly ever mount /dev/sda1, so maybe that's why you don't see any
umount. Also I had 3 hard lockups so I had to switch off my pc.
Well, I cannot understand why the mount was not reported by the log files...
I mount it through fstab
UUID=4CF8C602F8C5E9F2 /media/Dati ntfs
4 ours to do the first compression!
See you tomorrow for the second :D
** Attachment added: ntfsmeta-pre-chkdsk.img.bz2
http://launchpadlibrarian.net/18325928/ntfsmeta-pre-chkdsk.img.bz2
--
sharing amule temp files winth Vista in ntfs partition gives BSOD
The file metadata is indeed inconsistent.
Did you start to download the file in Linux or Vista?
What is your Vista version? Do you have Vista Patches, Service Packs?
--
sharing amule temp files winth Vista in ntfs partition gives BSOD
https://bugs.launchpad.net/bugs/279017
You received this
I started the download in linux
I have vista upgraded to sp1+patches.
Now I will reboot into windows and run chkdsk and create the new debug
--
sharing amule temp files winth Vista in ntfs partition gives BSOD
https://bugs.launchpad.net/bugs/279017
You received this bug notification because you
Hello, I've run chkdsk and saved the ntfs debug.
Then I rebooted into windows again but I still got the BSOD!
so chkdsk does not resolve the problem :(
do you think that you still need the ntfs debug?
--
sharing amule temp files winth Vista in ntfs partition gives BSOD
Yes, chkdsk has many problems unfortunately. If it still crashes then no
need for the other debug file.
What are the Amule versions for Windows and Linux?
You don't have Windows Home Server, do you?
Microsoft is having major problems with NTFS file corruptions and they even had
to hire back
amule 2.2.2
emule 0.49b
Do I need windows home server to do some tests?
I can have windows 2003 server, if needed.
Anyway I think that the BSOD comes even when copying the file, not
only when using emule.
Wait, I didn't enable compression... Why is the file marked
compressed? (if I understood)
That would be a very good observation! If BSOD comes when you copy the
file then please run the below command in Linux shell. It is one line:
for i in $(seq 1 200); do dd if=/dev/zero of=sparse bs=4096
seek=$((2*$i)) count=1 conv=notrunc; done
Then try to copy the 'sparse' file on Windows. If it
Do you think that sparse files are wrongly managed by ntfs-3g?
This might be true, since when the file is completed (and though
re-created) it does not cause any BSOD.
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
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!
--
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
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
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.
Really? To tell the truth I've always had this error, since I bought
my laptop, on January, but I didn't test if I had
Can you write down the Vista BSOD messages, or make a photo about it?
--
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.
--
Copying the sparse file works without problems :(
Copying the 001.part does not give the BSOD too.
So Mabe the problem was in writing that file!
Unfortunately I can't take a photo right now, and I cannot write down
the information because they last a few seconds.
But I found this, when coming
Thank you for the bug report. The NTFS-3G project is very interested to
help you to solve your problem. Please follow the below steps to be
able to help you:
1. Reproduce the problem.
2. Create the NTFS debug information according to http://www.linux-
Sorry, step 4 had a typo, it should be:
4. Repeat step 2.
It's important to create the NTFS debug info right after running CHKDSK
and before trying to reproduce the problem.
--
sharing amule temp files winth Vista in ntfs partition gives BSOD
https://bugs.launchpad.net/bugs/279017
You received
And of course step 6 was supposed to say:
6. Send the files you got in step 2. and 4. to szaka AT ntfs-3g.org or
make them available somewhere for download and let us know if step 3
helped.
--
sharing amule temp files winth Vista in ntfs partition gives BSOD
43 matches
Mail list logo
