https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxNzQxIiwiaGFzaCI6ImU4OTIyYzhlLWVkMTUtNDlkNS1iZGZhLWRjNWQwODZhZmJhYyJ9
1-800-691-1991 | 9am - 8pm ET
EN

Bad file descriptor error message on Linux repository with mounted NFS

Challenge

When using Linux repository with mounted NFS as a backup storage, the backup job may fail with "failed to lock file" errors:
 
[14.03.2013 13:57:13] < 65541> ERR |Bad file descriptor
[14.03.2013 13:57:13] < 65541> >> |Failed to lock file [/storage/backups/job.vbk].

Cause

Some specific storages don't support flock() file locking with their NFS implementation so the workaround is to disable flock() on the mount with nolock parameter. If it doesn't help, then please change nfsvers=4 to nfsvers=3, it should help.
This issue is particularly known for DataDomain storage.

Solution

Use the following command to mount NFS:
mount -t nfs -o nolock,hard,intr,nfsvers=3,tcp,bg xxx.xxx.xxx.xxx:/aa/bb /dd/storage/backup

More information

You can find more information about NFS-options for DataDomain here: https://community.emc.com/docs/DOC-30123
KB ID:
1741
Product:
Veeam Backup & Replication
Version:
6.x, 7
Published:
2013-03-20
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later