From: folkert <folkert@vanheusden.com>
To: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: assertion failed
Date: Fri, 10 Jan 2014 15:25:10 +0100 [thread overview]
Message-ID: <20140110142510.GG8833@belle.intranet.vanheusden.com> (raw)
In-Reply-To: <1389338340.29315.3.camel@kjgkr>
I'll give it a new try (e.g. purged git directory and re-cloned the git
repo).
I noticed while compiling this warning:
libf2fs.c: In function '__ffs':
libf2fs.c:157:3: warning: right shift count >= width of type [enabled by default]
This means that the result is always 0.
and also
fsck.c: In function fsck_chk_inode_blk¿:
fsck.c:395:3: warning: format %d expects argument of type ¿int¿, but argument 6 has type u64 [-Wformat]
This wreaks havoc when emitting multiple arguments due to more bytes on
the stack than what is expected.
The result output is:
[FSCK] Unreachable nat entries [Fail] [0x238c]
[FSCK] SIT valid block bitmap checking [Ok..]
[FSCK] Hard link checking for regular file [Ok..] [0x0]
[FSCK] valid_block_count matching with CP [Ok..] [0x1]
[FSCK] valid_node_count matcing with CP (de lookup) [Ok..] [0xe8746]
[FSCK] valid_node_count matcing with CP (nat lookup) [Fail] [0xeaad2]
[FSCK] valid_inode_count matched with CP [Ok..] [0xe3859]
Does that mean the fsck failed?
On Fri, Jan 10, 2014 at 04:19:00PM +0900, Jaegeuk Kim wrote:
> Hi,
>
> Did you get the latest from:
> http://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs-tools.git?
>
> Since this log shows the line number differently from the latest source
> codes.
>
> For example,
>
> [fsck_chk_dentry_blk: 509] le32_to_cpu(de_blk->dentry[i].hash_code) ==
> hash_code
>
> should be:
>
> [fsck_chk_dentry_blk: 568] le32_to_cpu(de_blk->dentry[i].hash_code) ==
> hash_code
>
> Thanks,
>
> 2014-01-08 (???), 22:09 +0100, folkert:
> > Hi,
> >
> > After I installed the latest I got this error:
> >
> > build_nat_area_bitmap:1031] valid nat entries (block_addr != 0x0) [0x e65ee : 943598]
> > [build_sit_area_bitmap: 937] Blocks [0x198d273] Free Segs [0x1db2]
> > [fsck_chk_dentry_blk: 528] [ 1] - no[0x2] name[belle] len[0x5] ino[0xd1] type[0x2]
> > [fsck_chk_dentry_blk: 528] [ 2] - no[0x2] name[home] len[0x4] ino[0xd2] type[0x2]
> > [fsck_chk_dentry_blk: 528] [ 3] - no[0x2] name[sandra] len[0x6] ino[0xd3] type[0x2]
> > [fsck_chk_dentry_blk: 528] [ 4] - no[0x2] name[.less] len[0x5] ino[0xd4] type[0x1]
> > [fsck_chk_dentry_blk: 528] [ 4] - no[0x3] name[.forward] len[0x8] ino[0xd5] type[0x1]
> > [fsck_chk_dentry_blk: 528] [ 4] - no[0x4] name[.lessrc] len[0x7] ino[0xd6] type[0x1]
> > [fsck_chk_dentry_blk: 547] [ 4] Dentry Block [0x1a3980a] Done : dentries:3 in 214 slots (len:255)
> >
> > [fsck_chk_inode_blk: 377] Directory Inode: ino: d3 name: sandra depth: 1 child files: 3
> >
> > [fsck_chk_dentry_blk: 528] [ 3] - no[0x3] name[dialin] len[0x6] ino[0xd7] type[0x2]
> > [fsck_chk_dentry_blk: 528] [ 4] - no[0x2] name[.less] len[0x5] ino[0xd8] type[0x1]
> > [fsck_chk_dentry_blk: 528] [ 4] - no[0x3] name[.lessrc] len[0x7] ino[0xd9] type[0x1]
> > [fsck_chk_dentry_blk: 528] [ 4] - no[0x4] name[.bash_history] len[0xd] ino[0xda] type[0x1]
> >
> > Assertion failed!
> > [fsck_chk_dentry_blk: 509] le32_to_cpu(de_blk->dentry[i].hash_code) == hash_code
> >
> >
> > On Tue, Jan 07, 2014 at 10:01:58AM +0900, Jaegeuk Kim wrote:
> > > Hi,
> > >
> > > Thank you for the report.
> > > Could you pull the lastest f2fs-tools and then test this again?
> > > Thanks,
> > >
> > > 2014-01-02 (???), 15:56 +0100, folkert:
> > > > Hi,
> > > >
> > > > While running fsck.f2fs I get an assertion. This is with the f2fs from
> > > > git from half an hour ago:
> > > >
> > > > +--------------------------------------------------------+
> > > > | Checkpoint |
> > > > +--------------------------------------------------------+
> > > > checkpoint_ver [0x 4a7 : 1191]
> > > > user_block_count [0x 1bcce00 : 29150720]
> > > > valid_block_count [0x 19769e2 : 26700258]
> > > > rsvd_segment_count [0x 30 : 48]
> > > > overprov_segment_count [0x be4 : 3044]
> > > > free_segment_count [0x 1e7f : 7807]
> > > > 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 df99 : 57241]
> > > > cur_node_segno[1] [0x df91 : 57233]
> > > > cur_node_segno[2] [0x d565 : 54629]
> > > > cur_node_blkoff[0] [0x 1a4 : 420]
> > > > cur_node_blkoff[1] [0x 1a5 : 421]
> > > > cur_node_blkoff[2] [0x 7 : 7]
> > > > 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 dfef : 57327]
> > > > cur_data_segno[1] [0x a531 : 42289]
> > > > cur_data_segno[2] [0x a70d : 42765]
> > > > cur_data_blkoff[0] [0x 63 : 99]
> > > > cur_data_blkoff[1] [0x 13a : 314]
> > > > cur_data_blkoff[2] [0x c3 : 195]
> > > > ckpt_flags [0x 5 : 5]
> > > > cp_pack_total_block_count [0x 7 : 7]
> > > > cp_pack_start_sum [0x 1 : 1]
> > > > valid_node_count [0x e359f : 931231]
> > > > valid_inode_count [0x de77c : 911228]
> > > > next_free_nid [0x 11f16c : 1175916]
> > > > sit_ver_bitmap_bytesize [0x c0 : 192]
> > > > nat_ver_bitmap_bytesize [0x e80 : 3712]
> > > > checksum_offset [0x ffc : 4092]
> > > > elapsed_time [0x 7f5b6a : 8346474]
> > > > sit_nat_version_bitmap[0] [0x 40 : 64]
> > > >
> > > >
> > > > [build_nat_area_bitmap:1031] valid nat entries (block_addr != 0x0) [0x
> > > > e520f : 938511]
> > > > [build_sit_area_bitmap: 937] Blocks [0x19769e2] Free Segs [0x1e7f]
> > > > [fsck_chk_dentry_blk: 547] [ 4] Dentry Block [0x1a3980a] Done :
> > > > dentries:3 in 214 slots (len:255)
> > > >
> > > > [fsck_chk_inode_blk: 377] Directory Inode: ino: d3 name: sandra depth: 1
> > > > child files: 3
> > > >
> > > >
> > > > Assertion failed!
> > > > [fsck_chk_dentry_blk: 509] le32_to_cpu(de_blk->dentry[i].hash_code) ==
> > > > hash_code
> > > >
> > > >
> > > >
> > > > Folkert van Heusden
> > > >
> > >
> > > --
> > > Jaegeuk Kim
> > > Samsung
> >
> >
> > Folkert van Heusden
> >
>
> --
> Jaegeuk Kim
> Samsung
Folkert van Heusden
--
MultiTail är ett flexibel redskap för att följa en eller flera logfiler, utföra
kommandon, filtrera, färglägga, sammanfoga, o.s.v...
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
next prev parent reply other threads:[~2014-01-10 14:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 14:56 assertion failed folkert
2014-01-07 1:01 ` Jaegeuk Kim
2014-01-08 21:09 ` folkert
2014-01-10 7:19 ` Jaegeuk Kim
2014-01-10 14:25 ` folkert [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-03-23 14:22 folkert
2014-03-23 17:45 ` Kim Jaegeuk
2014-03-23 19:08 ` folkert
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=20140110142510.GG8833@belle.intranet.vanheusden.com \
--to=folkert@vanheusden.com \
--cc=jaegeuk.kim@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).