[bug]: SuSFS causing storage to report as 8 GB after a few days and crashing several apps

[xmicro]

Prerequisites

• I have searched existing issues and this is not a duplicate.
• I am running a Stock ROM (OOS or ColorOS).
• (Non-OnePlus devices only) I have read the compatibility list and confirmed my device is listed or uses a OnePlus kernel with a matching KMI.

Device Type

OnePlus device

Device Name & Model

OnePlus 15 - CPH2747

(Non-OnePlus only) OnePlus kernel used

No response

OOS / COS Version

OOS 16.0.5.700

Android Version

Android 16

Manager Type

KernelSU-Next

Manager Version

3.2.0 (33129)

Kernel Driver Version

33129

Kernel Installation Source

GitHub Release

Kernel Release Tag or Actions Run Link

2.1.0 r2

Bug Description

After a reboot, around 2 days, my storage as shown in files will start showing 503 MB used out of 8.00 GB, but will show correctly my 512 GB in termux using df and in settings. Unable to save files with an internet browser for example (out of storage error). But can still read/write files via Termux. Also, several apps start crashing (so far I've identified) X, Musicolet, Phantom (a crypto app) due to libpairipcore.so according to logcat. Additionally, the camera app also crashes. There's likely other apps crashing as well I just can't locate them all. But most apps are oddly fine.

I've spent weeks trying to debug this and I believe it's due to between SuSFS. Though I'm not sure if it's the susfs4ksu module itself or the way SuSFS is implemented in this kernel responding to the hide sus mount option... I only began getting the issue once SuSFS was installed though.

Auto try umount option in SuSFS being on or off with or without "skip legit mounts" has no effect. Only option enabled is the hide sus mount feature.

The weirdest part for me is definitely that it only occurs after a few days. If I reboot, everything will be fine. But it comes back every single time without fail. There's been other reports of this as well on the mountify GitHub.

Df command

:/data/data/com.termux/files/home # df -h
Filesystem        Size Used Avail Use% Mounted on
/dev/block/dm-36  737M 737M     0 100% /
tmpfs             7.3G 3.2M  7.3G   1% /dev
tmpfs             7.3G 692K  7.3G   1% /mnt
/dev/block/sdf3   224M  60M  164M  27% /mnt/vendor/oplusreserve
/dev/fuse         457G 241G  216G  53% /mnt/installer/0/emulated
tmpfs             7.3G    0  7.3G   0% /mnt/vm
/dev/block/sda2   108M 5.4M  103M   6% /mnt/vendor/persist
/dev/block/sde24  128M    0  128M   0% /mnt/vendor/qmcs
/dev/block/sde98   32M    0   32M   0% /mnt/vendor/spunvm
/dev/block/loop4  3.9M 3.9M   28K 100% /mnt/opex/com.oplus.CustCore@16000008
/dev/block/loop5   27M  27M   28K 100% /mnt/opex/com.oplus.NetworkAssistSys@16001051
/dev/block/loop44 328K 296K   32K  91% /mnt/opex/com.oplus.fancyIconLoader@1000000
/dev/block/loop45 912K 884K   28K  97% /mnt/opex/com.oplus.moduleservices@15000014
/dev/block/loop46 9.2M 9.1M   32K 100% /mnt/opex/com.oplus.odmf@16003006
/dev/block/dm-91  457G 241G  216G  53% /mnt/pass_through/0/emulated
/dev/block/sda10   62M  43M   19M  70% /metadata
/dev/block/dm-37  815M 815M     0 100% /system_ext
oplus_overlay     3.9M 3.9M   28K 100% /system_ext/framework/oplusex/com.oplus.CustCore
oplus_overlay      27M  27M   28K 100% /system_ext/framework/oplusex/com.oplus.NetworkAssistSys
oplus_overlay      27M  27M   28K 100% /system_ext/lib64/oplusex/com.oplus.NetworkAssistSys
oplus_overlay     328K 296K   32K  91% /system_ext/framework/oplusex/com.oplus.fancyIconLoader
oplus_overlay     912K 884K   28K  97% /system_ext/framework/oplusex/com.oplus.moduleservices
oplus_overlay     912K 884K   28K  97% /system_ext/lib64/oplusex/com.oplus.moduleservices
oplus_overlay     9.2M 9.1M   32K 100% /system_ext/framework/oplusex/com.oplus.odmf
oplus_overlay     9.2M 9.1M   32K 100% /system_ext/lib64/oplusex/com.oplus.odmf
/dev/block/dm-38  5.9M 5.9M     0 100% /product
KSU               127M  10M  117M   9% /product/overlay
overlay-overlay    46M  46M     0 100% /product/app
overlay-overlay    46M  46M     0 100% /product/priv-app
overlay-overlay    46M  46M     0 100% /product/lib64
overlay-overlay    46M  46M     0 100% /product/lib
overlay-overlay   3.4G 3.4G     0 100% /product/etc/permissions
overlay-overlay   3.4G 3.4G     0 100% /product/framework
/dev/block/dm-39  459M 459M     0 100% /vendor
/dev/block/sde6   349M 236M  113M  68% /vendor/firmware_mnt
/dev/block/sde9    68M  59M  8.9M  87% /vendor/dsp
/dev/block/sde7   7.9M 924K  7.0M  12% /vendor/bt_firmware
/dev/block/sde33  7.9M 2.6M  5.2M  34% /vendor/soccp_firmware
/dev/block/dm-40  134M 134M  412K 100% /vendor_dlkm
/dev/block/dm-41   13M  13M     0 100% /system_dlkm
/dev/block/dm-42  2.5G 2.5G     0 100% /odm
/dev/block/dm-43  3.4G 3.4G     0 100% /my_product
/dev/block/dm-91  127M  10M  117M   9% /my_product/etc/extension/com.oplus.oplus-feature.xml
KSU               127M  10M  117M   9% /my_product/etc
/dev/block/dm-44   16K  16K     0 100% /my_engineering
/dev/block/dm-45  4.0K 4.0K     0 100% /my_company
/dev/block/dm-46  4.0K 4.0K     0 100% /my_carrier
/dev/block/dm-47   46M  46M     0 100% /my_region
/dev/block/dm-48  4.0K 4.0K     0 100% /my_heytap
/dev/block/dm-49  2.1G 2.1G     0 100% /my_stock
/dev/block/dm-50  140M 140M     0 100% /my_preload
/dev/block/dm-51  4.0K 4.0K     0 100% /my_bigball
/dev/block/dm-52  356K 356K     0 100% /my_manifest
tmpfs             7.3G  24K  7.3G   1% /apex
/dev/block/loop31 232K 180K   52K  78% /apex/com.android.hardware.cas@1
/dev/block/loop18 844K 816K   28K  97% /apex/vendor.oplus.hardware.engineer.aidl@1
/dev/block/loop37  49M  49M     0 100% /apex/com.android.virt@3
/dev/block/loop23 3.9M 3.9M     0 100% /apex/com.android.runtime@1
/dev/block/loop33 7.4M 7.4M   28K 100% /apex/com.android.devicelock@343201000
/dev/block/loop14 388K 356K   32K  92% /apex/vendor.oplus.hardware.stability.aidl@1
/dev/block/loop6  232K 112K  120K  49% /apex/com.android.apex.cts.shim@1
/dev/block/loop7  132K 132K     0 100% /apex/com.android.crashrecovery@360499999
/dev/block/loop21  18M  18M     0 100% /apex/com.android.i18n@1
/dev/block/dm-74   16M  16M   32K 100% /apex/com.android.healthfitness@361420700
/dev/block/loop26 684K 684K     0 100% /apex/com.android.uprobestats@360499999
/dev/block/loop10 5.1M 5.1M   32K 100% /apex/com.google.android.widevine@190250226
/dev/block/loop15 836K 836K     0 100% /apex/com.android.profiling@360499999
/dev/block/loop27 1.9M 1.9M     0 100% /apex/com.android.compos@3
/dev/block/dm-66   21M  21M   28K 100% /apex/com.android.cellbroadcast@361524280
/dev/block/dm-76  7.1M 7.1M   32K 100% /apex/com.android.uwb@361524000
/dev/block/dm-79  1.3M 1.3M   32K  98% /apex/com.android.rkpd@361420880
/dev/block/dm-64  5.3M 5.3M   32K 100% /apex/com.android.configinfrastructure@361153320
/dev/block/dm-53   11M  10M   28K 100% /apex/com.android.wifi@361524080
/dev/block/dm-57  232K  24K  208K  11% /apex/com.android.resolv@361524040
/dev/block/dm-78   29M  29M   40K 100% /apex/com.android.art@361501120
/dev/block/dm-61   22M  22M   32K 100% /apex/com.android.adservices@361153320
/dev/block/dm-58   13M  13M   28K 100% /apex/com.android.ondevicepersonalization@361153320
/dev/block/dm-70  788K 756K   32K  96% /apex/com.android.tzdata@361157000
/dev/block/dm-56  232K 104K  128K  45% /apex/com.android.scheduling@361153320
/dev/block/dm-71  5.1M 5.0M   32K 100% /apex/com.android.conscrypt@361331440
/dev/block/dm-67   29M  29M   36K 100% /apex/com.android.media.swcodec@361521100
/dev/block/dm-69  7.4M 7.4M   28K 100% /apex/com.android.adbd@361154540
/dev/block/dm-80  3.1M 3.0M   32K  99% /apex/com.android.os.statsd@361420820
/dev/block/dm-83   27M  27M   28K 100% /apex/com.android.permission@361524160
/dev/block/dm-55  1.0M 1.0M   32K  98% /apex/com.android.sdkext@361418240
/dev/block/dm-54   28M  28M   28K 100% /apex/com.android.tethering@361524320
/dev/block/dm-81  5.9M 5.9M   32K 100% /apex/com.android.media@361521100
/dev/block/dm-65  4.5M 4.5M   28K 100% /apex/com.android.neuralnetworks@361153320
/dev/block/dm-87  4.1M 4.1M   32K 100% /apex/com.android.appsearch@361525160
/dev/block/dm-60  840K 812K   28K  97% /apex/com.android.ipsec@361153320
/dev/block/dm-77  6.2M 6.2M   32K 100% /apex/com.android.extservices@361153323
/dev/block/dm-59   26M  26M   32K 100% /apex/com.android.mediaprovider@361521100
tmpfs             7.3G 4.0K  7.3G   1% /bootstrap-apex
/dev/block/loop1   49M  49M     0 100% /bootstrap-apex/com.android.virt@3
/dev/block/loop0  788K 756K   32K  96% /bootstrap-apex/com.android.tzdata@361157000
/dev/block/loop2  3.9M 3.9M     0 100% /bootstrap-apex/com.android.runtime@1
/dev/block/loop3   18M  18M     0 100% /bootstrap-apex/com.android.i18n@1
tmpfs             7.3G 1.0M  7.3G   1% /linkerconfig
tmpfs             7.3G    0  7.3G   0% /tmp
tmpfs             7.3G    0  7.3G   0% /data_mirror
overlay           127M  10M  117M   9% /system/lib64
:/data/data/com.termux/files/home

Logcat crash

-b crash                                  < --------- beginning of crash                      05-14 17:43:06.953 14046 14046 F libc    : Fatal signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xb400007374000000 in tid 14046 (twitter.android), pid 14046 (twitter.android)                   05-14 17:43:07.259 14086 14086 F DEBUG   : Process name is com.twitter.android, uid is 10756, not key_process                                         05-14 17:43:07.259 14086 14086 F DEBUG   : keyProcess: 0                                            05-14 17:43:07.259 14086 14086 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***                                            05-14 17:43:07.259 14086 14086 F DEBUG   : Build fingerprint: 'OnePlus/CPH2747/OP611FL1:16/BP2A.250605.015/B.R4T3.2ba6ea1-907619-907cf4:user/release-keys'                                              05-14 17:43:07.259 14086 14086 F DEBUG   : Revision: '0'
05-14 17:43:07.259 14086 14086 F DEBUG   : ABI: 'arm64'
05-14 17:43:07.259 14086 14086 F DEBUG   : Timestamp: 2026-05-14 17:43:07.015643937-0400
05-14 17:43:07.259 14086 14086 F DEBUG   : Process uptime: 1s
05-14 17:43:07.259 14086 14086 F DEBUG   : Cmdline: com.twitter.android
05-14 17:43:07.259 14086 14086 F DEBUG   : pid: 14046, tid: 14046, name: twitter.android  >>> com.twitter.android <<<
05-14 17:43:07.259 14086 14086 F DEBUG   : uid: 10756
05-14 17:43:07.259 14086 14086 F DEBUG   : tagged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE)
05-14 17:43:07.259 14086 14086 F DEBUG   : pac_enabled_keys: 000000000000000f (PR_PAC_APIAKEY, PR_PAC_APIBKEY, PR_PAC_APDAKEY, PR_PAC_APDBKEY)
05-14 17:43:07.259 14086 14086 F DEBUG   : signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xb400007374000000
05-14 17:43:07.259 14086 14086 F DEBUG   :     x0  fffffffffffffff7  x1  0000000048590000  x2  0000000000000000  x3  b400007373e0d600
05-14 17:43:07.259 14086 14086 F DEBUG   :     x4  00000000ffffeffe  x5  00000000f6dde6ee  x6  00000000f6dde6ee  x7  0000000000000767
05-14 17:43:07.259 14086 14086 F DEBUG   :     x8  b400007373e0d600  x9  00000000ffe492a1  x10 c2325e6977d32cd4  x11 b400007373e4e42b
05-14 17:43:07.259 14086 14086 F DEBUG   :     x12 00000000001b1bd5  x13 00000000001b1bd6  x14 0000000000000000  x15 0000000000000d03
05-14 17:43:07.259 14086 14086 F DEBUG   :     x16 0000007ffdbea090  x17 00000000d15ca22c  x18 000000746c1e0000  x19 000000001b00e8ef
05-14 17:43:07.259 14086 14086 F DEBUG   :     x20 0000007ffdbea588  x21 00000000ffffeffe  x22 000000000000fa94  x23 f34ac0d992654faf
05-14 17:43:07.259 14086 14086 F DEBUG   :     x24 d34bfa551b00e8ef  x25 000000000003c394  x26 00000000000651c9  x27 000000009618406e
05-14 17:43:07.259 14086 14086 F DEBUG   :     x28 00000000f20cbced  x29 00000000000001ba
05-14 17:43:07.259 14086 14086 F DEBUG   :     lr  00000100000001b3  sp  0000007ffdbe9a20  pc  00000073017b380c  pst 00000000a0001000
05-14 17:43:07.259 14086 14086 F DEBUG   : 1 total frames
05-14 17:43:07.259 14086 14086 F DEBUG   : backtrace:
05-14 17:43:07.259 14086 14086 F DEBUG   :       #00 pc 000000000004580c  /data/app/~~i4RE_z-JwmYjdP_RuAq7Tg==/com.twitter.android-Jj8IqpHeLxFLE1hmR9pOPw==/split_config.arm64_v8a.apk!libpairipcore.so (offset 0x31e0000)
05-14 17:43:10.678 14251 14251 F libc    : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xb40000735be00000 in tid 14251 (colet:musicolet), pid 14251 (colet:musicolet)
05-14 17:43:10.730 14282 14282 F libc    : Fatal signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xb400007374000000 in tid 14282 (twitter.android), pid 14282 (twitter.android)
05-14 17:43:10.787 14316 14316 F DEBUG   : Process name is in.krosbits.musicolet:musicolet, uid is 10570, not key_process
05-14 17:43:10.787 14316 14316 F DEBUG   : keyProcess: 0
05-14 17:43:10.787 14316 14316 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-14 17:43:10.787 14316 14316 F DEBUG   : Build fingerprint: 'OnePlus/CPH2747/OP611FL1:16/BP2A.250605.015/B.R4T3.2ba6ea1-907619-907cf4:user/release-keys'
05-14 17:43:10.787 14316 14316 F DEBUG   : Revision: '0'
05-14 17:43:10.787 14316 14316 F DEBUG   : ABI: 'arm64'
05-14 17:43:10.787 14316 14316 F DEBUG   : Timestamp: 2026-05-14 17:43:10.716209977-0400
05-14 17:43:10.787 14316 14316 F DEBUG   : Process uptime: 2s
05-14 17:43:10.787 14316 14316 F DEBUG   : Cmdline: in.krosbits.musicolet:musicolet
05-14 17:43:10.787 14316 14316 F DEBUG   : pid: 14251, tid: 14251, name: colet:musicolet  >>> in.krosbits.musicolet:musicolet <<<
05-14 17:43:10.787 14316 14316 F DEBUG   : uid: 10570
05-14 17:43:10.787 14316 14316 F DEBUG   : tagged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE)
05-14 17:43:10.787 14316 14316 F DEBUG   : pac_enabled_keys: 000000000000000f (PR_PAC_APIAKEY, PR_PAC_APIBKEY, PR_PAC_APDAKEY, PR_PAC_APDBKEY)
05-14 17:43:10.787 14316 14316 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xb40000735be00000
05-14 17:43:10.787 14316 14316 F DEBUG   :     x0  00000000f934c9a6  x1  000000004a98934e  x2  131b44f7c72c9b97  x3  000000007592e512
05-14 17:43:10.787 14316 14316 F DEBUG   :     x4  000000001140120d  x5  00000000338cd6e8  x6  00000000fffe4db6  x7  d1cbb0830d2d80a8
05-14 17:43:10.787 14316 14316 F DEBUG   :     x8  000000000004fc86  x9  00000000f9fddfff  x10 d8ee5424811f948b  x11 00000000fd3e271b
05-14 17:43:10.787 14316 14316 F DEBUG   :     x12 0000000000004f46  x13 000000004450588c  x14 b40000735bd9fec0  x15 000000000004fc86
05-14 17:43:10.787 14316 14316 F DEBUG   :     x16 00000000294904cd  x17 00000000a08c9197  x18 000000746c1e0000  x19 b40000735bdec9e0
05-14 17:43:10.787 14316 14316 F DEBUG   :     x20 0000000000013620  x21 0000000000013621  x22 000000000000003f  x23 0000000000000000
05-14 17:43:10.787 14316 14316 F DEBUG   :     x24 00000100000001b3  x25 b40000735bd9fec0  x26 00000000221ca735  x27 00000000000006d7
05-14 17:43:10.787 14316 14316 F DEBUG   :     x28 0000000000000942  x29 000000000000037a
05-14 17:43:10.787 14316 14316 F DEBUG   :     lr  0000000000002567  sp  0000007ffdbea4b0  pc  00000073772ddcd0  pst 00000000a0001000
05-14 17:43:10.787 14316 14316 F DEBUG   : 1 total frames
05-14 17:43:10.787 14316 14316 F DEBUG   : backtrace:
05-14 17:43:10.787 14316 14316 F DEBUG   :       #00 pc 000000000005bcd0  /data/app/~~bL4o_GbCIpui5_TO3YNS6Q==/in.krosbits.musicolet-AW_cPlAtX58t389PNVp7-A==/split_config.arm64_v8a.apk!libpairipcore.so (offset 0x14b8000)
05-14 17:43:10.874 14324 14324 F DEBUG   : Process name is com.twitter.android, uid is 10756, not key_process
05-14 17:43:10.874 14324 14324 F DEBUG   : keyProcess: 0
05-14 17:43:10.874 14324 14324 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-14 17:43:10.874 14324 14324 F DEBUG   : Build fingerprint: 'OnePlus/CPH2747/OP611FL1:16/BP2A.250605.015/B.R4T3.2ba6ea1-907619-907cf4:user/release-keys'
05-14 17:43:10.874 14324 14324 F DEBUG   : Revision: '0'
05-14 17:43:10.874 14324 14324 F DEBUG   : ABI: 'arm64'
05-14 17:43:10.874 14324 14324 F DEBUG   : Timestamp: 2026-05-14 17:43:10.802993310-0400
05-14 17:43:10.874 14324 14324 F DEBUG   : Process uptime: 2s
05-14 17:43:10.874 14324 14324 F DEBUG   : Cmdline: com.twitter.android
05-14 17:43:10.874 14324 14324 F DEBUG   : pid: 14282, tid: 14282, name: twitter.android  >>> com.twitter.android <<<
05-14 17:43:10.874 14324 14324 F DEBUG   : uid: 10756
05-14 17:43:10.874 14324 14324 F DEBUG   : tagged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE)
05-14 17:43:10.874 14324 14324 F DEBUG   : pac_enabled_keys: 000000000000000f (PR_PAC_APIAKEY, PR_PAC_APIBKEY, PR_PAC_APDAKEY, PR_PAC_APDBKEY)
05-14 17:43:10.874 14324 14324 F DEBUG   : signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xb400007374000000
05-14 17:43:10.874 14324 14324 F DEBUG   :     x0  fffffffffffffff7  x1  0000000048590000  x2  0000000000000000  x3  b400007373e0d600
05-14 17:43:10.874 14324 14324 F DEBUG   :     x4  00000000ffffeffe  x5  00000000f6dde6ee  x6  00000000f6dde6ee  x7  0000000000000767
05-14 17:43:10.874 14324 14324 F DEBUG   :     x8  b400007373e0d600  x9  00000000ffe492a1  x10 f5809a298c2d7a7e  x11 b400007373e4e42b
05-14 17:43:10.874 14324 14324 F DEBUG   :     x12 00000000001b1bd5  x13 00000000001b1bd6  x14 0000000000000000  x15 0000000000000d03
05-14 17:43:10.874 14324 14324 F DEBUG   :     x16 0000007ffdbea090  x17 00000000d15ca22c  x18 000000746c1e0000  x19 000000001b00e8ef
05-14 17:43:10.874 14324 14324 F DEBUG   :     x20 0000007ffdbea588  x21 00000000ffffeffe  x22 000000000000fa94  x23 f34ac0d992654faf
05-14 17:43:10.874 14324 14324 F DEBUG   :     x24 d34bfa551b00e8ef  x25 000000000003c394  x26 00000000000651c9  x27 000000009618406e
05-14 17:43:10.874 14324 14324 F DEBUG   :     x28 00000000f20cbced  x29 00000000000001ba
05-14 17:43:10.874 14324 14324 F DEBUG   :     lr  00000100000001b3  sp  0000007ffdbe9a20  pc  00000073774c780c  pst 00000000a0001000
05-14 17:43:10.874 14324 14324 F DEBUG   : 1 total frames
05-14 17:43:10.874 14324 14324 F DEBUG   : backtrace:
05-14 17:43:10.874 14324 14324 F DEBUG   :       #00 pc 000000000004580c  /data/app/~~i4RE_z-JwmYjdP_RuAq7Tg==/com.twitter.android-Jj8IqpHeLxFLE1hmR9pOPw==/split_config.arm64_v8a.apk!libpairipcore.so (offset 0x31e0000)
05-14 17:43:14.611 14571 14571 F libc    : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x650008b720c4fc49 in tid 14571 (app.phantom), pid 14571 (app.phantom)
05-14 17:43:14.717 14607 14607 F DEBUG   : Process name is app.phantom, uid is 10384, not key_process
05-14 17:43:14.718 14607 14607 F DEBUG   : keyProcess: 0
05-14 17:43:14.718 14607 14607 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-14 17:43:14.718 14607 14607 F DEBUG   : Build fingerprint: 'OnePlus/CPH2747/OP611FL1:16/BP2A.250605.015/B.R4T3.2ba6ea1-907619-907cf4:user/release-keys'
05-14 17:43:14.718 14607 14607 F DEBUG   : Revision: '0'
05-14 17:43:14.718 14607 14607 F DEBUG   : ABI: 'arm64'
05-14 17:43:14.718 14607 14607 F DEBUG   : Timestamp: 2026-05-14 17:43:14.648496694-0400
05-14 17:43:14.718 14607 14607 F DEBUG   : Process uptime: 1s
05-14 17:43:14.718 14607 14607 F DEBUG   : Cmdline: app.phantom
05-14 17:43:14.718 14607 14607 F DEBUG   : pid: 14571, tid: 14571, name: app.phantom  >>> app.phantom <<<
05-14 17:43:14.718 14607 14607 F DEBUG   : uid: 10384
05-14 17:43:14.718 14607 14607 F DEBUG   : tagged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE)
05-14 17:43:14.718 14607 14607 F DEBUG   : pac_enabled_keys: 000000000000000f (PR_PAC_APIAKEY, PR_PAC_APIBKEY, PR_PAC_APDAKEY, PR_PAC_APDBKEY)
05-14 17:43:14.718 14607 14607 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x650008b720c4fc49
05-14 17:43:14.718 14607 14607 F DEBUG   :     x0  b40000737540d040  x1  00000000000004eb  x2  0000000000002424  x3  000000000006f64d
05-14 17:43:14.718 14607 14607 F DEBUG   :     x4  00000000000004eb  x5  000000005fe9fafb  x6  00000000dec6faef  x7  000000000001b1f8
05-14 17:43:14.718 14607 14607 F DEBUG   :     x8  0000007ffdbea5a8  x9  000000000006f64d  x10 000000008c7fdc15  x11 0000000000000000
05-14 17:43:14.718 14607 14607 F DEBUG   :     x12 650008b720c4fc48  x13 b40000737540d040  x14 650008b720c4fc49  x15 180b2c7da3641378
05-14 17:43:14.718 14607 14607 F DEBUG   :     x16 00000000ffffffff  x17 0000000094465886  x18 000000746c1e0000  x19 000000003bdd4dfd
05-14 17:43:14.718 14607 14607 F DEBUG   :     x20 00000000d12bfeaf  x21 0000000000000899  x22 0000007ffdbea4d0  x23 000000000000008c
05-14 17:43:14.718 14607 14607 F DEBUG   :     x24 0000000000001e0b  x25 000000002ba845bb  x26 0000000000000645  x27 000000003bdd4dfd
05-14 17:43:14.718 14607 14607 F DEBUG   :     x28 0000000000000899  x29 00000000000004eb
05-14 17:43:14.718 14607 14607 F DEBUG   :     lr  00000000000001a4  sp  0000007ffdbea370  pc  000000737730d7fc  pst 0000000080001000
05-14 17:43:14.718 14607 14607 F DEBUG   : 1 total frames
05-14 17:43:14.718 14607 14607 F DEBUG   : backtrace:
05-14 17:43:14.718 14607 14607 F DEBUG   :       #00 pc 000000000005f7fc  /data/app/~~vQ2ZkkniOk4L4EQftVbV1A==/app.phantom-va5hxTUlsJ2KRkhZxyXljw==/split_config.arm64_v8a.apk!libpairipcore.so (offset 0x17a8000)
^C
130|:/data/data/com.termux/files/home

