From: V10lator <v10lator@myway.de>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: Unrecoverable FS errors
Date: Wed, 01 Feb 2017 18:59:05 +0100 [thread overview]
Message-ID: <0078de3b-fa1e-4f32-9424-68b0735ae87a@myway.de> (raw)
In-Reply-To: <20170130232252.GA1492@jaegeuk.local>
Am Dienstag, 31. Januar 2017 00:22:52 CET schrieb Jaegeuk Kim:
> On 01/29, V10lator wrote:
>> Hi,
>>
>> I compiled and tried the version you linked, sadly it's still the same.
>
> Oh, was there no reported error?
Yes there was, sorry for not showing earlier:
Info: Force to fix corruption
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 247967744 (121078 MB)
Info: MKFS version
""
Info: FSCK version
from "Linux version 4.8.17-hardened-r1 (root@kali) (gcc version 5.3.0
(Gentoo Hardened 5.3.0 p1.1, pie-0.6.5) ) #3 SMP PREEMPT Wed Feb 1 13:02:02
CET 2017"
to "Linux version 4.8.17-hardened-r1 (root@kali) (gcc version 5.3.0
(Gentoo Hardened 5.3.0 p1.1, pie-0.6.5) ) #3 SMP PREEMPT Wed Feb 1 13:02:02
CET 2017"
Info: superblock features = 0 :
Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000
Info: total FS sectors = 247967744 (121078 MB)
Info: CKPT version = 189ba6
Info: checkpoint state = 1 : unmount
[ASSERT] (f2fs_check_dirent_position:1152) --> Wrong position of dirent
pino:175381, name:NetLock_Arany_=Class_Gold=_Főtanúsítvány.pem, level:1,
dir_level:0, pgofs:4, correct range:[2, 3]
[ASSERT] (f2fs_check_dirent_position:1152) --> Wrong position of dirent
pino:552333, name:fr-Besançon, level:1, dir_level:0, pgofs:4, correct
range:[2, 3]
[ASSERT] (f2fs_check_dirent_position:1152) --> Wrong position of dirent
pino:552333, name:fr-Alençon, level:1, dir_level:0, pgofs:5, correct
range:[2, 3]
[ASSERT] (f2fs_check_dirent_position:1152) --> Wrong position of dirent
pino:599566,
name:TÜBİTAK_UEKAE_Kök_Sertifika_Hizmet_Sağlayıcısı_-_Sürüm_3.crt, level:1,
dir_level:0, pgofs:2, correct range:[4, 5]
[FSCK] Unreachable nat entries [Ok..] [0x0]
[FSCK] SIT valid block bitmap checking [Ok..]
[FSCK] Hard link checking for regular file [Ok..] [0x97]
[FSCK] valid_block_count matching with CP [Ok..] [0x16d1141]
[FSCK] valid_node_count matcing with CP (de lookup) [Ok..] [0xf869d]
[FSCK] valid_node_count matcing with CP (nat lookup) [Ok..] [0xf869d]
[FSCK] valid_inode_count matched with CP [Ok..] [0xc05d9]
[FSCK] free segment_count matched with CP [Ok..] [0x34d0]
[FSCK] next block offset is free [Ok..]
[FSCK] fixing SIT types
[FSCK] other corrupted bugs [Fail]
Done.
> Then, which kernel version are you using?
4.8.17
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2017-02-01 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 12:11 Unrecoverable FS errors V10lator
2017-01-29 4:14 ` Jaegeuk Kim
2017-01-29 18:14 ` V10lator
2017-01-30 23:22 ` Jaegeuk Kim
2017-02-01 17:59 ` V10lator [this message]
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=0078de3b-fa1e-4f32-9424-68b0735ae87a@myway.de \
--to=v10lator@myway.de \
--cc=jaegeuk@kernel.org \
--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).