19.09.2020 17:32, Aaron Digulla пишет:

Am 18.09.20 um 21:07 schrieb Andrei Borzenkov:

...

18.09.2020 21:35, Aaron Digulla пишет:

...

...

...

lsof -n | grep dropbox

as root returns nothing.

Google found some sources saying that udev locks the device node.

Shouldn't lsof report that?

It depends on how it is used. ... I tried to remove it:

$ lvremove /dev/system/dropbox --autobackup y --verbose --test   TEST MODE: Metadata will NOT be updated and volumes will not be (de)activated.   Logical volume system/dropbox contains a filesystem in use. $ mount|grep dropbox $

Who is using the file system?

What

fuser -c /dev/system/dropbox

says?

Thanks for the suggestion. That lists all kinds of processes including PID 1 (systemd):

/dev/dm-5:               1rce     2rc     3rc     4rc     6rc     9rc ... plus a ton more

This means that either device /dev/system/dropbox is root filesystem or that /dev/system/dropbox is a file on root filesystem.

...

In the worst case it could be lazy unmounted or it could be mounted in another namespace. I am not sure if it is possible to list all mounts in all namespaces.

actually "lsns -t mnt" does it. From there it may be possible to see what is mounted in each namespace. But it is probably premature.

...

Did you try to reboot?

Not yet. I was wondering why Linux thinks that the drive is used when the command line tools can't tell me the process. I'm trying to learn something right now, not just quickly fix it.

Regards,

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org