Unsolved
1 Rookie
•
6 Posts
0
64
January 22nd, 2026 21:03
Powerscale API (namespace) and symbolic links
PowerScale 9.10
API Version 21 (namespace says 1.0)
Say, I have a file /ifs/share/file1 and two symboolic links file2 and file3 in the same directory as file1.
file2 is a relative symlink that points to file1 created with: ln -s file1 file2
file3 is a full path symlink points to something that does not resolve on a powerscale node (target is on an nfs client's system). Created with: ln -s /localdir/myfile file3
Now, Powerscale CAN resolve file2, but can't resolve file3 (that's fine, not the issue)
I would like to get the ACL for these 3 files. The desire is for file2 and file3 to get the ACL for the symlink file, NOT the target file
So:
GET {apihost:port}/namespace/ifs/share/file1?acl
works fine
GET {apihost:port}/namespace/ifs/share/file2?acl
returns the info about file1, not file 2 (hint, different owners/group to make it obvious)
GET {apihost:port}/namespace/ifs/share/file3?acl
returns a 404
Is there some way to do the operations on the symlink file, not the target of the symlink?
Google's unhelpfull "AI" suggested "add resolve=false" query parameter, which doesn't do anything, not documented, no idea where it halucinated that from...
Thanks


Phil.Lam
3 Apprentice
•
637 Posts
0
February 16th, 2026 21:53
@JamesD2 , have you tried CLI command ls -led?
ls -led /ifs/share/file3
JamesD2
1 Rookie
•
6 Posts
0
February 18th, 2026 13:25
It's part of a management application we are writing, so CLI isn't going to help.
After talking with support, the magic parameters are:
follow_symlinks=0&worm
And then it will return the info about the symlink.