- Notifications
You must be signed in to change notification settings - Fork67
filesystems: include more remote fs types, pass them to fsck#10
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Can't many of these also be local filesystems? |
And I don't like the change to fsck -- why? |
Which ones could be local filesystems? I'm not sure how GlusterFS, or Ceph, could be available that early in the boot sequence. The list was gathered from systemd source code, mountall (Upstart mount helper) source code, and Debian init scripts. As for the fsck change: I thought it would be best if the fsck and mount commands operate on the same mountpoints and with the same information. Anything less might produce inconsistent results. Is a fsck even useful for remote filesystems? |
If gluster is started in the ramdisk for some reason, it could very well be running at that point. |
From what I have seen while digging through dracut, they fsck themselves before mounting anything (typically / or maybe /usr). |
No description provided.