SR_BACKEND_FAILURE_453(, tapdisk experienced an error [opterr=Permission denied], )

pnunn

Dabbler
Joined
Jan 31, 2015
Messages
39
Hi folks,
I've just upgraded my FreeNAS storage box to TrueNAS 12 and that would seem to have been a bad idea.

I have it acting as an NFS shared storage device for two XCP-NG hosts running XCP-NG 8.1 and now when I try and start any of the VM's on the shared storage I'm getting the above error.

I have no idea if this is an XCP problem or a TrueNAS problem, but I suspect TrueNAS.

I have tried to change the permissions on the storage (they were already a+rwx) and when I did do that I got

Oct 24 13:10:06 cwpstorage 1 2020-10-24T13:10:06.311023+10:00 cwpstorage.marketdispatch.com.au mountd 2151 - - can't open /etc/zfs/exports
Oct 24 13:10:06 cwpstorage 1 2020-10-24T13:10:06.405770+10:00 cwpstorage.marketdispatch.com.au mountd 2151 - - can't open /etc/zfs/exports
Oct 24 13:10:16 cwpstorage 1 2020-10-24T13:10:16.368608+10:00 cwpstorage.marketdispatch.com.au mountd 2151 - - can't open /etc/zfs/exports
Oct 24 13:10:16 cwpstorage 1 2020-10-24T13:10:16.503037+10:00 cwpstorage.marketdispatch.com.au mountd 2151 - - can't open /etc/zfs/exports

so I created that file (it didn't exist) and set the permissions again.

Unfortunately nothing changed.

I have cross posted this on the XCP forums as well as I'm really not sure where the issues is.

Does anyone have any idea?

Ta, Peter
 

pnunn

Dabbler
Joined
Jan 31, 2015
Messages
39
OK, turns out the issue was permissions as the messages states.

Turns out the upgrade had changed the ownership of the data set to some crazy long number rather than root, and had set the permissions to something other than a+rwx.

Changed both of those, and away we go again.

Not sure why the upgrade would have changed them though.

P.
 
Joined
Oct 24, 2020
Messages
1
Registered for a new account on here just to say this saved my behind today. I would have never thought to check these permissions, why would storage permissions change during an OS upgrade?

In any case, thank you for posting here what you experienced and how you solved it.
 
Top