void-linux / void-linux/void-runit
failed to lock /etc/exports.d/zfs.exports.lock: Read-only file system in core-services/03-filesystems.sh
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 245
- Forks
- 67
- Avg merge
- 2d
- Merged PRs (30d)
- 2
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with core-services/03-filesystems.sh, especially the read-only mount at line 6, zfs share -a at line 51, and the read-write mount at line 77. Reproduce the boot sequence with a ZFS pool and inspect the runit and socklog configuration described in the issue. Done means the lock error is explained and the appropriate mount ordering or boot-log location is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100