Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate whether it's possible to make PathResolver more resilient to long paths #70

Open
mmat11 opened this issue Feb 2, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@mmat11
Copy link
Contributor

mmat11 commented Feb 2, 2022

Podman / overlayfs:

{"event_type":"FILE_RENAME","pids": ...,"old_path":"./test","new_path":"./test2"}
mv-170700  [003] d...  9717.441932: bpf_trace_printk: path truncated
mv-170700  [003] d...  9717.441938: bpf_trace_printk: path truncated

Check if the bottleneck is PATH_RESOLVER_MAX_COMPONENTS or PATH_MAX and if it makes sense to allocate more space; evaluate how often this happen

@mmat11 mmat11 added the enhancement New feature or request label Feb 2, 2022
@fntlnz
Copy link
Contributor

fntlnz commented Feb 2, 2022

This also happens with overlayfs2, while with fuse-overlayfs it seems good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants