All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
To: folkert <folkert@vanheusden.com>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] fsck: assertion failed
Date: Thu, 18 Jul 2013 09:34:40 +0900	[thread overview]
Message-ID: <1374107680.26443.18.camel@kjgkr> (raw)
In-Reply-To: <20130711090403.GT19245@belle.intranet.vanheusden.com>

Hi,

After I look at a glance the log, it seems you need to use the latest
f2fs sources from 
http://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs.git

I've resolved many bugs with respect to those erros showing the same
output in previous version.
And now, I do pretty much convince that current f2fs is very much stable
than older one especially wrt power-off-recovery.

Thanks,

2013-07-11 (목), 11:04 +0200, folkert:
> Hi,
> 
> Here's the result.
> It is compressed with 'xz'.
> 
> On Thu, Jul 11, 2013 at 01:31:21PM +0900, Changman Lee wrote:
> > Hello.
> > If you have the disk which fsck is failed until now, retry it with
> > attached fsck binary. And I'll appreciate if you send me the result.
> > 
> > On ???, 2013-07-08 at 08:47 +0200, folkert wrote:
> > > > Thanks for your report.
> > > > I have some questions. Did you umount and ran fsck? Otherwise, after SPO
> > > > (Sudden Power Off) did you do it?
> > > 
> > > The system had a SPO yes. The fsck was on an unmounted filesytem.
> > > 
> > > > I wish to get a dump image of your disk. However your disk is such large
> > > > one that I couldn't get it. So I have a request.
> > > > Could you try it in smaller partition again whether succeed or fail?
> > > 
> > > I cannot, of course, give a filesystem dump as that disk contains rather
> > > private data.
> > > 
> > > 
> > > Folkert van Heusden
> > > 
> > 
> 
> 
> 
> 
> Folkert van Heusden
> 
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

-- 
Jaegeuk Kim
Samsung



------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      reply	other threads:[~2013-07-18  0:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-07 10:19 [f2fs-dev] fsck: assertion failed folkert
2013-07-08  4:58 ` Changman Lee
2013-07-08  6:47   ` folkert
2013-07-11  4:31     ` Changman Lee
2013-07-11  9:04       ` folkert
2013-07-18  0:34         ` Jaegeuk Kim [this message]

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=1374107680.26443.18.camel@kjgkr \
    --to=jaegeuk.kim@samsung.com \
    --cc=folkert@vanheusden.com \
    --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.