From: "Arkadiusz Miśkiewicz" <a.miskiewicz@gmail.com>
To: linux-xfs@vger.kernel.org
Subject: xfs_repair doesn't handle: br_startoff 8388608 br_startblock -2 br_blockcount 1 br_state 0 corruption
Date: Wed, 15 Jul 2020 09:05:47 +0200 [thread overview]
Message-ID: <744867e7-0457-46c6-f14b-8d7b91a61bbc@gmail.com> (raw)
Hello.
xfs_repair (from for-next from about 2-3 weeks ago) doesn't seem to
handle such kind of corruption. Repair (few times) finishes just fine
but it ends up again with such trace.
Metadump is possible but problematic (will be huge).
Jul 9 14:35:51 x kernel: XFS (sdd1): xfs_dabuf_map: bno 8388608 dir:
inode 21698340263
Jul 9 14:35:51 x kernel: XFS (sdd1): [00] br_startoff 8388608
br_startblock -2 br_blockcount 1 br_state 0
Jul 9 14:35:51 x kernel: XFS (sdd1): Internal error xfs_da_do_buf(1) at
line 2557 of file fs/xfs/libxfs/xfs_da_btree.c. Caller
xfs_da_read_buf+0x6a/0x120 [xfs]
Jul 9 14:35:51 x kernel: CPU: 3 PID: 2928 Comm: cp Tainted: G
E 5.0.0-1-03515-g3478588b5136 #10
Jul 9 14:35:51 x kernel: Hardware name: Supermicro X10DRi/X10DRi, BIOS
3.0a 02/06/2018
Jul 9 14:35:51 x kernel: Call Trace:
Jul 9 14:35:51 x kernel: dump_stack+0x5c/0x80
Jul 9 14:35:51 x kernel: xfs_dabuf_map.constprop.0+0x1dc/0x390 [xfs]
Jul 9 14:35:51 x kernel: xfs_da_read_buf+0x6a/0x120 [xfs]
Jul 9 14:35:51 x kernel: xfs_da3_node_read+0x17/0xd0 [xfs]
Jul 9 14:35:51 x kernel: xfs_da3_node_lookup_int+0x6c/0x370 [xfs]
Jul 9 14:35:51 x kernel: ? kmem_cache_alloc+0x14e/0x1b0
Jul 9 14:35:51 x kernel: xfs_dir2_node_lookup+0x4b/0x170 [xfs]
Jul 9 14:35:51 x kernel: xfs_dir_lookup+0x1b5/0x1c0 [xfs]
Jul 9 14:35:51 x kernel: xfs_lookup+0x57/0x120 [xfs]
Jul 9 14:35:51 x kernel: xfs_vn_lookup+0x70/0xa0 [xfs]
Jul 9 14:35:51 x kernel: __lookup_hash+0x6c/0xa0
Jul 9 14:35:51 x kernel: ? _cond_resched+0x15/0x30
Jul 9 14:35:51 x kernel: filename_create+0x91/0x160
Jul 9 14:35:51 x kernel: do_linkat+0xa5/0x360
Jul 9 14:35:51 x kernel: __x64_sys_linkat+0x21/0x30
Jul 9 14:35:51 x kernel: do_syscall_64+0x55/0x100
Jul 9 14:35:51 x kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Longer log:
http://ixion.pld-linux.org/~arekm/xfs-10.txt
--
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
next reply other threads:[~2020-07-15 7:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 7:05 Arkadiusz Miśkiewicz [this message]
2020-07-15 11:40 ` xfs_repair doesn't handle: br_startoff 8388608 br_startblock -2 br_blockcount 1 br_state 0 corruption Brian Foster
2021-03-04 8:54 ` 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=744867e7-0457-46c6-f14b-8d7b91a61bbc@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).