Other modules
Susfs4ksu
Mountify
Play Integrity Fix
Tricky Store
Bindhosts
NeoZygisk
vector
Oxygen Customizer

I also attach my kernel log. https://drive.google.com/file/d/1iIevm9_gB8odiNQmg3SJ18Q330LWYw4_/view?usp=drivesdk

Gemini reading my dmesg.log seems to think it's because:

The log is flooded with hundreds of kernel crash traces that look exactly like this:
cleanup_mnt+0x11c/0x158
do_exit+0x25c/0xa48
ida_free called for id=556380 which is not allocated.

This is the exact smoking gun.

How this causes the 8 GB Glitch and Crashes

When you have "hide sus mounts for all non-su processes" enabled, SuSFS hooks into the mount namespace of every single app and background process Android creates.
When those processes close in the background, Linux runs a function called cleanup_mnt to delete the namespace and free the ID number assigned to those mounts.
Because of a bug in susfs4ksu's interaction with your kernel, it is corrupting the ID Allocator (IDA). The kernel tries to free the mount ID but fails, throwing that ida_free warning.

Look at the ID number in your log: id=556380. That means Zygote has spawned and leaked over half a million mount IDs over the last few days!

Eventually, the ID allocator completely runs out of numbers. When that happens:
You open X, Phantom, or your Files app.
Android tries to assign a new mount ID to bind your physical 512 GB /storage/emulated/0 to the app.
The allocation fails because the ID pool is exhausted.
The app gets dumped into the fallback root filesystem, which is your 8 GB tmpfs RAM disk.
Your Files app reads the 8 GB RAM disk, and X/Camera crash because they cannot find their data folders.

