From: Marc Lehmann <schmorp@schmorp.de>
To: Chao Yu <chao2.yu@samsung.com>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: f2fs stability problems keep me from testing
Date: Thu, 19 Nov 2015 02:42:19 +0100 [thread overview]
Message-ID: <20151119014219.GA6973@schmorp.de> (raw)
In-Reply-To: <004b01d121e8$10563730$3102a590$@samsung.com>
On Wed, Nov 18, 2015 at 06:00:40PM +0800, Chao Yu <chao2.yu@samsung.com> wrote:
> I ran fsck, and it have all "Ok" messages, I can run it again, but would
Anyways, here is the fsck output - it was made after the reboot, a fsck, and
two mounts, I think (also, kernel was upgraded).
PS: there is a typo ("matcing", don't know if it's still in git).
Info: sector size = 512
Info: total sectors = 15628050432 (7630884 MB)
Info: MKFS version
"Linux version 3.18.21-031821-generic (kernel@gloin) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04) ) #201509020527 SMP Wed Sep 2 05:29:06 UTC 2015"
Info: FSCK version
from "Linux version 3.18.24-031824-generic (kernel@gomeisa) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ) #201511031331 SMP Tue Nov 3 18:33:52 UTC 2015"
to "Linux version 3.18.24-031824-generic (kernel@gomeisa) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ) #201511031331 SMP Tue Nov 3 18:33:52 UTC 2015"
Info: superblock features = 0 :
Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000
Info: total FS sectors = 15628050432 (7630884 MB)
Info: CKPT version = 14c2
Info: checkpoint state = 5 : compacted_summary unmount
[FSCK] Unreachable nat entries [Ok..] [0x0]
[FSCK] SIT valid block bitmap checking [Ok..]
[FSCK] Hard link checking for regular file [Ok..] [0x0]
[FSCK] valid_block_count matching with CP [Ok..] [0x24dad5a5]
[FSCK] valid_node_count matcing with CP (de lookup) [Ok..] [0x9773e]
[FSCK] valid_node_count matcing with CP (nat lookup) [Ok..] [0x9773e]
[FSCK] valid_inode_count matched with CP [Ok..] [0x21bc]
[FSCK] free segment_count matched with CP [Ok..] [0x27ab81]
[FSCK] next block offset is free [Ok..]
[FSCK] fixing SIT types
[FSCK] other corrupted bugs [Ok..]
Done.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / schmorp@schmorp.de
-=====/_/_//_/\_,_/ /_/\_\
------------------------------------------------------------------------------
next prev parent reply other threads:[~2015-11-19 1:42 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
2015-11-19 1:42 ` Marc Lehmann [this message]
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=20151119014219.GA6973@schmorp.de \
--to=schmorp@schmorp.de \
--cc=chao2.yu@samsung.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.