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
  • #216
Closed
Open
Issue created Jan 09, 2017 by Glenn K. Lockwood@glockDeveloper

datawarp I/O being filtered out due to its location in /var

I/O activity targeted at files residing in DataWarp is being filtered out of the Darshan log. DataWarp currently mounts its partitions in

/var/opt/cray/dws/mounts/batch/XXXX/ss

where XXXX is the Slurm jobid, but commit 07ff011f excluded everything under /var from being tracked.

Do we

  1. create a whitelist that overrides the blacklist
  2. undo 07ff011f (probably not...it was added for a reason)
  3. something else
Assignee
Assign to
Time tracking