Steps to Reproduce

1. Wait a few days after rebooting with SuSFS enabled with susfs4ksu installed with default settings.
2. Storage glitches and app crashes

Expected vs Actual Behavior

Storage doesn't glitch out. Sus mounts are hidden correctly. Apps don't crash.

Regression?

Unknown / first install

(Regression only) Last working kernel version

No response

Boot.img stock

Untested

Manager Log (name_log.tar.gz)

https://drive.google.com/file/d/1iIevm9_gB8odiNQmg3SJ18Q330LWYw4_/view?usp=drivesdk

Won't upload for some reason.

SYSTEM_LAST_KMSG (OnePlus devices only)

No such directory exists for me OnePlus 15.

Additional Context

No response

[techIndia-hacker]

Wow, and I was thinking that motherboard was short-circuited in my case, cause a reboot fixed it everytime. Oneplus 13

[fatalcoder524]

Disable HIDE SUS MOUNTS FOR ALL/NON-SU PROCESSES and see if you have enabled it.

And yes. It's a known bug i think!

[techIndia-hacker]

Disable HIDE SUS MOUNTS FOR ALL/NON-SU PROCESSES and see if you have enabled it.

Check, is this correct?

[xmicro]

Disable HIDE SUS MOUNTS FOR ALL/NON-SU PROCESSES and see if you have enabled it.

