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.

Sign up for GitHub

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

Jump to bottom

Request for additional documentation around use of the :z flag on large volumes with many files #16575

Closed
Surfrdan opened this issue Nov 21, 2022 · 3 comments · Fixed by #16922
Closed

Request for additional documentation around use of the :z flag on large volumes with many files #16575

Surfrdan opened this issue Nov 21, 2022 · 3 comments · Fixed by #16922
Labels
kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. stale-issue

Comments

@Surfrdan
Copy link

/kind feature

When mounting a large volume containing a large number of files and using the :z mount flag, podman run and subsequemtly, other podman commands hang with no reporting to the user. If this is required behaviour, can there be some additional reporting to the user on what is happening under the hood instead of hanging silently. In my case mounting several terabytes of millions of files,the command was hanging for multiple days

If anyone is experiencing the same issue, what worked for me was @mheon 's recommendation of removing the :z flag and using --security-opt label=disable instead (from #16541 16541)
@openshift-ci openshift-ci bot added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 21, 2022
@mheon
Copy link
Member

mheon commented Nov 21, 2022

On the Podman side, we can add logging for progress on :z, ensure that Podman does not keep the container locked during it, and add documentation to the Manpages regarding potential performance implications for startup time.

@rhatdan
Copy link
Member

rhatdan commented Nov 21, 2022

I don't think we want to warn on this, it should be in the debug log though. Saying it is starting to relabel. We would have the same issue with :U as well.
Warning in the man page makes a lot of sense.

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@rhatdan rhatdan mentioned this issue Dec 22, 2022
Merged
rhatdan added a commit to rhatdan/podman that referenced this issue Dec 22, 2022
@rhatdan
Explain that relabeling/chowning of volumes can take along time
d27ebf2 
Users are surprised when chowning large volumes how long it can take
to relabel of chown the entire directory tree. This PR updates the
documentation to explain this fact to the user.

Fixes: containers#16575

Signed-off-by: Daniel J Walsh <[email protected]>
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 6, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 6, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. stale-issue
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[CI:DOCS] Explain that relabeling/chowning of volumes can take along time rhatdan/podman
3 participants
@Surfrdan @rhatdan @mheon