sanitizers detect an issue in sdcard service, making FUSE fs unavailable

[Bmme2GFTbU]

The Update from today killed my /storage/emulated folder. Its only available as a link, so far I could see.

[Bmme2GFTbU]

Update for Nexus 5, sorry missed

[Bmme2GFTbU]

Update for Nexus 5, sorry missed

[thestinger]

It's an sdcard service bug detected by one of the sanitizers. The upstream bug needs to be found and fixed. Can't easily do that in a normal user build since there are no debugging symbols and trapping UBSan doesn't provide any guidance without that.

[thestinger]

It's an sdcard service bug detected by one of the sanitizers. The upstream bug needs to be found and fixed. Can't easily do that in a normal user build since there are no debugging symbols and trapping UBSan doesn't provide any guidance without that.

[denharad]

This also happened to me. Is the data gone or just unmounted and is there any quick fix?

[denharad]

This also happened to me. Is the data gone or just unmounted and is there any quick fix?

[vanitasvitae]

Are all the files still there? I can't see them from my computer. I'm a little bit worried about my data.

[vanitasvitae]

Are all the files still there? I can't see them from my computer. I'm a little bit worried about my data.

[vanitasvitae]

@denharad: I just checked my file structure via TWRP. In my case the files are still there when android isnt booted pfew

[vanitasvitae]

@denharad: I just checked my file structure via TWRP. In my case the files are still there when android isnt booted pfew

[thestinger]

No data is lost. As I said, it's a bug caught in the sdcard service by one of the sanitizers. It doesn't always occur, which is why it wasn't caught in testing. CopperheadOS didn't introduce the bug, it just detected it. I could make new builds with the sanitizers disabled again, but that will waste a day that could be spent fixing the issue which is what I plan on doing.

[thestinger]

No data is lost. As I said, it's a bug caught in the sdcard service by one of the sanitizers. It doesn't always occur, which is why it wasn't caught in testing. CopperheadOS didn't introduce the bug, it just detected it. I could make new builds with the sanitizers disabled again, but that will waste a day that could be spent fixing the issue which is what I plan on doing.

[vanitasvitae]

@thestinger That's okay for me. I think I can spend some days without my files. I'll try to push the important files to my desktop for now.

[vanitasvitae]

@thestinger That's okay for me. I think I can spend some days without my files. I'll try to push the important files to my desktop for now.

[thestinger]

Don't have the resources to do thorough testing so issues like this will happen, and it's going to take a while to resolve due to the long build times.

[thestinger]

Don't have the resources to do thorough testing so issues like this will happen, and it's going to take a while to resolve due to the long build times.

[thestinger]

Alright, I think it's fixed. I was just a benign overflow. Testing it again, and then I'll push out new builds.

[thestinger]

Alright, I think it's fixed. I was just a benign overflow. Testing it again, and then I'll push out new builds.

[thestinger]

Just need clean builds to publish now. Going to take a while.

[thestinger]

Just need clean builds to publish now. Going to take a while.

[thestinger]

New builds are published for the Nexus 5 and 5X. Nexus 9 coming later.

[thestinger]

New builds are published for the Nexus 5 and 5X. Nexus 9 coming later.

[vanitasvitae]

I can confirm that this is fixed on hammerhead 👍

[vanitasvitae]

I can confirm that this is fixed on hammerhead 👍