From: Josef Bacik <jbacik@fusionio.com>
To: Mike Lowe <j.michael.lowe@gmail.com>
Cc: Josef Bacik <JBacik@fusionio.com>, Sage Weil <sage@inktank.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"billk@iinet.net.au" <billk@iinet.net.au>
Subject: Re: corrupted file size on inline extent conversion?
Date: Wed, 30 Jan 2013 14:09:40 -0500 [thread overview]
Message-ID: <20130130190940.GJ3660@localhost.localdomain> (raw)
In-Reply-To: <949A937F-7E0F-47E9-B63F-EC58E3B6370C@gmail.com>
On Wed, Jan 30, 2013 at 11:30:49AM -0700, Mike Lowe wrote:
> 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.
>
Ok since you are seeing the message I'll go ahead and post the patch and get it
moving along, let me know if you still see the problem. Thanks,
Josef
next prev parent reply other threads:[~2013-01-30 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 0:12 corrupted file size on inline extent conversion? Sage Weil
2013-01-29 14:54 ` Josef Bacik
2013-01-30 18:17 ` Mike Lowe
2013-01-30 18:22 ` Josef Bacik
2013-01-30 18:30 ` Mike Lowe
2013-01-30 19:09 ` Josef Bacik [this message]
2013-02-05 0:04 ` Sage Weil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130130190940.GJ3660@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=billk@iinet.net.au \
--cc=j.michael.lowe@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sage@inktank.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).