| commit | f48b90756bd834dda852ff514f2690d3175b1f44 | |
| author | Josef Bacik <josef@redhat.com> | |
| Wed, 27 Jan 2010 02:07:59 +0000 (27 02:07 +0000) | ||
| committer | Chris Mason <chris.mason@oracle.com> | |
| Thu, 28 Jan 2010 21:20:39 +0000 (28 16:20 -0500) | ||
| tree | 071f502edbe6668f9451d676ae3a0f751da5e105 | treesnapshot (tar.gz zip) |
| parent | e3acc2a6850efff647f1c5458524eb3a8bcba20a | commitdiff |
Btrfs: do not mark the chunk as readonly if in degraded mode
If a RAID setup has chunks that span multiple disks, and one of those
disks has failed, btrfs_chunk_readonly will return 1 since one of the
disks in that chunk's stripes is dead and therefore not writeable. So
instead if we are in degraded mode, return 0 so we can go ahead and
allocate stuff. Without this patch all of the block groups in a RAID1
setup will end up read-only, which will mean we can't add new disks to
the array since we won't be able to make allocations.
Signed-off-by: Josef Bacik <josef@redhat.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
If a RAID setup has chunks that span multiple disks, and one of those
disks has failed, btrfs_chunk_readonly will return 1 since one of the
disks in that chunk's stripes is dead and therefore not writeable. So
instead if we are in degraded mode, return 0 so we can go ahead and
allocate stuff. Without this patch all of the block groups in a RAID1
setup will end up read-only, which will mean we can't add new disks to
the array since we won't be able to make allocations.
Signed-off-by: Josef Bacik <josef@redhat.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
| fs/btrfs/volumes.c | diffblobblamehistory |