linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Lakshmipathi.G" <lakshmipathi.g@giis.co.in>
To: dsterba@suse.cz, quwenruo@cn.fujitsu.com, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: btrfs-convert: Add larger device support
Date: Tue, 2 May 2017 20:58:41 +0530	[thread overview]
Message-ID: <20170502152840.GA3719@giis.co.in> (raw)
In-Reply-To: <20170502150601.GK23260@twin.jikos.cz>

On Tue, May 02, 2017 at 05:06:01PM +0200, David Sterba wrote:
> On Thu, Apr 27, 2017 at 03:35:34PM +0530, Lakshmipathi.G wrote:
> > Bug: Fail to convert 22TB EXT4 to BTRFS
> > https://bugzilla.kernel.org/show_bug.cgi?id=194795
> 
> Thanks for working on the bug, the proposed fix looks good to me judging
> by the use of extended API. This would need a test though. I'm trying
> this on a sparse file, 3TB occupies 50G and is slow to create.
> Conversion works and hasn't finished yet, so this is not suitable for
> tests run by default.
> 
> Please write a more detailed changelog, a reference to bugzilla is not
> really sufficient.

Sure, will send a patch with better commit description about the bug and
proposed fix. 

Cheers.
Lakshmipathi.G

  reply	other threads:[~2017-05-02 15:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-27 10:05 [PATCH] btrfs-progs: btrfs-convert: Add larger device support Lakshmipathi.G
     [not found] ` <3907c93a-c525-5874-8d14-594f66383261@cn.fujitsu.com>
     [not found]   ` <016db1e7-c9d5-a8ec-1d64-cbd08f14503d@cn.fujitsu.com>
2017-04-28  5:55     ` Lakshmipathi.G
2017-05-02 15:06 ` David Sterba
2017-05-02 15:28   ` Lakshmipathi.G [this message]
2017-05-02 15:35   ` David Sterba
2017-05-03 16:38     ` Lakshmipathi.G
2017-05-09 14:16       ` Lakshmipathi.G
2017-05-09 15:41         ` David Sterba
2017-05-09 17:15           ` Lakshmipathi.G

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=20170502152840.GA3719@giis.co.in \
    --to=lakshmipathi.g@giis.co.in \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo@cn.fujitsu.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).