I've been running rsync against a rbd device backed by btrfs filesystems that are about 11% full for about 45 minutes before I checked and noticed the printk message. That was the first go with the patch. Seems like I was able to get by without any problems until the btrfs filesystems got some use and filled up a little bit.
On Jan 30, 2013, at 1:22 PM, Josef Bacik <jba...@fusionio.com> wrote: > On Wed, Jan 30, 2013 at 11:17:25AM -0700, Mike Lowe wrote: >> Well I found this, so I think it's likely: >> >> root@gwboss2:~# dmesg |grep bitten >> [ 3196.193238] this would have bitten us in the ass >> [ 3196.193784] this would have bitten us in the ass >> > > Well that makes me happy since I had almost talked myself out of this being a > possiblity. How long did it take you to hit this problem before and how long > have you been running with this patch? Thanks, > > Josef -- 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
