From: Sasha Levin <sasha.levin@oracle.com>
To: jaegeuk.kim@samsung.com
Cc: Dave Jones <davej@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: f2fs: kernel BUG at fs/f2fs/segment.h:543
Date: Sun, 06 Apr 2014 21:55:26 -0400 [thread overview]
Message-ID: <5342058E.4090500@oracle.com> (raw)
In-Reply-To: <1396833642.12401.12.camel@kjgkr>
On 04/06/2014 09:20 PM, Jaegeuk Kim wrote:
> Hi,
>
> Thank you for the report.
>
> If possible, could you share fsck.f2fs or dump.f2fs on the corrupted
> partition?
>
> Otherwise, how about this?
> # fdisk /dev/sdx
>> > p
Hey Jaegeuk,
Unfortunately it was a temporary filesystem inside the fuzzer that has
gone away as soon as the kernel died, so I don't have access to it.
Thanks,
Sasha
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees_APR
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sasha.levin@oracle.com>
To: jaegeuk.kim@samsung.com
Cc: linux-f2fs-devel@lists.sourceforge.net,
LKML <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>
Subject: Re: f2fs: kernel BUG at fs/f2fs/segment.h:543
Date: Sun, 06 Apr 2014 21:55:26 -0400 [thread overview]
Message-ID: <5342058E.4090500@oracle.com> (raw)
In-Reply-To: <1396833642.12401.12.camel@kjgkr>
On 04/06/2014 09:20 PM, Jaegeuk Kim wrote:
> Hi,
>
> Thank you for the report.
>
> If possible, could you share fsck.f2fs or dump.f2fs on the corrupted
> partition?
>
> Otherwise, how about this?
> # fdisk /dev/sdx
>> > p
Hey Jaegeuk,
Unfortunately it was a temporary filesystem inside the fuzzer that has
gone away as soon as the kernel died, so I don't have access to it.
Thanks,
Sasha
next prev parent reply other threads:[~2014-04-07 1:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-05 15:12 f2fs: kernel BUG at fs/f2fs/segment.h:543 Sasha Levin
2014-04-05 15:12 ` Sasha Levin
2014-04-07 1:20 ` Jaegeuk Kim
2014-04-07 1:20 ` Jaegeuk Kim
2014-04-07 1:55 ` Sasha Levin [this message]
2014-04-07 1:55 ` Sasha Levin
2014-04-07 3:40 ` Jaegeuk Kim
2014-04-07 3:40 ` Jaegeuk Kim
2014-04-09 15:51 ` Chao Yu
2014-04-09 15:51 ` [f2fs-dev] " Chao Yu
2014-04-09 15:57 ` Sasha Levin
2014-04-09 15:57 ` [f2fs-dev] " Sasha Levin
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=5342058E.4090500@oracle.com \
--to=sasha.levin@oracle.com \
--cc=davej@redhat.com \
--cc=jaegeuk.kim@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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 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.