Linux binaries or scripts will NOT run from NSS volumes on OES23.4

From an OES23.4 server (for example) "/usr/bin/ls" will execute.

If "ls" is copied to an NSS volume, it will not run:
# /media/nss/VOL201/opt/ls
-bash: /media/nss/VOL201/opt/ls: cannot execute binary file: Exec format error

strace output:
# strace /media/nss/VOL201/opt/ls
execve("/media/nss/VOL201/opt/ls", ["/media/nss/VOL201/opt/ls"], 0x7ffcdc7054f0 /* 51 vars */) = -1 ENOEXEC (Exec format error)
strace: exec: Exec format error
+++ exited with 1 +++

The same thing happens with a python or perl script on an NSS volume. However a bash script will run successfully.
All these tests run fine from an NSS volume on OES 2018 SP2 Update 10.

Raised as case 02806985. Backline Support can reproduce this issue.

Has anyone else noticed this or have an idea what's happening?

Parents Reply
  • This is a clarification:

    NSS volumes are made visible to the Linux kernel directly like any other (ext4/xfs/btrfs/...) Linux filesystem - not via the NCP filesystem or ncp2nss. Also the built-in-ncp-in-the-kernel had no role in making NSS visible to the Linux kernel.

    NSS plugs-in as yet another filesystem with the Linux kernel via the VFS (Virtual File System) interface of the Linux kernel.

No Data