On Wed, Jun 27, 2012 at 11:45 AM, Josef Bacik [off-list ref] wrote:

On Wed, Jun 27, 2012 at 10:32:22AM -0600, Chester wrote:

quoted

Hey Josef, the btrfsck was dirty. Here it is pasted inline.

Ok, do btrfsck --repair on the device (the device must be unmounted) and
hopefully it will fix everything.  Thanks,

Josef

After a --repair run, the extent problem is fixed, but I'm having
another issue where it has a bunch of

warning, bad space info total_bytes NNNNNNN

and then

root 268 inode 199959 errors 4c0
root 804 inode 199959 errors 4c0
root 949 inode 199959 errors 4c0
root 951 inode 199959 errors 4c0
root 1249 inode 199959 errors 4c0