Re: NTFS filesystem problems
Here are the script to test it:
Warning: Of This Script the provided file and also the file allocation table destroys.
If a blank HDD uses.
make a folder on HDD:
Code:
mkdir /tmp/usbmounts/sda1/try
provide the Script (Tip: it is one line, even if it does not look so):
Code:
echo -e '#!/bin/ash\n\ntryfile="x.$$"\ntouch "${tryfile}"\n\ntrynum=0\nwhile true ; do\n\tcp "${tryfile}" "${tryfile}.tmp"\n\techo "this is some text" $trynum >>"${tryfile}.tmp"\n\tmv "${tryfile}.tmp" "${tryfile}"\n\ttrynum=$(( ${trynum} + 1))\n\n\tsleep 1\ndone' > /tmp/usbmounts/sda1/try/try.sh
Script workable do:
Code:
chmod +x /tmp/usbmounts/sda1/try/try.sh
Go to the Script folder:
Code:
cd /tmp/usbmounts/sda1/try
Script in the background start:
Look like the generated file is called (file name is x.prozessnr):
At contents of the generated file look (file name from ls-> x.prozessnr.tmp do not take, if available)
One can begin the Script also several times.
Script finish (prozessnr is the No. in the provided file it seems.):
If the destroyed file covers the same memory like before Chkdsk find nothing.
Chkdsk can not repair files. It repairs "File allocation table". I believe many Chkdsk do not know what really does.
The Script does not point also whether the mistake while copying or with him purely write in a file the mistakes happen.
However, I think rather with him purely write or even both.
And this performed mistake is the cause. Now differences are between the file allocation table and the actual hard disk allocation.
Becomes now with this wrong file allocation table furthermore copies / move / etc. the strangest things can happen. Not only 0 KB files
And hier are the Script in Readable Style (but with him echo order is more simply to be provided for you):
Code:
#!/bin/ash
tryfile="x.$$"
touch "${tryfile}"
trynum=0
while true ; do
cp "${tryfile}" "${tryfile}.tmp"
echo "this is some text" $trynum >>"${tryfile}.tmp"
mv "${tryfile}.tmp" "${tryfile}"
trynum=$(( ${trynum} + 1))
sleep 1
done
If A.C.Ryan was really interested in a mistake removal for a long time they would have tried the Script.
It was often enough mentioned. There is no excuse here nothing from knew.
In addition, I believe you no more. My trust is away. I have often enough become "veräppelt" (in german: I know the word not in in English).
I will sell on a PM to Mikael personally. Indeed, I can write it only in in German there it to complicate is.
This is my last attempt. Then all media are informed like A.C.Ryan with your customers handles.
@ wheelspt:
Because I know which files make this error, I can say to you everything are concerned original FW by Realtek. Try out the Script.
