From: folkert <folkert@vanheusden.com>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] fsck: assertion failed
Date: Sun, 7 Jul 2013 12:19:30 +0200 [thread overview]
Message-ID: <20130707101930.GD19245@belle.intranet.vanheusden.com> (raw)
Hello,
Trying to fsck an f2fs volume. This gives an assertion failed:
+--------------------------------------------------------+
| Checkpoint |
+--------------------------------------------------------+
checkpoint_ver [0x 82 : 130]
user_block_count [0x 1bcfe00 : 29163008]
valid_block_count [0x cb2600 : 13313536]
rsvd_segment_count [0x 19 : 25]
overprov_segment_count [0x bce : 3022]
free_segment_count [0x 84b3 : 33971]
alloc_type[CURSEG_HOT_NODE] [0x 0 : 0]
alloc_type[CURSEG_WARM_NODE] [0x 0 : 0]
alloc_type[CURSEG_COLD_NODE] [0x 0 : 0]
cur_node_segno[0] [0x e4e6 : 58598]
cur_node_segno[1] [0x e546 : 58694]
cur_node_segno[2] [0x e902 : 59650]
cur_node_blkoff[0] [0x 5c : 92]
cur_node_blkoff[1] [0x 91 : 145]
cur_node_blkoff[2] [0x 1b8 : 440]
alloc_type[CURSEG_HOT_DATA] [0x 0 : 0]
alloc_type[CURSEG_WARM_DATA] [0x 0 : 0]
alloc_type[CURSEG_COLD_DATA] [0x 0 : 0]
cur_data_segno[0] [0x e3ff : 58367]
cur_data_segno[1] [0x 219e : 8606]
cur_data_segno[2] [0x e4a3 : 58531]
cur_data_blkoff[0] [0x 152 : 338]
cur_data_blkoff[1] [0x 63 : 99]
cur_data_blkoff[2] [0x 11b : 283]
ckpt_flags [0x 5 : 5]
cp_pack_total_block_count [0x 7 : 7]
cp_pack_start_sum [0x 1 : 1]
valid_node_count [0x ccdba : 839098]
valid_inode_count [0x cb031 : 831537]
next_free_nid [0x 113607 : 1127943]
sit_ver_bitmap_bytesize [0x c0 : 192]
nat_ver_bitmap_bytesize [0x e80 : 3712]
checksum_offset [0x ffc : 4092]
elapsed_time [0x 2d76c1 : 2979521]
sit_nat_version_bitmap[0] [0x 81 : 129]
[build_nat_area_bitmap:1031] valid nat entries (block_addr != 0x0) [0x ce30b : 844555]
[build_sit_area_bitmap: 937] Blocks [0xcb2600] Free Segs [0x84b3]
Assertion failed!
[fsck_chk_dentry_blk: 509] le32_to_cpu(de_blk->dentry[i].hash_code) == hash_code
Folkert van Heusden
--
Ever wonder what is out there? Any alien races? Then please support
the seti@home project: setiathome.ssl.berkeley.edu
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
next reply other threads:[~2013-07-07 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-07 10:19 folkert [this message]
2013-07-08 4:58 ` [f2fs-dev] fsck: assertion failed 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
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=20130707101930.GD19245@belle.intranet.vanheusden.com \
--to=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.