ubihealthd status

[Richard Weinberger]

Maurice,

On Mon, Nov 2, 2020 at 8:29 PM Maurice Smulders
<maurice.smulders at genevatech.net> wrote:
>
> I am trying to determine how to be able to figure out if a PEB had an
> uncorrectable bitflip and expose it to user space.
> It would be good to determine if a specific volume is suspect
> determined from the actual LEB, and have some exposure in for example
> SYSFS. Would the actual volume be turned read-only?

It is a little more complicated.
There are many situations where a block is allowed to have uncorrectable
bit flips. e.g. the last data written by UBIFS after a power-cut. It
can recover from that.

On the other hand if all of a sudden committed data is no longer readable due to
ECC errors you are in deep trouble. UBI can fail to attach then, UBIFS
can refuse to
mount or fail much later, etc...

What situation are you trying to deal with?

> I'm open to suggestions, either I build something into ubihealthd to
> notify user programs to tell something bad has happened, or sysfs (but
> that cannot notify)
>
> The problem I have is that one of the apps i need to support this for
> is commercial - and I couldn't change ubihealthd to a libary because
> it is GPLv2, the other app is now Apache License based I think, it
> used to be under NOSA.  Also UBIHEALTHD doesn't necessarily have
> access to which LEB/Volume is potentially affected.

ubihealthd is a rather simple program. See source and use the kernel interface
directly in your application.

-- 
Thanks,
//richard