Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D
darshan
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 72
    • Issues 72
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 5
    • Merge Requests 5
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • darshan
  • darshan
  • Issues
  • #216

Closed
Open
Opened Jan 09, 2017 by Glenn K. Lockwood@glock
  • Report abuse
  • New issue
Report abuse New issue

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
3.1.3
Milestone
3.1.3
Assign milestone
Time tracking
Jan 27, 2017
Due date
Jan 27, 2017
1
Labels
defect
Assign labels
  • View project labels
Reference: darshan/darshan#216