From: Zhang Yi <yi.zhang@huaweicloud.com>
To: Guangwu Zhang <guazhang@redhat.com>,
linux-block@vger.kernel.org, linux-xfs@vger.kernel.org,
fstests@vger.kernel.org
Subject: Re: [bug report] Internal error isnullstartblock(got.br_startblock) a t line 6005 of file fs/xfs/libxfs/xfs_bmap.c.
Date: Tue, 21 May 2024 13:05:00 +0800 [thread overview]
Message-ID: <ae36c333-29fe-1bfd-9558-894b614e916d@huaweicloud.com> (raw)
In-Reply-To: <CAGS2=Ypq9_X23syZw8tpybjc_hPk7dQGqdYNbpw0KKN1A1wbNA@mail.gmail.com>
On 2024/5/20 19:48, Guangwu Zhang wrote:
> Hi,
> I get a xfs error when run xfstests generic/461 testing with
> linux-block for-next branch.
> looks it easy to reproduce with s390x arch.
>
> kernel info :
> commit 04d3822ddfd11fa2c9b449c977f340b57996ef3d
> 6.9.0+
> reproducer
> git clone xfstests
> ./check generic/461
>
>
I guess this issue should be fixed by 5ce5674187c3 ("xfs: convert delayed
extents to unwritten when zeroing post eof blocks"), please merge this commit
series (include 4 patches) and try again.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5ce5674187c345dc31534d2024c09ad8ef29b7ba
Yi.
> [ 5322.046654] XFS (loop1): Internal error isnullstartblock(got.br_startblock) a
> t line 6005 of file fs/xfs/libxfs/xfs_bmap.c. Caller xfs_bmap_insert_extents+0x
> 2ee/0x420 [xfs]
> [ 5322.046859] CPU: 0 PID: 157526 Comm: fsstress Kdump: loaded Not tainted 6.9.0
> + #1
> [ 5322.046863] Hardware name: IBM 8561 LT1 400 (z/VM 7.2.0)
> [ 5322.046864] Call Trace:
> [ 5322.046866] [<0000022f504d8fc4>] dump_stack_lvl+0x8c/0xb0
> [ 5322.046876] [<0000022ed00fc308>] xfs_corruption_error+0x70/0xa0 [xfs]
> [ 5322.046955] [<0000022ed00b7206>] xfs_bmap_insert_extents+0x3fe/0x420 [xfs]
> [ 5322.047024] [<0000022ed00f55a6>] xfs_insert_file_space+0x1be/0x248 [xfs]
> [ 5322.047105] [<0000022ed00ff1dc>] xfs_file_fallocate+0x244/0x400 [xfs]
> [ 5322.047186] [<0000022f4fe90000>] vfs_fallocate+0x218/0x338
> [ 5322.047190] [<0000022f4fe9112e>] ksys_fallocate+0x56/0x98
> [ 5322.047193] [<0000022f4fe911aa>] __s390x_sys_fallocate+0x3a/0x48
> [ 5322.047196] [<0000022f505019d2>] __do_syscall+0x23a/0x2c0
> [ 5322.047200] [<0000022f50511d20>] system_call+0x70/0x98
> [ 5322.054644] XFS (loop1): Corruption detected. Unmount and run xfs_repair
> [ 5322.977488] XFS (loop1): User initiated shutdown received.
> [ 5322.977505] XFS (loop1): Log I/O Error (0x6) detected at xfs_fs_goingdown+0xb
> 4/0xf8 [xfs] (fs/xfs/xfs_fsops.c:458). Shutting down filesystem.
> [ 5322.977772] XFS (loop1): Please unmount the filesystem and rectify the proble
> m(s)
> [ 5322.977877] loop1: writeback error on inode 755831, offset 32768, sector 1804
> 712
> 00:00:00
>
>
> .
>
next prev parent reply other threads:[~2024-05-21 5:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 11:48 [bug report] Internal error isnullstartblock(got.br_startblock) a t line 6005 of file fs/xfs/libxfs/xfs_bmap.c Guangwu Zhang
2024-05-20 15:09 ` Christoph Hellwig
2024-05-21 1:05 ` Guangwu Zhang
2024-05-21 2:16 ` Jens Axboe
2024-05-21 5:05 ` Zhang Yi [this message]
2024-05-21 10:06 ` Guangwu Zhang
2024-05-21 11:57 ` Zhang Yi
2024-05-22 0:46 ` Guangwu Zhang
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=ae36c333-29fe-1bfd-9558-894b614e916d@huaweicloud.com \
--to=yi.zhang@huaweicloud.com \
--cc=fstests@vger.kernel.org \
--cc=guazhang@redhat.com \
--cc=linux-block@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).