On Mon, Nov 27, 2023 at 10:30 AM Lennart Poettering <lennart@xxxxxxxxxxxxxx> wrote:
On So, 26.11.23 00:39, Richard Weinberger (richard.weinberger@xxxxxxxxx) wrote:
> Hello!
>
> After upgrading my main test worker to a recent distribution, the UBI
> test suite [0] fails at various places with -EBUSY.
> The reason is that these tests create and remove UBI volumes rapidly.
> A typical test sequence is as follows:
> 1. creation of /dev/ubi0_0
> 2. some exclusive operation, such as atomic update or volume resize on
> /dev/ubi0_0
> 3. removal of /dev/ubi0_0
>
> Both steps 2 and 3 can fail with -EBUSY because the udev worker still
> holds a file descriptor to /dev/ubi0_0.
Hmm, I have no experience with UBI, but are you sure we open that? why
would we? are such devices analyzed by blkid? We generally don't open
device nodes unless we have a reason to, such as doing blkid on it or
so.
blkid and 60-persistent-storage indeed analyze ubi devices, it seems.
--
Mantas Mikulėnas
