Knowledgebase: Tips and tricks
File related error messages in file access logs
Posted by Sven Koester, Last modified by Andre Kuehnemund on 23 May 2016 13:45

PresSTORE's jobs may end regular even if some single files could not be read or written or may be incomplete. In either case, PresSTORE protocols each file related error in the file access log.

Starting with PresSTORE 3.2, a job will show a warning in case there are file related error messages.
Up to PresSTORE 3.1, the job ended without warning.
It is good practice to check the files that are listed and in case these are temporary of log files to skip them using a filter in the backup or synchronize job.

This list shows the most common errors that appear and what can cause the error.

File truncated:

Means we expected to read more data than we actually did. In other words: the file was cut short while we were reading it because it had changed during the backup. As a result, the file on the target does not reflect its latest state. The changed file will be saved during the next incremental. This is a normal behavior for log files or similar protocol files. For files where the data is not simply appended, this may be a problem, e.g. database files should not be saved or copied when they are open because that may produce inconsistent results.

No such file or directory:
During a file scan a file existed that is no longer present when it comes to copying it. This is not a problem for files that have been deleted during the backup, e.g. temporary files.
Another possibility for this message for a target file in a synchronize job is the following:
PresSTORE attempted to set any attributes (e.g. timestamps) and failed to open the file, that is expected to be there. This could appear due to an erroneous interpretation of the name in PresSTORE, e.g. the file "~a2145" is such an example, but this may also arise when the target file system is not ok.

Not owner or Permission denied:
Even if PresSTORE is executed with highest permissions, some situations are possible where files or directories cannot be read. E.g. on Mac OSX and on Windows, restrictive ACL settings can disallow file access for everybody excepts the owner. This error may also appear when saving files from or restoring files to a network share.

Invalid Argument, Invalid Parameter:
This error may appear when the file system in use does not support the requested operation when reading or writing files. An example is when access control lists or file streams are requested from a mounted FAT filesystem.
This error also may arise during operations normally supported on the according filesystem, in this case an error arises from the driver or the filesystem itself. Often this indicates an error in the filesystem.

I/O Error:
An I/O error is always an indication of a hardware related error. I/O errors often appear when an external disk has been switched off or disconnected during operation.

File has changed

Either the file had expanded (it grew) while it was saved OR, during a verify, the file did not correspond with the saved content.

Forced save

Files that need to be backed up had either expired, or P5 was unable to find a corresponding address on any of the volumes. This can happen if a customer reconfigured a progressive backup plan or manually relabeled volumes.


(263 vote(s))
Not helpful

Comments (4)
Loren Risker
31 October 2013 19:56
When receiving I/O errors, I can't stop the operation or restart the presstore server. How can I get past this error so I can cleanly restart the machine or job?
Andre Kuehnemund
19 November 2013 16:41
I/O errors are hardware errors and there is nothing that can be done in Presstore. You will typically need to restart the machine, killing Presstore process and the running jobs in the process. This means you'll need to re-run the job once Presstore is back up. In order to avoid future I/O errors, check your hardware, connections, make sure the drivers are up-to-date etc.
Andreas Heidenreich
24 August 2016 9:35
My backup log says Status is incomplete. In the file access log some files are mentioned, but all of them with "No error".
Which of these message should I believe, and is there a log where I see the files and folders that make the backup incomplete?
Andre Kuehnemund
31 August 2016 19:25
'No error' typically means that we're not getting an error code or description from Windows. What typically happens is that P5 (or rather the Windows built-in SYSTEM account P5 runs on top of) has insufficient permissions to the file system being read or written to. By default, SYSTEM should have full permissions to all local filesystems. The no error messages oftentimes occur with NAS or SAN volumes that are not local filesystems and SYSTEM does not have the required permissions to read or write certain file attributes like ownership, permissions, alternate streams, extended attributes etc.
Post a new comment
Full Name:
CAPTCHA Verification 
Please enter the text you see in the image into the textbox below (we use this to prevent automated submissions).