public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-xfs@vger.kernel.org, Nikola Ciprich <nikola.ciprich@linuxbox.cz>
Subject: Re: XFS / xfs_repair - problem reading very large sparse files on very large filesystem
Date: Fri, 5 Nov 2021 15:17:19 +0100	[thread overview]
Message-ID: <20211105141719.GI32555@pcnci.linuxbox.cz> (raw)
In-Reply-To: <20211105141343.GH32555@pcnci.linuxbox.cz>

> > I'm guessing they are horrifically fragmented? What does xfs_bmap tell you
> > about the number of extents in one of these files?
> 
> unfortunately, xfs_bmap blocks on this file too:

anyways, trying to run it on another similar file, which doesn't seem
to suffer such problem (of 10TB size) shows 680657 allocation
groups which I guess is not very good..

here's the output if it is of some use:

https://storage.linuxbox.cz/index.php/s/AyZGW5Xdfxg47f6


-- 
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28.rijna 168, 709 00 Ostrava

tel.:   +420 591 166 214
fax:    +420 596 621 273
mobil:  +420 777 093 799
www.linuxbox.cz

mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------

  reply	other threads:[~2021-11-05 14:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04  9:09 XFS / xfs_repair - problem reading very large sparse files on very large filesystem Nikola Ciprich
2021-11-04 16:20 ` Eric Sandeen
2021-11-05 14:13   ` Nikola Ciprich
2021-11-05 14:17     ` Nikola Ciprich [this message]
2021-11-05 14:56       ` Eric Sandeen
2021-11-05 15:59         ` Nikola Ciprich
2021-11-05 16:11           ` Eric Sandeen
2021-11-05 16:19             ` Nikola Ciprich
2021-11-07 22:25               ` Dave Chinner
2021-11-04 23:04 ` Dave Chinner

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=20211105141719.GI32555@pcnci.linuxbox.cz \
    --to=nikola.ciprich@linuxbox.cz \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    /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