* [f2fs-dev] F2FS Segmentation Fault
@ 2020-07-13 22:24 Nathan Royce
2020-07-14 0:03 ` Jaegeuk Kim
0 siblings, 1 reply; 6+ messages in thread
From: Nathan Royce @ 2020-07-13 22:24 UTC (permalink / raw)
To: Jaegeuk Kim; +Cc: linux-kernel, linux-f2fs-devel
I won't re-format unless I hear something within a few days in case
you want me to try something.
Preface: There was a notable power outage a couple of nights ago.
When the power returned, everything seemed fine. No issues during
bootup or anything.
Then today, I went to open an application and my system started
schitzing out with programs suddenly closing(/crashing?).
I switched tty and tried to log in but was unable to even be allowed
to enter in my password.
I switched to another and tried logging in as root which succeeded (somehow).
I looked at the journal and saw an entry saying something about
/bin/login not being a valid exec format.
I went to reboot and when it got to fsck part of initramfs, it failed
and I was kicked to root.
I ran fsck and saw a bunch of issues, but I guess nothing could get
resolved enough to let me reboot.
Oh, in case you're wondering, my / (system) is on a 64GB SDHC card.
I just happened to also have an older / system on my mechanical drive
using BTRFS which I could boot to (which I'm on now).
I ran fsck from this older system and it seems I got the same results:
*****
Info: Fix the reported corruption.
Info: Force to fix corruption
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 124168159 (60628 MB)
Info: MKFS version
"Linux version 5.1.15.a-1-hardened (builduser@slave-1) (gcc version
9.1.0 (GCC)) #1 SMP PREEMPT Thu Jun 27 11:33:04 CEST 2019"
Info: FSCK version
from "Linux version 4.19.13-dirty (userName@computerName) (gcc
version 8.2.1 20181127 (GCC)) #2 SMP PREEMPT Mon Dec 31 00:15:50 CST
2018"
to "Linux version 4.19.13-dirty (userName@computerName) (gcc
version 8.2.1 20181127 (GCC)) #2 SMP PREEMPT Mon Dec 31 00:15:50 CST
2018"
Info: superblock features = 0 :
Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000
Info: total FS sectors = 124168152 (60628 MB)
Info: CKPT version = 63f2b4a
Info: checkpoint state = 55 : crc fsck compacted_summary unmount
NID[0x18eca] is unreachable, blkaddr:0xcf1d9d3c
NID[0x18ecb] is unreachable, blkaddr:0x5db5f91f
NID[0x18ecc] is unreachable, blkaddr:0x4653d
NID[0x18ee3] is unreachable, blkaddr:0x144dc401
NID[0x18ee4] is unreachable, blkaddr:0x558cfba9
NID[0x18ee5] is unreachable, blkaddr:0x45553
NID[0x18f78] is unreachable, blkaddr:0x560555ac
NID[0x18f79] is unreachable, blkaddr:0x58cccb0d
NID[0x18f7a] is unreachable, blkaddr:0x53d84
NID[0x4d621] is unreachable, blkaddr:0x4fc1d
NID[0x4d622] is unreachable, blkaddr:0x4fc1e
NID[0x7fa32] is unreachable, blkaddr:0x20b0ca3a
NID[0x7fa33] is unreachable, blkaddr:0xf71b60
[FSCK] Unreachable nat entries [Fail] [0xd]
[FSCK] SIT valid block bitmap checking [Fail]
[FSCK] Hard link checking for regular file [Ok..] [0x4f6]
[FSCK] valid_block_count matching with CP [Fail] [0x736fcb]
[FSCK] valid_node_count matcing with CP (de lookup) [Fail] [0x70327]
[FSCK] valid_node_count matcing with CP (nat lookup) [Ok..] [0x70334]
[FSCK] valid_inode_count matched with CP [Fail] [0x6f09e]
[FSCK] free segment_count matched with CP [Ok..] [0x3bfc]
[FSCK] next block offset is free [Ok..]
[FSCK] fixing SIT types
[FSCK] other corrupted bugs [Fail]
Do you want to restore lost files into ./lost_found/? [Y/N] Y
Segmentation fault
*****
*****
Message: Process 3425 (fsck.f2fs) of user 0 dumped core.
Stack trace of thread 3425:
#0 0x000055f8515739c8 n/a (fsck.f2fs)
#1 0x000055f851575261 n/a (fsck.f2fs)
#2 0x000055f851572c56 n/a (fsck.f2fs)
#3 0x000055f85156a3f0 n/a (fsck.f2fs)
#4 0x00007f51420feee3 __libc_start_main (libc.so.6)
#5 0x000055f85156a95e n/a (fsck.f2fs)
*****
So if you want more information or need me to try something, let me
know soon if you would. Otherwise, I'll just be reformatting my card
in a few days.
It just could've been a fluke occurred because of the power outage but
didn't manifest itself until today.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [f2fs-dev] F2FS Segmentation Fault
2020-07-13 22:24 [f2fs-dev] F2FS Segmentation Fault Nathan Royce
@ 2020-07-14 0:03 ` Jaegeuk Kim
2020-07-14 2:24 ` Nathan Royce
0 siblings, 1 reply; 6+ messages in thread
From: Jaegeuk Kim @ 2020-07-14 0:03 UTC (permalink / raw)
To: Nathan Royce; +Cc: linux-kernel, linux-f2fs-devel
Hi Nathan,
On 07/13, Nathan Royce wrote:
> I won't re-format unless I hear something within a few days in case
> you want me to try something.
>
> Preface: There was a notable power outage a couple of nights ago.
> When the power returned, everything seemed fine. No issues during
> bootup or anything.
> Then today, I went to open an application and my system started
> schitzing out with programs suddenly closing(/crashing?).
> I switched tty and tried to log in but was unable to even be allowed
> to enter in my password.
> I switched to another and tried logging in as root which succeeded (somehow).
> I looked at the journal and saw an entry saying something about
> /bin/login not being a valid exec format.
> I went to reboot and when it got to fsck part of initramfs, it failed
> and I was kicked to root.
> I ran fsck and saw a bunch of issues, but I guess nothing could get
> resolved enough to let me reboot.
> Oh, in case you're wondering, my / (system) is on a 64GB SDHC card.
> I just happened to also have an older / system on my mechanical drive
> using BTRFS which I could boot to (which I'm on now).
> I ran fsck from this older system and it seems I got the same results:
>
> *****
> Info: Fix the reported corruption.
> Info: Force to fix corruption
> Info: Segments per section = 1
> Info: Sections per zone = 1
> Info: sector size = 512
> Info: total sectors = 124168159 (60628 MB)
> Info: MKFS version
> "Linux version 5.1.15.a-1-hardened (builduser@slave-1) (gcc version
> 9.1.0 (GCC)) #1 SMP PREEMPT Thu Jun 27 11:33:04 CEST 2019"
> Info: FSCK version
> from "Linux version 4.19.13-dirty (userName@computerName) (gcc
> version 8.2.1 20181127 (GCC)) #2 SMP PREEMPT Mon Dec 31 00:15:50 CST
> 2018"
> to "Linux version 4.19.13-dirty (userName@computerName) (gcc
> version 8.2.1 20181127 (GCC)) #2 SMP PREEMPT Mon Dec 31 00:15:50 CST
> 2018"
> Info: superblock features = 0 :
> Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000
> Info: total FS sectors = 124168152 (60628 MB)
> Info: CKPT version = 63f2b4a
> Info: checkpoint state = 55 : crc fsck compacted_summary unmount
>
> NID[0x18eca] is unreachable, blkaddr:0xcf1d9d3c
> NID[0x18ecb] is unreachable, blkaddr:0x5db5f91f
> NID[0x18ecc] is unreachable, blkaddr:0x4653d
> NID[0x18ee3] is unreachable, blkaddr:0x144dc401
> NID[0x18ee4] is unreachable, blkaddr:0x558cfba9
> NID[0x18ee5] is unreachable, blkaddr:0x45553
> NID[0x18f78] is unreachable, blkaddr:0x560555ac
> NID[0x18f79] is unreachable, blkaddr:0x58cccb0d
> NID[0x18f7a] is unreachable, blkaddr:0x53d84
> NID[0x4d621] is unreachable, blkaddr:0x4fc1d
> NID[0x4d622] is unreachable, blkaddr:0x4fc1e
> NID[0x7fa32] is unreachable, blkaddr:0x20b0ca3a
> NID[0x7fa33] is unreachable, blkaddr:0xf71b60
> [FSCK] Unreachable nat entries [Fail] [0xd]
> [FSCK] SIT valid block bitmap checking [Fail]
> [FSCK] Hard link checking for regular file [Ok..] [0x4f6]
> [FSCK] valid_block_count matching with CP [Fail] [0x736fcb]
> [FSCK] valid_node_count matcing with CP (de lookup) [Fail] [0x70327]
> [FSCK] valid_node_count matcing with CP (nat lookup) [Ok..] [0x70334]
> [FSCK] valid_inode_count matched with CP [Fail] [0x6f09e]
> [FSCK] free segment_count matched with CP [Ok..] [0x3bfc]
> [FSCK] next block offset is free [Ok..]
> [FSCK] fixing SIT types
> [FSCK] other corrupted bugs [Fail]
>
> Do you want to restore lost files into ./lost_found/? [Y/N] Y
Could you try to say "N" here to move forward to fix the corrupted metadata?
Thanks,
> Segmentation fault
> *****
>
> *****
> Message: Process 3425 (fsck.f2fs) of user 0 dumped core.
>
> Stack trace of thread 3425:
> #0 0x000055f8515739c8 n/a (fsck.f2fs)
> #1 0x000055f851575261 n/a (fsck.f2fs)
> #2 0x000055f851572c56 n/a (fsck.f2fs)
> #3 0x000055f85156a3f0 n/a (fsck.f2fs)
> #4 0x00007f51420feee3 __libc_start_main (libc.so.6)
> #5 0x000055f85156a95e n/a (fsck.f2fs)
> *****
>
> So if you want more information or need me to try something, let me
> know soon if you would. Otherwise, I'll just be reformatting my card
> in a few days.
> It just could've been a fluke occurred because of the power outage but
> didn't manifest itself until today.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [f2fs-dev] F2FS Segmentation Fault
2020-07-14 0:03 ` Jaegeuk Kim
@ 2020-07-14 2:24 ` Nathan Royce
2020-07-14 5:54 ` Jaegeuk Kim
0 siblings, 1 reply; 6+ messages in thread
From: Nathan Royce @ 2020-07-14 2:24 UTC (permalink / raw)
To: Jaegeuk Kim; +Cc: linux-kernel, linux-f2fs-devel
On Mon, Jul 13, 2020 at 7:03 PM Jaegeuk Kim <jaegeuk@kernel.org> wrote:
>
> Hi Nathan,
>
> Could you try to say "N" here to move forward to fix the corrupted metadata?
>
> Thanks,
*****
Do you want to restore lost files into ./lost_found/? [Y/N] N
Info: Write valid nat_bits in checkpoint
[FIX] (nullify_nat_entry:2273) --> Remove nid [0x18eca] in NAT
[FIX] (nullify_nat_entry:2273) --> Remove nid [0x18ecb] in NAT
[FIX] (nullify_nat_entry:2273) --> Remove nid [0x18ecc] in NAT
[FIX] (nullify_nat_entry:2273) --> Remove nid [0x18ee3] in NAT
[FIX] (nullify_nat_entry:2273) --> Remove nid [0x18ee4] in NAT
[FIX] (nullify_nat_entry:2273) --> Remove nid [0x18ee5] in NAT
[FIX] (nullify_nat_entry:2273) --> Remove nid [0x18f78] in NAT
[FIX] (nullify_nat_entry:2273) --> Remove nid [0x18f79] in NAT
[FIX] (nullify_nat_entry:2273) --> Remove nid [0x18f7a] in NAT
[FIX] (nullify_nat_entry:2273) --> Remove nid [0x4d621] in NAT
[FIX] (nullify_nat_entry:2273) --> Remove nid [0x4d622] in NAT
[FIX] (nullify_nat_entry:2273) --> Remove nid [0x7fa32] in NAT
[FIX] (nullify_nat_entry:2273) --> Remove nid [0x7fa33] in NAT
Info: Write valid nat_bits in checkpoint
Done.
*****
*****
Info: Fix the reported corruption.
Info: Force to fix corruption
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 124168159 (60628 MB)
Info: MKFS version
"Linux version 5.1.15.a-1-hardened (builduser@slave-1) (gcc version
9.1.0 (GCC)) #1 SMP PREEMPT Thu Jun 27 11:33:04 CEST 2019"
Info: FSCK version
from "Linux version 4.19.13-dirty (nater@devx64) (gcc version 8.2.1
20181127 (GCC)) #2 SMP PREEMPT Mon Dec 31 00:15:50 CST 2018"
to "Linux version 4.19.13-dirty (nater@devx64) (gcc version 8.2.1
20181127 (GCC)) #2 SMP PREEMPT Mon Dec 31 00:15:50 CST 2018"
Info: superblock features = 0 :
Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000
Info: total FS sectors = 124168152 (60628 MB)
Info: CKPT version = 63f2b4a
Info: checkpoint state = 281 : allow_nocrc nat_bits unmount
Info: No error was reported
*****
I'm now booted in from my SDHC card. So it "seems" I'm good to go.
But with the actions taken and the files I've seen displayed during
the fsck, I'm thinking I'm going to reinstall all packages.
Assuming the issue was related to the power outage, I do wonder why
there weren't any fsck issues at bootup at that time. I hadn't had any
disk issues before with that card.
At least now I know the issue would be resolved by not saving the lost
files and I can continue on my merry way.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [f2fs-dev] F2FS Segmentation Fault
2020-07-14 2:24 ` Nathan Royce
@ 2020-07-14 5:54 ` Jaegeuk Kim
2021-03-27 12:02 ` Nathan Royce
0 siblings, 1 reply; 6+ messages in thread
From: Jaegeuk Kim @ 2020-07-14 5:54 UTC (permalink / raw)
To: Nathan Royce; +Cc: linux-kernel, linux-f2fs-devel
On 07/13, Nathan Royce wrote:
> On Mon, Jul 13, 2020 at 7:03 PM Jaegeuk Kim <jaegeuk@kernel.org> wrote:
> >
> > Hi Nathan,
> >
> > Could you try to say "N" here to move forward to fix the corrupted metadata?
> >
> > Thanks,
> *****
> Do you want to restore lost files into ./lost_found/? [Y/N] N
> Info: Write valid nat_bits in checkpoint
> [FIX] (nullify_nat_entry:2273) --> Remove nid [0x18eca] in NAT
> [FIX] (nullify_nat_entry:2273) --> Remove nid [0x18ecb] in NAT
> [FIX] (nullify_nat_entry:2273) --> Remove nid [0x18ecc] in NAT
> [FIX] (nullify_nat_entry:2273) --> Remove nid [0x18ee3] in NAT
> [FIX] (nullify_nat_entry:2273) --> Remove nid [0x18ee4] in NAT
> [FIX] (nullify_nat_entry:2273) --> Remove nid [0x18ee5] in NAT
> [FIX] (nullify_nat_entry:2273) --> Remove nid [0x18f78] in NAT
> [FIX] (nullify_nat_entry:2273) --> Remove nid [0x18f79] in NAT
> [FIX] (nullify_nat_entry:2273) --> Remove nid [0x18f7a] in NAT
> [FIX] (nullify_nat_entry:2273) --> Remove nid [0x4d621] in NAT
> [FIX] (nullify_nat_entry:2273) --> Remove nid [0x4d622] in NAT
> [FIX] (nullify_nat_entry:2273) --> Remove nid [0x7fa32] in NAT
> [FIX] (nullify_nat_entry:2273) --> Remove nid [0x7fa33] in NAT
> Info: Write valid nat_bits in checkpoint
>
> Done.
> *****
>
> *****
> Info: Fix the reported corruption.
> Info: Force to fix corruption
> Info: Segments per section = 1
> Info: Sections per zone = 1
> Info: sector size = 512
> Info: total sectors = 124168159 (60628 MB)
> Info: MKFS version
> "Linux version 5.1.15.a-1-hardened (builduser@slave-1) (gcc version
> 9.1.0 (GCC)) #1 SMP PREEMPT Thu Jun 27 11:33:04 CEST 2019"
> Info: FSCK version
> from "Linux version 4.19.13-dirty (nater@devx64) (gcc version 8.2.1
> 20181127 (GCC)) #2 SMP PREEMPT Mon Dec 31 00:15:50 CST 2018"
> to "Linux version 4.19.13-dirty (nater@devx64) (gcc version 8.2.1
> 20181127 (GCC)) #2 SMP PREEMPT Mon Dec 31 00:15:50 CST 2018"
> Info: superblock features = 0 :
> Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000
> Info: total FS sectors = 124168152 (60628 MB)
> Info: CKPT version = 63f2b4a
> Info: checkpoint state = 281 : allow_nocrc nat_bits unmount
> Info: No error was reported
> *****
> I'm now booted in from my SDHC card. So it "seems" I'm good to go.
> But with the actions taken and the files I've seen displayed during
> the fsck, I'm thinking I'm going to reinstall all packages.
> Assuming the issue was related to the power outage, I do wonder why
> there weren't any fsck issues at bootup at that time. I hadn't had any
> disk issues before with that card.
> At least now I know the issue would be resolved by not saving the lost
> files and I can continue on my merry way.
I suspect the last power outage caused the FTL in the card firmware to point
the f2fs NAT table area to somewhere wrong flash cells. It may be possible
that we can't see any filesystem corruption easily, since it can corrupt
data area in higher possibility; this doesn't lead filesystem inconsistency.
I guess you use "-a" for fsck at boot up, which means scanning the disk when
runtime f2fs detects any inconsistent data. But that is true, only when the disk
guarantees SYNC_CACHE at least. Unfortunately, IMHO, such the flash card doesn't
support it gracefully, and thus, we can't rely on SYNC_CACHE which should be the
baseline to guarantee filesystem consistency. I think it'd be good to run "-f",
if sudden power cut happens in this case.
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [f2fs-dev] F2FS Segmentation Fault
2020-07-14 5:54 ` Jaegeuk Kim
@ 2021-03-27 12:02 ` Nathan Royce
2021-03-27 12:41 ` Nathan Royce
0 siblings, 1 reply; 6+ messages in thread
From: Nathan Royce @ 2021-03-27 12:02 UTC (permalink / raw)
To: Jaegeuk Kim; +Cc: LKML, linux-f2fs-devel
An update, not quite 1 year later. I encountered another segfault issue.
It began with my email report to the linux-btrfs mailing list titled
"BTRFS Balance Hard System Crash (Blinking LEDs)" just the other day.
Essentially, I had run "btrfs balance" on my btrfs filesystem
drive/partition (not sd-card).
It looks like it had completed or was just about to complete when I
came back to my computer to find my keyboard numlock and scrolllock
leds were blinking.
The short of it was that I thought something about the "balance"
process caused the problem.
Then I encountered boot issues, and then when I was in, I later
encountered issues which dealt with my f2fs (sd-card), where programs
weren't being run because of libutils (glibc).
So I was forced to do another reboot and everything seemed fine until
I went to sleep and woke up again to blinking leds.
No btrfs process/action was being taken.
I spun up my KDE Neon sd-card, which I'm in right now and running a
btrfs scrub on my btrfs drive as I write this.
I also ran an fsck.f2fs on my sd-card (not kde-neon), and it got bad
right away...
*****
$ sudo fsck.f2fs -a /dev/mapper/lukssdi2
Info: Fix the reported corruption.
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 124168159 (60628 MB)
Info: MKFS version
"Linux version 5.1.15.a-1-hardened (builduser@slave-1) (gcc version
9.1.0 (GCC)) #1 SMP PREEMPT Thu Jun 27 11:33:04 CEST 2019"
Info: FSCK version
from "Linux version 5.7.4-dirty (nater@devx64) (gcc version 10.1.0
(GCC), GNU ld (GNU Binutils) 2.34.0) #2 SMP PREEMPT Sat Jun 20
14:10:44 CDT 2020"
to "Linux version 5.4.0-66-generic (buildd@lgw01-amd64-039) (gcc
version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #74-Ubuntu SMP Wed Jan
27 22:54:38 UTC 2021"
Info: superblock features = 0 :
Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000
Info: total FS sectors = 124168152 (60628 MB)
Info: CKPT version = 64ad7cd
Info: checkpoint state = 45 : crc compacted_summary unmount
[ASSERT] (sanity_check_nid: 410) --> nid[0x9e359]
footer.nid[0xf9c78d27] footer.ino[0xeb53d27e]
[FIX] (__chk_dentries:1458) --> Unlink [0x9e359] - cmp.js len[0x6], type[0x1]
[ASSERT] (fsck_chk_inode_blk: 849) --> ino: 0x9e337 has i_blocks:
4b6da06f35755b22, but has 1 blocks
[FIX] (fsck_chk_inode_blk: 855) --> [0x9e337]
i_blocks=0x4b6da06f35755b22 -> 0x1
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xab5e5e15]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e30d] i_addr[438] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xf77f2dbc]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e30d] i_addr[439] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x54f59437]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e30d] i_addr[440] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xb7e1860a]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e30d] i_addr[441] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x2f705bf0]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e30d] i_addr[566] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x8d4d35fd]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e30d] i_addr[567] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x39b52875]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e30d] i_addr[568] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x2199a4cb]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e30d] i_addr[569] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xe96a44d6]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e30d] i_addr[574] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x71027b6c]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e30d] i_addr[575] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x8b9ad104]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e30d] i_addr[576] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x7490f998]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e30d] i_addr[577] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xfa89d7d7]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e30d] i_addr[610] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xd4628485]]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e30d] i_addr[611] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x6824154e]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e30d] i_addr[612] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x6b50a940]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e30d] i_addr[613] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xc27ef23]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e30d] i_addr[782] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x6a5bbf49]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e30d] i_addr[783] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x7854aab6]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e30d] i_addr[784] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x64f4372e]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e30d] i_addr[785] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xb14ed504]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e3a6] i_addr[302] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x86a7fda5]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e3a6] i_addr[303] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x989215c5]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e3a6] i_addr[304] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x745044d2]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e3a6] i_addr[305] = 0
[ASSERT] (__check_inode_mode: 371) --> inode [0x9c798] mismatch
i_mode [0x1 vs. 0x15a3]
[FIX] (__chk_dentries:1458) --> Unlink [0x9c798] - axios.js len[0x8], type[0x1]
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x68e77e8]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e3d7] i_addr[22] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x33facbb]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e3d7] i_addr[23] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xd7859924]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e3d7] i_addr[24] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x7b9854f8]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e3d7] i_addr[25] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x6226d630]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[266] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xb1f9f056]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[267] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xa69e1ca7]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[268] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x2d4c1a87]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[269] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x2cc93801]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[318] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x2caca0cd]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[319] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xb04e26d7]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[320] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x610ce9cf]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[321] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x2db812e1]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[558] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x24241497]]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[559] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x598c6421]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[560] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x795adae8]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[561] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xb838a973]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[606] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xde310dda]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[607] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xdc31adb2]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[608] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x475034e9]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[609] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x3f9d40a7]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[766] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x5a14583c]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[767] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x5d008b8b]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[768] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xa88d34f9]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[769] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x94e78459]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[838] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x6ff9a8fc]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[839] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xc177be50]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[840] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x4972dad4]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5e8] i_addr[841] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xca14c78c]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5fd] i_addr[338] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x5955dbb3]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5fd] i_addr[339] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x2ebcaeff]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5fd] i_addr[340] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x9c34d9c9]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5fd] i_addr[341] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x6e939c46]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5fd] i_addr[434] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xe85c355e]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5fd] i_addr[435] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xa2f7d908]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5fd] i_addr[436] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x2f2dd1e2]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5fd] i_addr[437] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x92c67341]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5fd] i_addr[574] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xe301b1c4]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5fd] i_addr[575] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xbe42214a]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5fd] i_addr[576] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xf1302262]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5fd] i_addr[577] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x9f0379c]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5fd] i_addr[734] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x9894bdcc]]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5fd] i_addr[735] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xd22fb2d1]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5fd] i_addr[736] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xacf8ccf0]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5fd] i_addr[737] = 0
[ASSERT] (__chk_dots_dentries:1275) --> Bad inode number[0x9e35c] for
'..', parent parent ino is [0xbc194d49]
[ASSERT] (fsck_chk_inode_blk: 866) --> ino: 0x9e38d has i_namelen:
0xa4211fc, but has 4 characters for name
[FIX] (fsck_chk_inode_blk: 870) --> [0x9e38d] i_namelen=0xa4211fc -> 0x4
[ASSERT] (__chk_dots_dentries:1275) --> Bad inode number[0x9e35c] for
'..', parent parent ino is [0x18025d66]
[ASSERT] (fsck_chk_inode_blk: 866) --> ino: 0x9e403 has i_namelen:
0x6b1a3cdf, but has 7 characters for name
[FIX] (fsck_chk_inode_blk: 870) --> [0x9e403] i_namelen=0x6b1a3cdf -> 0x7
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xca8ac6d6]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e53c] i_addr[26] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x70481c27]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e53c] i_addr[27] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x96343e0f]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e53c] i_addr[28] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x2c5f73c1]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e53c] i_addr[29] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x4843a092]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e53c] i_addr[286] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x22c91166]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e53c] i_addr[287] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xdb5063f7]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e53c] i_addr[288] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xce43128]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e53c] i_addr[289] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x95b73f10]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e53c] i_addr[818] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xc96716c2]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e53c] i_addr[819] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x4f3e23a3]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e53c] i_addr[820] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xc8ac8076]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e53c] i_addr[821] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x3ff28034]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5dc] i_addr[498] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xb86e79dc]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5dc] i_addr[499] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x71361046]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5dc] i_addr[500] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xd47bcde3]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5dc] i_addr[501] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xbfd42c6d]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e640] i_addr[166] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x1ce93cd5]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e640] i_addr[167] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xeefa3f4a]]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e640] i_addr[168] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x200f3d49]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e640] i_addr[169] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x82570d2e]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e640] i_addr[214] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x72d93f37]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e640] i_addr[215] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x13bdb757]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e640] i_addr[216] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x960cf5aa]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e640] i_addr[217] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xfab0eaed]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[94] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xfd229386]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[95] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x8c4e2c01]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[96] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x1451a3e9]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[97] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xb7fec026]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[174] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x5627f3a5]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[175] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xf680d8a1]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[176] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xb141bcbc]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[177] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xbc525001]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[274] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xb478c927]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[275] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xf8b92645]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[276] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x9ef2f47d]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[277] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xc326ba37]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[430] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x9d3f608d]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[431] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x5fdd2bac]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[432] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x5aa44e41]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[433] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xad6bc741]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[626] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xaead228]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[627] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xa0cf522e]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[628] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xae5023d7]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[629] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x96624f4a]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[634] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x182d3b99]]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[635] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xcd7ccf8]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[636] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xf95991d8]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e64f] i_addr[637] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x41237f1a]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e654] i_addr[46] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xd87ee4f3]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e654] i_addr[47] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x3567468c]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e654] i_addr[48] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xcc26a1d7]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e654] i_addr[49] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x20f4ac9e]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e654] i_addr[386] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x3b8d3236]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e654] i_addr[387] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x2fe93339]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e654] i_addr[388] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x28789efc]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e654] i_addr[389] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xcc821607]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e654] i_addr[522] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x30893a61]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e654] i_addr[523] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xbe2722a]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e654] i_addr[524] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x159e9e48]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e654] i_addr[525] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x78e4920f]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e654] i_addr[686] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x73389ea2]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e654] i_addr[687] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x3323b2c3]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e654] i_addr[688] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xd442f672]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e654] i_addr[689] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x2ca0f966]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e4da] i_addr[602] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xccbd063d]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e4da] i_addr[603] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x4e9ed377]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e4da] i_addr[604] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xfcfcf807]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e4da] i_addr[605] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x21aaccdb]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e522] i_addr[94] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x835bca2d]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e522] i_addr[95] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xa642be37]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e522] i_addr[96] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x500ebc2]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e522] i_addr[97] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xdb56d869]]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e54e] i_addr[686] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xc699ef86]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e54e] i_addr[687] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x8658571c]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e54e] i_addr[688] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x412c63d4]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e54e] i_addr[689] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xd863961f]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e54e] i_addr[818] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x5da14266]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e54e] i_addr[819] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xa3eb54c0]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e54e] i_addr[820] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xbe83ea55]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e54e] i_addr[821] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x38f048cf]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5d9] i_addr[42] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x1bb20aba]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5d9] i_addr[43] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x164914cd]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5d9] i_addr[44] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x18432b76]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5d9] i_addr[45] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xcfefd9c5]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e484] i_addr[366] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xd672fbb7]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e484] i_addr[367] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xa113bab3]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e484] i_addr[368] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x1af84de0]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e484] i_addr[369] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x147f77a5]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5b0] i_addr[30] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0xb8fb4384]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5b0] i_addr[31] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x7dc7364]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5b0] i_addr[32] = 0
[ASSERT] (fsck_chk_data_blk:1555) --> blkaddress is not valid. [0x20350042]
[FIX] (fsck_chk_inode_blk: 788) --> [0x9e5b0] i_addr[33] = 0
Segmentation fault
$ sudo fsck.f2fs -af /dev/mapper/lukssdi2
Info: Fix the reported corruption.
Info: Force to fix corruption
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 124168159 (60628 MB)
Can't find a valid F2FS superblock at 0x0
Mismatch segment0(3096048428) cp_blkaddr(24874649)
Can't find a valid F2FS superblock at 0x1
*****
journal:
*****
Mar 27 06:22:07 neon kernel: Code: 41 f6 c1 04 75 53 4d 85 c9 74 0b 0f
b6 0f 88 0a 41 f6 c1 02 75 53 42 c6 04 0a 00 c3 0f 1f 44 00 00 48 8b
0f 4c 89 c6 48 89 0a <4a> 8b 4c 0f f8 48 8d 7a 08 48 83 e7 f8 4a 89 4c
0a f8 48 89 d1 48
Mar 27 06:22:07 neon kernel: fsck.f2fs[6302]: segfault at 5564d32978f5
ip 000055651c124919 sp 00007ffd202ff9f8 error 4 in
fsck.f2fs[55651c121000+1c000]
*****
This kde-neon kernel version is 5.4.0, and the associated tools
version is f2fs-tools-1.11.0.
There hasn't been any power-outage that I'm aware of.
With that segfault, I'm thinking that fs is now toast, and I need to
rebuild that arch-linux partition. At least /home was on btrfs which
is still accessible.
While I'm at it (scrubbing btrfs), I think I'll memtest my RAM and
badblocks my sd-card.
On Tue, Jul 14, 2020 at 12:54 AM Jaegeuk Kim <jaegeuk@kernel.org> wrote:
>
> On 07/13, Nathan Royce wrote:
> > On Mon, Jul 13, 2020 at 7:03 PM Jaegeuk Kim <jaegeuk@kernel.org> wrote:
> > >
> > > Hi Nathan,
> > >
> > > Could you try to say "N" here to move forward to fix the corrupted metadata?
> > >
> > > Thanks,
> > *****
> > Do you want to restore lost files into ./lost_found/? [Y/N] N
...
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [f2fs-dev] F2FS Segmentation Fault
2021-03-27 12:02 ` Nathan Royce
@ 2021-03-27 12:41 ` Nathan Royce
0 siblings, 0 replies; 6+ messages in thread
From: Nathan Royce @ 2021-03-27 12:41 UTC (permalink / raw)
To: Jaegeuk Kim; +Cc: LKML, linux-f2fs-devel
I don't know how much of it was the issue, but when I unmounted the
sd-card, and closed the cryptsetup for it, and then ran
non-destructive badblocks on it, I was getting ONLY errors.
I stopped bb, then pulled out the card, blew on it, wiped down the
contacts with rubbing alcohol, let it dry, put it back in and now bb
is running cleanly.
I then stopped bb, tried to cryptsetup-open it and it said the
partition is not a valid LUKS device.
Weird since I was using non-destructive.
Looks like I'm now forced to rebuild that partition.
I wish I had troubleshot the aspect of the sd-card being properly
seated. I know I've experienced something similar to it in the past
where files suddenly aren't able to be read. Once I reseat the
sd-card, everything was fine.
The last time I had to even remove the card was maybe 1-2 weeks ago
when I had to deal with a noisy power-supply fan.
The whole debacle (including btrfs, keyboard leds blinking) may very
well have been from the sd-card not being seated well.
On Sat, Mar 27, 2021 at 7:02 AM Nathan Royce <nroycea+kernel@gmail.com> wrote:
>
> An update, not quite 1 year later. I encountered another segfault issue.
>
> It began with my email report to the linux-btrfs mailing list titled
> "BTRFS Balance Hard System Crash (Blinking LEDs)" just the other day.
...
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2021-03-27 12:41 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-07-13 22:24 [f2fs-dev] F2FS Segmentation Fault Nathan Royce
2020-07-14 0:03 ` Jaegeuk Kim
2020-07-14 2:24 ` Nathan Royce
2020-07-14 5:54 ` Jaegeuk Kim
2021-03-27 12:02 ` Nathan Royce
2021-03-27 12:41 ` Nathan Royce
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).