[f2fs-dev] [Bug 210795] fsck.f2fs - 1.14.0 - error when not /dev/vgXX/lvYYY path provided - [ASSERT] (init_sb_info:1017) !strcmp((char *)sb->devs[i].path, (char *)c.devices[i].path)

[bugzilla-daemon@bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=210795

Chao Yu (chao@kernel.org) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |chao@kernel.org

--- Comment #1 from Chao Yu (chao@kernel.org) ---
> Info: Device[0] : /dev/vgftp1a/VIRTUALa blkaddr = 0--13fffff
> Info: [/dev/vgftp1b/VIRTUALb] Disk Model: SanDisk SDSSDXPS
> Info: Device[1] : /dev/vgftp1b/VIRTUALb blkaddr = 1400000--27fffff

You can see that in f2fs superblock, we record original paths of multipath
instead of paths symlinks point to, when you use fsck.f2fs /dev/xxx to check
multiple devices of f2fs image, fsck can only compare paths stored in
superblock with parameters we passed, otherwise it will trigger ASSERT warning.

So we can only use

fsck.f2fs  --dry-run /dev/vgftp1a/VIRTUALa

to check f2fs image, rather than using

fsck.f2fs  --dry-run /dev/dm-15

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

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