Check, is this correct?

You have it enabled. He's saying to turn it off.

[xmicro]

Disable HIDE SUS MOUNTS FOR ALL/NON-SU PROCESSES and see if you have enabled it.

And yes. It's a known bug i think!

Oh I didn't realize it was known. I hadn't seen it addressed anywhere else. I do see a few reports of this glitch, but it's under mountify and Hybrid Mount GitHub issues (one of which was made by me), originally because we thought it was an interaction between SuSFS and unmounting with meta modules. (Since it occurs with both mountify and Hybrid Mount. I confirmed myself and with others.) I hadn't seen anything like that reported here though, so I wasn't sure if it was due to that or just a susfs/kernel issue instead, which is what I'm beginning to suspect instead.

But yes hide sus mounts was enabled for me, like it is by default. Do you know how to fix it/plan to release a fix soon? Thanks!

I will try it with it off and report back. It will take a few days to verify though due to the nature of the bug for me.

[fatalcoder524]

Yes. Please verify. And yes. There is no fix as of now unless we know exactly why it happens.

[xmicro]

Yes. Please verify. And yes. There is no fix as of now unless we know exactly why it happens.

After 4 days now and no issue, I can confidently confirm that it is indeed hiding sus mounts that causes it.

[xmicro]

I see an update to the repo. I am installing the new kernel (5/20 release) and will re-enable hide sus mounts to see if I still get the issue.