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

failed to lock /etc/exports.d/zfs.exports.lock: Read-only file system in core-services/03-filesystems.sh #117

Open
lzhoucs opened this issue May 26, 2024 · 1 comment

Comments

@lzhoucs
Copy link

lzhoucs commented May 26, 2024

It seems we are mounting the zfs pool as read-only first, then zfs share -a will attempt to place a lock /etc/exports.d/zfs.exports.lock which causes the issue in the title. I wonder if we should mount the pool as read-write earlier to avoid the error?

Also a separate question, how do I check the log for the runit boot process? I literally took a screenshot during booting to create this issue. I've setup socklog according to the docs, but I couldn't find the error: failed to lock /etc/exports.d/zfs.exports.lock: Read-only file system anywhere in the /var/log.

@leahneukirchen
Copy link
Member

I think only the zfs share operation should be moved behind the remount rw.

Void doesn't keep logs from boot output, unfortunately.

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