]> git.baikalelectronics.ru Git - kernel.git/commit
Btrfs: fix easily get into ENOSPC in mixed case
authorliubo <liubo2009@cn.fujitsu.com>
Fri, 8 Apr 2011 08:44:37 +0000 (08:44 +0000)
committerChris Mason <chris.mason@oracle.com>
Sat, 14 May 2011 20:10:26 +0000 (16:10 -0400)
commitd6504c18bfba2ac9dd4bf99c740dad0dc8a59c30
tree8e2a3dc2bceca44c1525f4815b00ef1ae275adad
parenta1fb21a62126c20962b11dc153dc5028c3763f6b
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>
fs/btrfs/extent-tree.c