From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [Bug 200871] F2FS experiences data loss (entry is completely lost) when an I/O failure occurs.
Date: Sat, 29 Sep 2018 01:58:03 +0000 [thread overview]
Message-ID: <bug-200871-202145-eRTgTy4XY3@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200871-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=200871
--- Comment #15 from Chao Yu (chao@kernel.org) ---
diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
index 71f5953..1b5d391 100644
--- a/fs/f2fs/data.c
+++ b/fs/f2fs/data.c
@@ -114,6 +114,11 @@ static void f2fs_write_end_io(struct bio *bio)
mapping_set_error(page->mapping, -EIO);
if (type == F2FS_WB_CP_DATA)
f2fs_stop_checkpoint(sbi, true);
+ printk("f2fs_write_end_io, ino:%lu, idx:%lu, eio:%d,
type:%d\n",
+ page->mapping->host->i_ino,
+ page->index,
+ test_bit(AS_EIO, &page->mapping->flags),
+ type);
}
f2fs_bug_on(sbi, page->mapping == NODE_MAPPING(sbi) &&
diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
index 5907775..76ac293 100644
--- a/fs/f2fs/node.c
+++ b/fs/f2fs/node.c
@@ -1912,6 +1912,8 @@ int f2fs_wait_on_node_pages_writeback(struct f2fs_sb_info
*sbi,
}
ret2 = filemap_check_errors(NODE_MAPPING(sbi));
+ printk("f2fs_wait_on_node_pages_writeback, eio:%d\n",
+ test_bit(AS_EIO, &NODE_MAPPING(sbi)->flags));
if (!ret)
ret = ret2;
Could you help to add above code to reproduce this issue in your environment?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2018-09-29 1:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-200871-202145@https.bugzilla.kernel.org/>
2018-08-23 15:26 ` [Bug 200871] F2FS experiences data loss (entry is completely lost) when an I/O failure occurs bugzilla-daemon
2018-08-26 9:09 ` bugzilla-daemon
2018-08-26 23:43 ` bugzilla-daemon
2018-08-31 7:19 ` bugzilla-daemon
2018-09-05 21:22 ` bugzilla-daemon
2018-09-05 21:23 ` bugzilla-daemon
2018-09-05 21:23 ` bugzilla-daemon
2018-09-05 21:40 ` bugzilla-daemon
2018-09-05 21:42 ` bugzilla-daemon
2018-09-21 1:50 ` Sotirios-Efstathios Maneas
2018-09-21 2:18 ` bugzilla-daemon
2018-09-21 8:50 ` bugzilla-daemon
2018-09-23 4:16 ` bugzilla-daemon
2018-09-26 8:48 ` bugzilla-daemon
2018-09-26 9:13 ` bugzilla-daemon
2018-09-26 9:45 ` bugzilla-daemon
2018-09-29 1:58 ` bugzilla-daemon [this message]
2018-10-07 1:50 ` bugzilla-daemon
2018-10-16 1:48 ` 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-200871-202145-eRTgTy4XY3@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 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).