BackUp jobs fails - only on some files and some situations

[peon2t]

Hello

We are using a ReadyNAS Duo v2 in our small business and are doing daily (& monthly) backups on different external HardDrives using the BackUp-Button.

For about the first year it worked flawlessly, then we were starting to see...

cp: cannot stat 'PATH/FILENAME': Input/output error

...in the logfile - but only for several files (always the smae) and only when using one (of four) external HardDrives that we were using alternately (always the same one too, we know, cause we numbered them).

So we assumed that this special external drive is faulty and replaced it with a new one which in our first test worked fine.

Now, only a few days later, we are seeing the exact same error (again, same files) on another of the external drives!

(By the way: the said 'faulty' files can be opened from the NAS and from the backup drives...)

Has anyone an idea?

[StephenB]

How is the USB formatted, and how long is the full output file name (including the path)?

[peon2t]

The USB drives are NTFS formatted.

The lenght of the file names differ... I have quite long ones that show the error (for example 144 chars) but also shorter ones (for example 74 chars).
And I also have long ones (for example 184 chars) which are working.

[StephenB]

There is a microsoft limit of 260 characters (including the drive letter and the full path). It sounds like you are below that limit though.

Maybe put the USB drive on a windows system and run chkdsk.

[peon2t]

Aftersome busy months in which the problems partially disappeared and I tried several things, I unfortunately have to warm up the thread again:

Situation is as follows:

We're seeing

cp: cannot create regular file [...] Input/output error

and

cp: cannot stat {...] Input/output error

errors on various files and disks.

The strange things are:

1. the errors don't happen every day (but we do backup every day)
2. the errors happen on different target-disks, so the shouldn't be related to a defective external harddisk
3. the errors don't always affect the same files
4. the affected files usually seem to be finde on source and on target

nevertheless it's disturbing to have errors in the log every some day since we're highly dependant on a working BackUp...

I also formatted two of the target disks because I tought that his maxbe could help. But it didn't have a long-term inpact.

[jdgs]

Was there any resolution for this? I too have the same issue, have just started trying to backup to USB.

[StephenB]

If "this" means that "file names+path > 260 characters" then no.

if "this" means means something else, then it would be more helpful if you provided more information on what files aren't being copied.

[Marto731]

Stephen, Peon, Jd & Co.,

"BackUp jobs fails - some files and some situations"
I have 2 thoughts.
(a) The files not copied, are been used by another program or process
(b) The file names contain non Alphanumeric characters, $,% ,& ,* £ / \ that are special characters in Linux.

Regards, Marto

[StephenB]

Marto73 wrote:
Stephen, Peon, Jd & Co., "BackUp jobs fails - some files and some situations" I have 2 thoughts. (a) The files not copied, are been used by another program or process (b) The file names contain non Alphanumeric characters, $,% ,& ,* £ / \ that are special characters in Linux. Regards, Marto

I agree either of these could cause this issue. Perhaps file permissions too.