From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 214077] New: [xfstests xfs/168] xfs_repair failed with shrinking 776672
Date: Mon, 16 Aug 2021 12:43:53 +0000 [thread overview]
Message-ID: <bug-214077-201763@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=214077
Bug ID: 214077
Summary: [xfstests xfs/168] xfs_repair failed with shrinking
776672
Product: File System
Version: 2.5
Kernel Version: v5.14-rc4 + xfs-5.15-merge-1
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: XFS
Assignee: filesystem_xfs@kernel-bugs.kernel.org
Reporter: zlang@redhat.com
Regression: No
Created attachment 298333
--> https://bugzilla.kernel.org/attachment.cgi?id=298333&action=edit
xfs-168.full
xfstests xfs/168 fails on ppc64le with xfs-linux kernel xfs-5.15-merge-1:
FSTYP -- xfs (debug)
PLATFORM -- Linux/ppc64le ibm-p9z-06-lp1 5.14.0-rc4+ #1 SMP Mon Aug 16
05:26:46 EDT 2021
MKFS_OPTIONS -- -f -m crc=1,finobt=1,reflink=1,rmapbt=1,bigtime=1,inobtcount=1
-b size=1024 /dev/sda3
MOUNT_OPTIONS -- -o context=system_u:object_r:root_t:s0 /dev/sda3
/mnt/xfstests/scratch
xfs/168 [failed, exit status 1]- output mismatch (see
/var/lib/xfstests/results//xfs/168.out.bad)
--- tests/xfs/168.out 2021-08-16 08:00:55.599141174 -0400
+++ /var/lib/xfstests/results//xfs/168.out.bad 2021-08-16
08:03:59.237993851 -0400
@@ -1,2 +1,3 @@
QA output created by 168
-Silence is golden
+xfs_repair failed with shrinking 776672
+(see /var/lib/xfstests/results//xfs/168.full for details)
...
(Run 'diff -u /var/lib/xfstests/tests/xfs/168.out
/var/lib/xfstests/results//xfs/168.out.bad' to see the entire diff)
Ran: xfs/168
Failures: xfs/168
Failed 1 of 1 tests
Part of .full output:
...
...
xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: No space left on device
meta-data=/dev/sda3 isize=512 agcount=2, agsize=517120 blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=1, rmapbt=1
= reflink=1 bigtime=1 inobtcount=1
data = bsize=1024 blocks=776673, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0, ftype=1
log =internal log bsize=1024 blocks=6011, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
fsstress: check_cwd failure
fsstress: check_cwd failure
fsstress: check_cwd failure
xfs_growfs: /mnt/xfstests/scratch is not a mounted XFS filesystem
xfs_growfs: /mnt/xfstests/scratch is not a mounted XFS filesystem
xfs_growfs: /mnt/xfstests/scratch is not a mounted XFS filesystem
xfs_growfs: /mnt/xfstests/scratch is not a mounted XFS filesystem
xfs_growfs: /mnt/xfstests/scratch is not a mounted XFS filesystem
xfs_growfs: /mnt/xfstests/scratch is not a mounted XFS filesystem
xfs_growfs: /mnt/xfstests/scratch is not a mounted XFS filesystem
xfs_growfs: /mnt/xfstests/scratch is not a mounted XFS filesystem
xfs_growfs: /mnt/xfstests/scratch is not a mounted XFS filesystem
xfs_growfs: /mnt/xfstests/scratch is not a mounted XFS filesystem
xfs_growfs: /mnt/xfstests/scratch is not a mounted XFS filesystem
xfs_growfs: /mnt/xfstests/scratch is not a mounted XFS filesystem
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
ALERT: The filesystem has valuable metadata changes in a log which is being
ignored because the -n option was used. Expect spurious inconsistencies
which may be resolved by first mounting the filesystem to replay the log.
- scan filesystem freespace and inode maps...
- found root inode chunk
Phase 3 - for each AG...
- scan (but don't clear) agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
- traversing filesystem ...
- traversal finished ...
- moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.
xfs_repair failed with shrinking 776672
Please check the attachment to get full .full output file
--
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 reply other threads:[~2021-08-16 12:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 12:43 bugzilla-daemon [this message]
2021-08-20 13:20 ` [Bug 214077] [xfstests xfs/168] xfs_repair failed with shrinking 776672 bugzilla-daemon
2021-08-23 3:08 ` bugzilla-daemon
2021-08-23 3:17 ` bugzilla-daemon
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@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.