Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D darshan
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 72
    • Issues 72
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • darshan
  • darshan
  • Issues
  • #302
Closed
Open
Issue created Feb 24, 2021 by Shane Snyder@ssnyderOwner

darshan does not understand symlinks, consider using realpath

Darshan is currently confused by symlinks used on Theta at ALCF. Theta project directories are symlinks to the underlying Lustre mount point that host the files. The Darshan Lustre module is unable to associate files that are referenced via the projects symlink since they do not match the mount point Darshan associates with Lustre.

We should investigate whether realpath overheads are reasonable enough that we could use it to fully resolve user file paths and avoid this symlink issue.

Assignee
Assign to
Time tracking