NFS problem
-
When I mount an nfs volume on linux the capacity is recognized normally:
192.168.50.8:/vx/VMS_XCP2 103T 251G 103T 1% /run/xo-server/mounts/f2bb1ed9-f757-49cb-8e1c-42ad993d8b2a
In xoa the displayed capacity is different:
NFS_LOCAL /run/xo-server/mounts/f2bb1ed9-f757-49cb-8e1c-42ad993d8b2a 312.5 GiB / 9.87 TiB 163.81 MiB/s / 598 MiB/s None
root@xoa-ce:/var/log# journalctl -u xo-server -f -n 50 ago 02 11:24:41 xoa-ce xo-server[2976]: 2022-08-02T15:24:41.953Z xo:storage WARN Xapi#_getUnhealthyVdiChainLength(fc8571f0-7894-4240-985a-718143bb1608) { ago 02 11:24:41 xoa-ce xo-server[2976]: error: Error: no object with UUID: fc8571f0-7894-4240-985a-718143bb1608 ago 02 11:24:41 xoa-ce xo-server[2976]: at Xapi.getObjectByUuid (/opt/xen-orchestra/packages/xen-api/src/index.js:653:11) ago 02 11:24:41 xoa-ce xo-server[2976]: at Xapi._getUnhealthyVdiChainLength (file:///opt/xen-orchestra/packages/xo-server/src/xapi/mixins/storage.mjs:61:29) ago 02 11:24:41 xoa-ce xo-server[2976]: at Xapi._getUnhealthyVdiChainLength (file:///opt/xen-orchestra/packages/xo-server/src/xapi/mixins/storage.mjs:63:26) ago 02 11:24:41 xoa-ce xo-server[2976]: at file:///opt/xen-orchestra/packages/xo-server/src/xapi/mixins/storage.mjs:81:29 ago 02 11:24:41 xoa-ce xo-server[2976]: at arrayEach (/opt/xen-orchestra/node_modules/lodash/_arrayEach.js:15:9) ago 02 11:24:41 xoa-ce xo-server[2976]: at forEach (/opt/xen-orchestra/node_modules/lodash/forEach.js:38:10) ago 02 11:24:41 xoa-ce xo-server[2976]: at Xapi.getUnhealthyVdiChainsLength (file:///opt/xen-orchestra/packages/xo-server/src/xapi/mixins/storage.mjs:78:5) ago 02 11:24:41 xoa-ce xo-server[2976]: at forEach (file:///opt/xen-orchestra/packages/xo-server/src/api/sr.mjs:875:60) ago 02 11:24:41 xoa-ce xo-server[2976]: at Array.forEach (<anonymous>) ago 02 11:24:41 xoa-ce xo-server[2976]: at Xo.apply (file:///opt/xen-orchestra/packages/xo-server/src/api/sr.mjs:874:100) ago 02 11:24:41 xoa-ce xo-server[2976]: at file:///opt/xen-orchestra/packages/xo-server/src/_pDebounceWithKey.mjs:45:22 ago 02 11:24:41 xoa-ce xo-server[2976]: at Promise._execute (/opt/xen-orchestra/node_modules/bluebird/js/release/debuggability.js:384:9) ago 02 11:24:41 xoa-ce xo-server[2976]: at Promise._resolveFromExecutor (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:518:18) ago 02 11:24:41 xoa-ce xo-server[2976]: at new Promise (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:103:10) ago 02 11:24:41 xoa-ce xo-server[2976]: at Xo.call (file:///opt/xen-orchestra/packages/xo-server/src/_pDebounceWithKey.mjs:44:20) ago 02 11:24:41 xoa-ce xo-server[2976]: at Api.#callApiMethod (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.mjs:306:33) ago 02 11:24:41 xoa-ce xo-server[2976]: }
root@xoa-ce:/var/log# systemctl status xo-server.service xo-server.service - XO Server Loaded: loaded (/lib/systemd/system/xo-server.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2022-08-02 10:51:35 -04; 35min ago Main PID: 2976 (node) Tasks: 100 (limit: 19043) Memory: 14.6G CPU: 1h 27min 46.856s CGroup: /system.slice/xo-server.service ├─2976 /usr/local/bin/node ./dist/cli.mjs ├─3808 /usr/local/bin/node /opt/xen-orchestra/@xen-orchestra/backups/_backupWorker.js ├─3849 /usr/local/bin/node /opt/xen-orchestra/@xen-orchestra/backups/_backupWorker.js ├─3863 /usr/local/bin/node /opt/xen-orchestra/@xen-orchestra/backups/_backupWorker.js ├─3886 /usr/local/bin/node /opt/xen-orchestra/@xen-orchestra/backups/_backupWorker.js ├─3915 /usr/local/bin/node /opt/xen-orchestra/@xen-orchestra/backups/_backupWorker.js ├─3929 /usr/local/bin/node /opt/xen-orchestra/@xen-orchestra/backups/_backupWorker.js ├─3941 /usr/local/bin/node /opt/xen-orchestra/@xen-orchestra/backups/_backupWorker.js └─3954 /usr/local/bin/node /opt/xen-orchestra/@xen-orchestra/backups/_backupWorker.js ago 02 11:26:49 xoa-ce xo-server[2976]: at forEach (file:///opt/xen-orchestra/packages/xo-server/src/api/sr.mjs:875:60) ago 02 11:26:49 xoa-ce xo-server[2976]: at Array.forEach (<anonymous>) ago 02 11:26:49 xoa-ce xo-server[2976]: at Xo.apply (file:///opt/xen-orchestra/packages/xo-server/src/api/sr.mjs:874:100) ago 02 11:26:49 xoa-ce xo-server[2976]: at file:///opt/xen-orchestra/packages/xo-server/src/_pDebounceWithKey.mjs:45:22 ago 02 11:26:49 xoa-ce xo-server[2976]: at Promise._execute (/opt/xen-orchestra/node_modules/bluebird/js/release/debuggability.js:384:9) ago 02 11:26:49 xoa-ce xo-server[2976]: at Promise._resolveFromExecutor (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:518:18) ago 02 11:26:49 xoa-ce xo-server[2976]: at new Promise (/opt/xen-orchestra/node_modules/bluebird/js/release/promise.js:103:10) ago 02 11:26:49 xoa-ce xo-server[2976]: at Xo.call (file:///opt/xen-orchestra/packages/xo-server/src/_pDebounceWithKey.mjs:44:20) ago 02 11:26:49 xoa-ce xo-server[2976]: at Api.#callApiMethod (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.mjs:306:33) ago 02 11:26:49 xoa-ce xo-server[2976]: }
-
Could it be an overflow when we parse the mount info? Any idea @julien-f ?
edit: @infraestrutura are you on XOA or XO from the sources? Is it fully up to date?
-
@olivierlambert Yep, it's a known issue: https://github.com/vatesfr/xen-orchestra/issues/5637
As it's pretty rare, not a big deal and hard to fix, it's still here.
-
@julien-f
But this problem is just visualization or does it interfere with the backup? -
@infraestrutura Just display, it does not impact anything else.