From: "Arkadiusz Miśkiewicz" <a.miskiewicz@gmail.com>
To: linux-xfs@vger.kernel.org
Subject: repair: realloc(): invalid next size
Date: Mon, 8 Oct 2018 16:03:25 +0200 [thread overview]
Message-ID: <214be03d-9cc7-378b-3635-6fca3cdcb1dd@gmail.com> (raw)
Big fs, ton of small files, repair takes 36h until this happens:
rebuilding directory inode 30363993060
rebuilding directory inode 30398868604
rebuilding directory inode 30414474627
rebuilding directory inode 30425006954
rebuilding directory inode 30447937553
rebuilding directory inode 30529556616
rebuilding directory inode 30537494728
rebuilding directory inode 30569826838
rebuilding directory inode 31060721895
Metadata corruption detected at 0x41f9db, inode 0x73b5d00e7 data fork
xfs_repair: warning - iflush_int failed (-117)
Warning: recursive buffer locking at block 31060721776 detected
Metadata corruption detected at 0x41f9db, inode 0x73b5d00e7 data fork
xfs_repair: warning - iflush_int failed (-117)
Warning: recursive buffer locking at block 31060721776 detected
Metadata corruption detected at 0x41f980, inode 0x73b5d00e7 data fork
xfs_repair: warning - iflush_int failed (-117)
realloc(): invalid next size
Aborted
Fails somewhere in 0x41f9db <xfs_dir2_sf_verify+603>
Complete log at
https://ixion.pld-linux.org/~arekm/xfs-1/repair.txt
Test was done with xfs_repair 4.17.0 and 4.18.0 with the same result.
kernel 4.18.5
Running under gdb now.
Any ideas?
--
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
next reply other threads:[~2018-10-08 21:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 14:03 Arkadiusz Miśkiewicz [this message]
2018-10-08 14:26 ` repair: realloc(): invalid next size Eric Sandeen
2018-10-08 14:42 ` Eric Sandeen
2018-10-09 13:49 ` Arkadiusz Miśkiewicz
2018-10-09 18:48 ` Arkadiusz Miśkiewicz
2018-10-12 7:52 ` Arkadiusz Miśkiewicz
-- strict thread matches above, loose matches on Subject: below --
2018-10-08 10:52 Arkadiusz Miśkiewicz
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=214be03d-9cc7-378b-3635-6fca3cdcb1dd@gmail.com \
--to=a.miskiewicz@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).