From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 214077] [xfstests xfs/168] xfs_repair failed with shrinking 776672
Date: Mon, 23 Aug 2021 03:17:38 +0000 [thread overview]
Message-ID: <bug-214077-201763-RkL3dJcFW6@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214077-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=214077
--- Comment #3 from Zorro Lang (zlang@redhat.com) ---
dmesg output, when xfs/168 run into fail:
[10782.980699] run fstests xfs/168 at 2021-08-16 09:29:52
[10785.856212] XFS (sda4): Mounting V5 Filesystem
[10785.960044] XFS (sda4): Ending clean mount
[10785.999747] XFS (sda4): EXPERIMENTAL online shrink feature in use. Use at
your own risk!
[10786.124668] XFS (sda4): Unmounting Filesystem
[10788.000206] XFS (sda4): Mounting V5 Filesystem
[10788.089115] XFS (sda4): Ending clean mount
[-- MARK -- Mon Aug 16 13:30:00 2021]
[10792.642459] XFS (sda4): Unmounting Filesystem
[10793.229287] XFS (sda4): Mounting V5 Filesystem
[10793.289566] XFS (sda4): Ending clean mount
[10797.115638] fsstress (111266) used greatest stack depth: 20600 bytes left
[10797.859428] XFS (sda4): Unmounting Filesystem
[10798.558178] XFS (sda4): Mounting V5 Filesystem
[10807.354979] XFS (sda4): Ending clean mount
[10810.791370] fsstress (111532) used greatest stack depth: 20312 bytes left
[10811.886076] XFS (sda4): xlog_verify_grant_tail: space > BBTOB(tail_blocks)
[10812.241353] XFS (sda4): Unmounting Filesystem
[10813.075136] XFS (sda4): Mounting V5 Filesystem
[10813.176424] XFS (sda4): Ending clean mount
[10817.343832] fsstress (111792) used greatest stack depth: 20008 bytes left
[10817.807386] XFS (sda4): Unmounting Filesystem
[10819.260537] XFS (sda4): Mounting V5 Filesystem
[10819.923391] XFS (sda4): Ending clean mount
[10824.793331] XFS (sda4): Unmounting Filesystem
[10825.701244] XFS (sda4): Mounting V5 Filesystem
[10843.028604] XFS (sda4): Ending clean mount
[10847.696262] XFS (sda4): Unmounting Filesystem
[10849.031471] XFS (sda4): Mounting V5 Filesystem
[10849.389481] XFS (sda4): Ending clean mount
[10854.117904] XFS (sda4): xlog_verify_grant_tail: space > BBTOB(tail_blocks)
[10854.117904] XFS (sda4): xlog_verify_grant_tail: space > BBTOB(tail_blocks)
[10854.626542] XFS (sda4): Unmounting Filesystem
[10855.791704] XFS (sda4): Mounting V5 Filesystem
[10860.128289] XFS (sda4): Ending clean mount
[10861.518327] XFS (sda4): Error -28 reserving per-AG metadata reserve pool.
[10861.534515] XFS (sda4): Corruption of in-memory data (0x8) detected at
xfs_ag_shrink_space+0x739/0xae0 [xfs] (fs/xfs/libxfs/xfs_ag.c:877). Shutting
down filesystem
[10861.543426] sda4: writeback error on inode 532936, offset 475136, sector
68696454
[10861.551487] XFS (sda4): Please unmount the filesystem and rectify the
problem(s)
[10862.297180] XFS (sda4): Unmounting Filesystem
[10863.893759] XFS (sda5): Unmounting Filesystem
[10864.373197] XFS (sda5): Mounting V5 Filesystem
[10864.483245] XFS (sda5): Ending clean mount
[10883.073207] XFS (sda4): Mounting V5 Filesystem
[10883.160863] XFS (sda4): Ending clean mount
[10883.190838] XFS (sda4): Unmounting Filesystem
[10883.610827] XFS (sda5): Unmounting Filesystem
[10884.278500] XFS (sda5): Mounting V5 Filesystem
[10884.322675] XFS (sda5): Ending clean mount
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-08-23 3:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 12:43 [Bug 214077] New: [xfstests xfs/168] xfs_repair failed with shrinking 776672 bugzilla-daemon
2021-08-20 13:20 ` [Bug 214077] " bugzilla-daemon
2021-08-23 3:08 ` bugzilla-daemon
2021-08-23 3:17 ` bugzilla-daemon [this message]
2021-08-23 3:37 ` bugzilla-daemon
2021-08-23 16:14 ` bugzilla-daemon
2021-08-24 3:34 ` bugzilla-daemon
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=bug-214077-201763-RkL3dJcFW6@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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 NNTP newsgroup(s).