All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [Bug 203197] kernel read fault at __is_cp_guaranteed
Date: Tue, 09 Apr 2019 14:58:45 +0000	[thread overview]
Message-ID: <bug-203197-202145-1CdizX7ADp@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203197-202145@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=203197

Chao Yu (chao@kernel.org) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |chao@kernel.org

--- Comment #1 from Chao Yu (chao@kernel.org) ---
I only got below info when reproducing this bug in 5.1-rc1 kernel.

[  258.605917] F2FS-fs (loop0): Mismatch start address, segment0(512)
cp_blkaddr(4293329408)
[  258.605917] F2FS-fs (loop0): Can't find valid F2FS filesystem in 2th
superblock
[  258.637909] F2FS-fs (loop0): Try to recover 2th superblock, ret: 0
[  258.637912] F2FS-fs (loop0): Mounted with checkpoint version = 7548c2d6
[  334.914699] F2FS-fs (loop0): sanity_check_inode: corrupted inode i_blocks
i_ino=7 iblocks=0, run fsck to fix.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  reply	other threads:[~2019-04-09 14:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 11:32 [Bug 203197] New: kernel read fault at __is_cp_guaranteed bugzilla-daemon
2019-04-09 14:58 ` bugzilla-daemon [this message]
2019-04-10  0:55 ` [Bug 203197] " bugzilla-daemon
2019-04-11  1:03 ` 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-203197-202145-1CdizX7ADp@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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.