From: Chao Yu <chao2.yu@samsung.com>
To: "'kernel test robot'" <ying.huang@linux.intel.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: Mon, 14 Dec 2015 15:57:38 +0800 [thread overview]
Message-ID: <005401d13645$330f2950$992d7bf0$@samsung.com> (raw)
In-Reply-To: <877fkhechk.fsf@yhuang-dev.intel.com>
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'.
Thanks,
>
> mount: wrong fs type, bad option, bad superblock on /dev/sda3,
> missing codepage or helper program, or other error
>
> In some cases useful info is found in syslog - try
> dmesg | tail or so.
>
>
> To reproduce:
>
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
> cd lkp-tests
> bin/lkp install job.yaml # job file is attached in this email
> bin/lkp run job.yaml
>
>
>
> Thanks,
> Ying Huang
next prev parent reply other threads:[~2015-12-14 7:58 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 [this message]
2015-12-15 4:06 ` Huang, Ying
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='005401d13645$330f2950$992d7bf0$@samsung.com' \
--to=chao2.yu@samsung.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=ying.huang@linux.intel.com \
/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