Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • aports aports
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 668
    • Issues 668
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 290
    • Merge requests 290
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • alpinealpine
  • aportsaports
  • Issues
  • #12176
Closed
Open
Issue created Dec 08, 2020 by omni@omniContributor

initramfs-init can't ro mount zfs root at /sysroot

I upgraded from v3.12.1 to edge (zfs 0.8.4-r0 -> 2.0.0-r0) to see what I'd hit before v3.13.0 release and caught this.

Here we default to mounting /sysroot read-only initramfs-init.in#L510, which yields "failed: Resource busy".

Manually running mount(8) with -t zfs -o rw works and the system will boot when you exit the rescue shell. For now I have added rootflags=rw to my cmdline as a workaround but that doesn't feel right.

Edited Dec 23, 2020 by omni
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking