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

Add way to find backing store for data #56

Closed
alexlarsson opened this issue Jul 18, 2022 · 2 comments
Closed

Add way to find backing store for data #56

alexlarsson opened this issue Jul 18, 2022 · 2 comments

Comments

@alexlarsson
Copy link
Collaborator

As mentioned here: ostreedev/ostree#2640 (comment)
ignition would like to be able to track which block devices as used by a mount. We can't currently always do this. For example, the mount source is a relative pathname. We should maybe make this an absolute pathname?

There might be similar issues with the basedir.

@alexlarsson
Copy link
Collaborator Author

We do expose all the backing paths in the mount info, although they are relative if they were supplied relative. I looked at other stuff, and nothing in the current kernel seems to change given options to absolute paths when printed. Maybe we just need to be careful about passing important mount options by full paths when we mount stuff.

@cgwalters
Copy link
Contributor

I think this is not necessary; in general, we just need to teach tooling to look at the underlying physical root filesystem, which is done in coreos/coreos-installer#1203

@cgwalters cgwalters closed this as not planned Won't fix, can't repro, duplicate, stale Jun 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants