Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • L linux-iv
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • linux-arm
  • linux-iv
  • Repository
  • linux-iv
  • fs
  • btrfs
  • volumes.c
Find file BlameHistoryPermalink
  • David Sterba's avatar
    btrfs: fix devs_max constraints for raid1c3 and raid1c4 · cf93e15e
    David Sterba authored Nov 27, 2019
    The value 0 for devs_max means to spread the allocated chunks over all
    available devices, eg. stripe for RAID0 or RAID5. This got mistakenly
    copied to the RAID1C3/4 profiles. The intention is to have exactly 3 and
    4 copies respectively.
    
    Fixes: 47e6f742 ("btrfs: add support for 3-copy replication (raid1c3)")
    Fixes: 8d6fac00
    
     ("btrfs: add support for 4-copy replication (raid1c4)")
    Signed-off-by: default avatarDavid Sterba <dsterba@suse.com>
    cf93e15e