Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
aports
aports
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 649
    • Issues 649
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 206
    • Merge Requests 206
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • alpine
  • aportsaports
  • Issues
  • #612

Closed
Open
Opened Apr 28, 2011 by iilluzion _@iilluzion

fsck should be aware of mdadm/lvm mounted file systems

By default ‘fsck’ starts before MDADM/LVM, so it could not check file system on it, but report errors. Perhaps ‘fsck’ should start strictly after ‘localmount’ script, which should be aware of MDADM and LVM partitions

(from redmine: issue id 612, created on 2011-04-28, closed on 2011-05-03)

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Alpine 2.2.0
Milestone
Alpine 2.2.0 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: alpine/aports#612