diff options
| author | liubo <liubo2009@cn.fujitsu.com> | 2011-04-08 12:44:37 +0400 |
|---|---|---|
| committer | Chris Mason <chris.mason@oracle.com> | 2011-05-15 00:10:26 +0400 |
| commit | 1aba86d67f340a8001d67183ec32e8a62e3ec658 (patch) | |
| tree | 8e2a3dc2bceca44c1525f4815b00ef1ae275adad /Documentation/SAK.txt | |
| parent | f5de93914983bf04b92a786d1d205286fc53b49b (diff) | |
| download | linux-1aba86d67f340a8001d67183ec32e8a62e3ec658.tar.xz | |
Btrfs: fix easily get into ENOSPC in mixed case
When a btrfs disk is created by mixed data & metadata option, it will have no
pure data or pure metadata space info.
In btrfs's for-linus branch, commit 78b1ea13838039cd88afdd62519b40b344d6c920
(Btrfs: fix OOPS of empty filesystem after balance) initializes space infos at
the very beginning. The problem is this initialization does not take the mixed
case into account, which will cause btrfs will easily get into ENOSPC in mixed
case.
Signed-off-by: Liu Bo <liubo2009@cn.fujitsu.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
Diffstat (limited to 'Documentation/SAK.txt')
0 files changed, 0 insertions, 0 deletions