On Fri, 08 Apr 2011 16:44:37 +0800 liubo <liubo2009@xxxxxxxxxxxxxx> wrote: > > 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@xxxxxxxxxxxxxx> > --- This morning I've got an ENOSPC OOps on --mixed (properly created this time) FS and 2.6.39-rc4 kernel. After applying this patch OOps gone away. Unfortunately, I haven't saved the trace and can't reproduce it yet. -- Sergei
Attachment:
signature.asc
Description: PGP signature
