Hello Josef On Wed, May 8, 2013 at 10:47 PM, Josef Bacik <jba...@fusionio.com> wrote: > On Wed, May 08, 2013 at 11:34:40AM -0600, Alexander Skwar wrote: >> Hello Josef >> >> Did you have a chance to look at that image? Did you find anything? >> >> Or should I simply create a new filesystem and forget about the issue? >> > > So the file system isn't corrupt, you just got a giant block group for some > reason.
Hmm... Sure? I did start a "btrfs balance" and it consistently fails. See my dmesg output at http://pastebin.com/7XgAhZ1s At first, there are a few WARNING messages: [ 300.422702] WARNING: at /build/buildd/linux-3.8.0/fs/btrfs/delayed-ref.c:454 update_existing_ref+0x119/0x150 [btrfs]() [ 300.422960] WARNING: at /build/buildd/linux-3.8.0/fs/btrfs/delayed-ref.c:454 update_existing_ref+0x119/0x150 [btrfs]() … But there's also an error: [ 300.425633] BTRFS error (device dm-5) in __btrfs_inc_extent_ref:1935: Object already exists [ 300.425634] btrfs is forced readonly What can I do? Other than destroying that filesystem? Regards, Alexander -- => Google+ => http://plus.skwar.me <== => Chat (Jabber/Google Talk) => a.sk...@gmail.com <== -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
