mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: "Edwin Török" <edwin@etorok.net>,
	"Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: XFS in-memory corruption with reflinks and duperemove: XFS (dm-4): Internal error xfs_trans_cancel at line 1048 of file fs/xfs/xfs_trans.c. Caller xfs_reflink_remap_extent+0x100/0x560
Date: Wed, 6 May 2020 20:19:34 -0500	[thread overview]
Message-ID: <3fa09c4e-6233-2216-f7c8-a28bd7dcaf04@sandeen.net> (raw)
In-Reply-To: <788538c79fc331f09d335d7526f5e79484403c59.camel@etorok.net>

On 5/6/20 6:20 PM, Edwin Török wrote:
>> (Obviously, a full metadump would be useful for confirming the shape
>> of
>> the refcount btree, but...first things first let's look at the
>> filefrag
>> output.)
> I'll try to gather one, and find a place to store/share it.
> 
> Best regards,
> --Edwin

Metadumps are compact to start with and usually compress pretty well.
Obviously a very large filesystem with lots of metadata will take some
space, but it might not be that bad.

-Eric

      reply	other threads:[~2020-05-07  1:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-18 10:19 Edwin Török
2020-04-21 17:16 ` Darrick J. Wong
2020-04-27  9:15   ` Edwin Török
2020-05-04 15:21     ` Darrick J. Wong
2020-05-04 22:54       ` Edwin Török
     [not found]         ` <20200505005811.GC5716@magnolia>
     [not found]           ` <124EB800-8712-4C36-8B35-41363A558269@etorok.net>
     [not found]             ` <20200506224749.GA6730@magnolia>
2020-05-06 23:20               ` Edwin Török
2020-05-07  1:19                 ` Eric Sandeen [this message]

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=3fa09c4e-6233-2216-f7c8-a28bd7dcaf04@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=darrick.wong@oracle.com \
    --cc=edwin@etorok.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®