[PR #1716] [MERGED] Add initiator pid, uid and gid to a debug log #2138

New issue

Closed

opened 2026-03-04 02:03:57 +03:00 by kerem · 0 comments

kerem commented

2026-03-04 02:03:57 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/1716
Author: @dolfinus
Created: 7/6/2021
Status: ✅ Merged
Merged: 7/10/2021
Merged by: @ggtakec

Base: master ← Head: debug_pid_info

📝 Commits (1)

45f44ee Add initiator pid, uid and gid to a debug log

📊 Changes

1 file changed (+2 additions, -0 deletions)

View changed files

📝 src/s3fs.cpp (+2 -0)

📄 Description

Details

I've discovered a lot of requests to my Minio installation from one of servers with s3fs installed.
After changing the log level to debug I saw a lot of log items that some process is recursively fetching file attributes. But I was not able to find any information about the process which made these requests - lsof could return only the information about opened files, but it does not handle get_attr kernel calls.

So I've added a debug info in the s3fs process itself. This is a really useful feature.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/s3fs-fuse/s3fs-fuse/pull/1716 **Author:** [@dolfinus](https://github.com/dolfinus) **Created:** 7/6/2021 **Status:** ✅ Merged **Merged:** 7/10/2021 **Merged by:** [@ggtakec](https://github.com/ggtakec) **Base:** `master` ← **Head:** `debug_pid_info` --- ### 📝 Commits (1) - [`45f44ee`](https://github.com/s3fs-fuse/s3fs-fuse/commit/45f44eeea855a3aee7b55c51871126ccf7eb76c0) Add initiator pid, uid and gid to a debug log ### 📊 Changes **1 file changed** (+2 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/s3fs.cpp` (+2 -0) </details> ### 📄 Description ### Details I've discovered a lot of requests to my Minio installation from one of servers with s3fs installed. After changing the log level to debug I saw a lot of log items that some process is recursively fetching file attributes. But I was not able to find any information about the process which made these requests - `lsof` could return only the information about opened files, but it does not handle `get_attr` kernel calls. So I've added a debug info in the s3fs process itself. This is a really useful feature. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>