From: "Huang\, Ying" <ying.huang@linux.intel.com>
To: Chao Yu <chao2.yu@samsung.com>
Cc: lkp@01.org, "'LKML'" <linux-kernel@vger.kernel.org>,
"'0day robot'" <fengguang.wu@intel.com>
Subject: Re: [lkp] [f2fs] 9f88450ff1: stderr.mount:wrong_fs_type,bad_option,bad_superblock_on/dev/sda3
Date: Tue, 15 Dec 2015 12:06:07 +0800 [thread overview]
Message-ID: <87zixcpd8w.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <005401d13645$330f2950$992d7bf0$@samsung.com> (Chao Yu's message of "Mon, 14 Dec 2015 15:57:38 +0800")
[-- Attachment #1: Type: text/plain, Size: 938 bytes --]
Chao Yu <chao2.yu@samsung.com> writes:
> Hi Ying Huang,
>
>> -----Original Message-----
>> From: kernel test robot [mailto:ying.huang@linux.intel.com]
>> Sent: Monday, December 14, 2015 3:06 PM
>> To: Chao Yu
>> Cc: lkp@01.org; LKML; 0day robot
>> Subject: [lkp] [f2fs] 9f88450ff1:
>> stderr.mount:wrong_fs_type,bad_option,bad_superblock_on/dev/sda3
>>
>> FYI, we noticed the below changes on
>>
>> https://github.com/0day-ci/linux
>> Chao-Yu/f2fs-clean-up-node-page-updating-flow/20151211-161235
>> commit 9f88450ff18d8bd577ff431318f7ae00034465c0 ("f2fs: do more integrity verification for
>> superblock")
>>
>>
>> After your commit, our mounting f2fs partition operations will fail with
>> following error message. But I have no dmesg now. Do you need it?
>
> Thanks for the report! Could you please share dmesg and some info (e.g. size..)
> about storage device '/dev/sda3'.
>
The dmesg is attached.
Best Regards,
Huang, Ying
[-- Attachment #2: dmesg.xz --]
[-- Type: application/x-xz, Size: 23092 bytes --]
next prev parent reply other threads:[~2015-12-15 4:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 7:05 [lkp] [f2fs] 9f88450ff1: stderr.mount:wrong_fs_type,bad_option,bad_superblock_on/dev/sda3 kernel test robot
2015-12-14 7:57 ` Chao Yu
2015-12-15 4:06 ` Huang, Ying [this message]
2015-12-15 5:53 ` Chao Yu
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=87zixcpd8w.fsf@yhuang-dev.intel.com \
--to=ying.huang@linux.intel.com \
--cc=chao2.yu@samsung.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.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