void-linux / void-linux/void-runit
03-filesystems.sh: too emergency_shell prone?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 245
- Forks
- 67
- Avg merge
- 2d
- Merged PRs (30d)
- 2
Description
In particular I was bitten by
[ -x /bin/btrfs ] && btrfs device scan || emergency_shell
Since I don't use it I had blacklisted the btrfs module, causing btrfs device scan to fail.
It's very unfortunate when emergency_shell is triggered without a real cause, since my headless maching gets stuck until I can go to school to fix it (i.e. type "exit" at the shell).
I should point out that this particular server I switched from debian to void when I got fed up with systemd-mount doing exactly that thing... (blocking the boot).
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 by reading 03-filesystems.sh, especially the btrfs device scan and emergency_shell command. Reproduce or trace the behavior with btrfs unavailable or its module blacklisted, then determine which scan failures should be fatal. Done means the filesystem script no longer blocks a headless boot for an optional btrfs scan failure, while genuine filesystem problems still receive appropriate handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100