From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 200063] XFS corruption: mismatch between format (2) and size (0) in symlink
Date: Mon, 12 Nov 2018 13:31:26 +0000 [thread overview]
Message-ID: <bug-200063-201763-KTWUnqKC4W@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200063-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=200063
--- Comment #4 from Zorro Lang (zlang@redhat.com) ---
I still can reproduce this bug on linux v4.20-rc1. So we haven't merged this
patch (in comment 3), right?
Phase 1 - find and verify superblock...
- reporting progress in intervals of 15 minutes
Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
- 14:10:29: scanning filesystem freespace - 16 of 16 allocation groups
done
- found root inode chunk
Phase 3 - for each AG...
- scan (but don't clear) agi unlinked lists...
- 14:10:29: scanning agi unlinked lists - 16 of 16 allocation groups
done
- process known inodes and perform inode discovery...
- agno = 15
- agno = 0
- agno = 1
mismatch between format (2) and size (0) in symlink ino 125888517
bad data fork in symlink 125888517
would have cleared inode 125888517
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- 14:10:32: process known inodes and inode discovery - 50048 of 50048
inodes done
- process newly discovered inodes...
- 14:10:32: process newly discovered inodes - 16 of 16 allocation
groups done
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- 14:10:32: setting up duplicate extent list - 16 of 16 allocation
groups done
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 13
- agno = 2
- agno = 3
- agno = 5
- agno = 4
- agno = 6
- agno = 7
- agno = 9
- agno = 11
- agno = 10
- agno = 8
- agno = 14
- agno = 12
- agno = 15
- agno = 1
mismatch between format (2) and size (0) in symlink ino 125888517
bad data fork in symlink 125888517
would have cleared inode 125888517
- 14:10:32: check for inodes claiming duplicate blocks - 50048 of 50048
inodes done
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...
- 14:10:33: verify and correct link counts - 16 of 16 allocation groups
done
--
You are receiving this mail because:
You are watching the assignee of the bug.
next parent reply other threads:[~2018-11-12 23:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-200063-201763@https.bugzilla.kernel.org/>
2018-11-12 13:31 ` bugzilla-daemon [this message]
2018-11-12 22:08 ` [Bug 200063] XFS corruption: mismatch between format (2) and size (0) in symlink Dave Chinner
2018-11-12 22:08 ` 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-200063-201763-KTWUnqKC4W@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).