search

drftpd-ng / drftpd

Distributed Daemon FTP Server (aka DrFTPD)
GNU General Public License v2.0
56 stars 21 forks source link

crc problem #72

Open maxpayneovh opened 7 years ago

maxpayneovh commented 7 years ago

When some files were uploaded and they were bad dr dont delete them and dont mark as missing, they stay on site. you have to rescan manual to find out whichone is bad. same with sample file.

epochyx commented 5 years ago

Can you reproduce that on dr 3.4 or develop ? Is it possible to have a detailed scenario with an example? Can you provide the java version and the OS for master / slaves ?

maxpayneovh commented 5 years ago

java version "1.8.0_201" Java(TM) SE Runtime Environment (build 1.8.0_201-b09) Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode) Ubuntu 18.04.2 LTS dr 3.3 dev

https://0bin.net/paste/0c+ByrZkotq7n259#zJebHP79UQcxEAvnIWs3TjieKL5nlt+0I1vYGKXb3ZL

mvangoor commented 4 years ago

Hi donmagic1,

Reading the code I noticed a specific setting to leave files behind if something happens during upload. It's called "delete.upload.on.abort" and has a default value of 'false'.

Could you let us know the value of that setting in your setup?

peps1 commented 4 years ago

I'm running into this issue myself, mostly in combination with ConstantMirroring. Not sure if donmagic1 uses that as well.

I have delete.upload.on.abort set to true for a long time and still see this.

There's a few ways this appears.

  1. The file size looks ok, but CRC check returns different value, so file should have been deleted or re-transmitted when mirroring
  2. File size looks ok, but rescan shows CRC as 000000.
ghost commented 1 year ago

Hello, @peps1 @maxpayneovh @mvangoor @epochyx Is the problem still current?