#1 2019-02-22 12:00:34

JackiMode
Member
Registered: 2019-02-22
Posts: 1

Problem with nfs share from QNAP

Hi,
I've got VMWare ESXi 6 and QNAP. QNAP has NFS share on witch i want to backup my virtual machines.

On ESXi:

esxcli storage nfs list
Volume Name  Host       Share  Accessible  Mounted  Read-Only   isPE  Hardware Acceleration
-----------  ---------  -----  ----------  -------  ---------  -----  ---------------------
qnap         10.0.0.61  vm           true     true      false  false  Not Supported

My job:

"/vmfs/volumes/datastore1/xsi-dir/xsibackup" \
--backup-point=/vmfs/volumes/qnap \
--backup-type=Custom \
--backup-how=Hot \
...(smtp options)...
--backup-vms=frontend1 \
--backup-prog=rsync \
--backup-id=008 \
--exec=yes >> "/vmfs/volumes/datastore1/xsi-dir/var/logs/xsibackup-job8.log"

I run:
./xsibackup --run-backup=008
but when coms to:
"Syncronizing config files"
My nfs share becomes unaccessible :

 esxcli storage nfs list
Volume Name  Host       Share  Accessible  Mounted  Read-Only   isPE  Hardware Acceleration
-----------  ---------  -----  ----------  -------  ---------  -----  ---------------------
qnap         10.0.0.61  vm          false     true      false  false  Unknown

In vSphere client under Configuration/Storage got "inactive".

Rest of log:

./xsibackup: line 1: can't create /vmfs/volumes/qnap/frontend1/frontend1.vmsd: Input/output error
cp: can't stat '/vmfs/volumes/qnap/frontend1': Input/output error
cp: can't stat '/vmfs/volumes/qnap/frontend1': Input/output error
[frontend1] info: VMWare Tools detected, taking snapshot QUIESCED(false)...
[frontend1] info: set argument --snapshot=doquiesce to quiesce your VMs
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Backing up virtual disks...
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
DISK=/vmfs/volumes/datastore1/frontend1/frontend1-000001-delta.vmdk
DISK=/vmfs/volumes/datastore1/frontend1/frontend1-000001.vmdk
DISK=/vmfs/volumes/datastore1/frontend1/frontend1-Snapshot18.vmsn
DISK=/vmfs/volumes/datastore1/frontend1/frontend1.vmdk
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
(c) XSIDiff 1.1.1.4 licensed:
A full file copy will be performed, no meta-data available
Reading from file /vmfs/volumes/datastore1/frontend1/frontend1-000001.vmdk
Error opening file on createfile() function: /vmfs/volumes/qnap/frontend1/frontend1-000001.vmdk, error: Input/output error
Error creating file2: -1
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
(c) XSIDiff 1.1.1.4 licensed:
A full file copy will be performed, no meta-data available
Reading from file /vmfs/volumes/datastore1/frontend1/frontend1-Snapshot18.vmsn
Error opening file on createfile() function: /vmfs/volumes/qnap/frontend1/frontend1-Snapshot18.vmsn, error: Input/output error
Error creating file2: -1
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
(c) XSIDiff 1.1.1.4 licensed:
A full file copy will be performed, no meta-data available
Reading from file /vmfs/volumes/datastore1/frontend1/frontend1.vmdk
Error opening file on createfile() function: /vmfs/volumes/qnap/frontend1/frontend1.vmdk, error: Input/output error
Error creating file2: -1
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
sending incremental file list
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[frontend1] CLXSITO1 error: rsync: ERROR: cannot stat destination "/vmfs/volumes/qnap/frontend1/frontend1-flat.vmdk": Input/output error (5)
rsync error: errors selecting input/output files, dirs (code 3) at main.c(634) [Receiver=3.1.0]

I've tried nfs41 also - result is the same.
Thats strange because it worked well a few months ago. Anybody have got an idea what was happened?

Last edited by JackiMode (2019-02-22 12:03:02)

Offline

#2 2019-02-24 23:16:42

admin
Administrator
Registered: 2017-04-21
Posts: 1,057

Re: Problem with nfs share from QNAP

NFS4 is broken in ESXi shell, use NFS3. NFS4 is useless for backups.

Offline

#3 2019-11-21 01:06:53

vscheuber
Member
Registered: 2019-11-18
Posts: 7

Re: Problem with nfs share from QNAP

@JackiMode, did @admin's advice help?

From your command it appears to me you were already running NFS 3 or the command wouldn't have returned any response. At least on my ESXi 6.7u1 my NFS 4.1 share on my Synology NAS only shows up when using "esxcli storage nfs41 list". When I use "esxcli storage nfs list" nothing is returned.

I'm wondering because I have backup jobs getting stuck for no apparent reason and if NFS 4.1 is really the culprit, that would be an easy fix. Just looking for some confirmation before I make the switch.

Offline

#4 2019-11-21 10:21:51

admin
Administrator
Registered: 2017-04-21
Posts: 1,057

Re: Problem with nfs share from QNAP

NFS3 is a well stablished protocol and it works well with all versions of ESXi. The only advantage NFS4 will offer you is mutipathing, but that will be useless for transferring big monolithic files. On the other side NFS4.1 will not work on some older ESXi releases. I believe ESXi 6.7 has solved that, still using NFS3 is the most recommendable option.

Offline

Board footer