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 13:22:13 -0500 [thread overview]
Message-ID: <20130130182213.GI3660@localhost.localdomain> (raw)
In-Reply-To: <08479684-218C-4B6E-8D76-DE39B36EE12E@gmail.com>
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
next prev parent reply other threads:[~2013-01-30 18:22 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 [this message]
2013-01-30 18:30 ` Mike Lowe
2013-01-30 19:09 ` Josef Bacik
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=20130130182213.GI3660@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