From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Marc Lehmann <schmorp@schmorp.de>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: f2fs stability problems keep me from testing
Date: Fri, 20 Nov 2015 04:56:14 +0800 [thread overview]
Message-ID: <20151119205614.GA10406@jaegeuk.local> (raw)
In-Reply-To: <20151119022317.GA7115@schmorp.de>
On Thu, Nov 19, 2015 at 03:23:17AM +0100, Marc Lehmann wrote:
> On Thu, Nov 19, 2015 at 09:29:29AM +0800, Chao Yu <chao2.yu@samsung.com> wrote:
> > Thanks for info your sharing.
> >
> > If fsck shows nothing problem in the disk, still can't see '/cold1/var' in
> > directory '/cold1' now?
>
> Ah, sorry if that might not have been clear - after a reboot, fsck showed
> no errors and all files and directories (apparently) were there, i.e. it
> looks like a transient problem, not a problem of the on-disk structure.
So, it seems that the system suffers from memory pressure significantly, which
can incur ENOMEM, as I guess.
Can you catch /sys/kernel/debug/f2fs/status at that moment?
Thanks,
>
> --
> The choice of a Deliantra, the free code+content MORPG
> -----==- _GNU_ http://www.deliantra.net
> ----==-- _ generation
> ---==---(_)__ __ ____ __ Marc Lehmann
> --==---/ / _ \/ // /\ \/ / schmorp@schmorp.de
> -=====/_/_//_/\_,_/ /_/\_\
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
------------------------------------------------------------------------------
next prev parent reply other threads:[~2015-11-19 20:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 17:24 f2fs stability problems keep me from testing Marc Lehmann
2015-11-18 10:00 ` Chao Yu
2015-11-19 0:38 ` Marc Lehmann
2015-11-19 1:29 ` Chao Yu
2015-11-19 2:23 ` Marc Lehmann
2015-11-19 20:56 ` Jaegeuk Kim [this message]
2015-11-19 1:42 ` Marc Lehmann
2015-11-19 8:04 ` Chao Yu
2015-11-19 21:01 ` Marc Lehmann
2015-11-20 1:48 ` 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=20151119205614.GA10406@jaegeuk.local \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=schmorp@schmorp.de \
/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.