[f2fs-dev] fsck: assertion failed

[f2fs-dev] fsck: assertion failed

[folkert]

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

Re: [f2fs-dev] fsck: assertion failed

[Changman Lee]

Thanks for your report.

I have some questions. Did you umount and ran fsck? Otherwise, after SPO
(Sudden Power Off) did you do it?

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?


On 일, 2013-07-07 at 12:19 +0200, folkert wrote:
> 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
> 



------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

Re: [f2fs-dev] fsck: assertion failed

[folkert]

> 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

-- 
www.vanheusden.com/multitail - multitail is tail on steroids. multiple
               windows, filtering, coloring, anything you can think of
----------------------------------------------------------------------
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

Re: [f2fs-dev] fsck: assertion failed

[Changman Lee]

[-- Attachment #1: Type: text/plain, Size: 764 bytes --]

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
> 



[-- Attachment #2: fsck.tgz --]
[-- Type: application/x-compressed-tar, Size: 757031 bytes --]

[-- Attachment #3: Type: text/plain, Size: 394 bytes --]

------------------------------------------------------------------------------
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

[-- Attachment #4: Type: text/plain, Size: 179 bytes --]

_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

Re: [f2fs-dev] fsck: assertion failed

[folkert]

[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]

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

-- 
Multi tail barnamaj mowahib li mora9abat attasjilat wa nataij awamir
al 7asoub. damj, talwin, mora9abat attarchi7 wa ila akhirih.
http://www.vanheusden.com/multitail/
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com

[-- Attachment #2: fsck.f2fs-fvh.log.xz --]
[-- Type: application/octet-stream, Size: 6239076 bytes --]

[-- Attachment #3: Type: text/plain, Size: 394 bytes --]

------------------------------------------------------------------------------
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

[-- Attachment #4: Type: text/plain, Size: 179 bytes --]

_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

Re: [f2fs-dev] fsck: assertion failed

[Jaegeuk Kim]

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