Er zijn 4 reacties in dit onderwerp

[Pr2]

Hi,

 

I try to perform a filesystem check of the internal HDD (by the way it is viewed as an external HDD by the VU+ Duo2).

 

But this failed due to this:

# umount -f /media/hdd/
umount: can't forcibly umount /media/hdd: Device or resource busy

 

Looking at what is preventing the umount, I found this:

 

root@vuduo2:/media# fuser /media/hdd/
20157

 

Searching the process associated to it with I found:

 

20157 root      8016 S    smbd -D

 

I think that it can be interesting to improve the filesystem check option by including this "fuser search and kill" process when the hdd cannot be unmounted.

 

Or at least think to kill smbd before trying to umount the hdd for filesystem check.

 

Pr2

 

[MiLo]

Sounds like a reasonable suggestion - and a nice improvement. After all, you cannot expect a shared disk to remain available while it's being initialized or fsck is running.

[Robinson]

 

# umount -f /media/hdd/
umount: can't forcibly umount /media/hdd: Device or resource busy

Looking at what is preventing the umount, I found this:

root@vuduo2:/media# fuser /media/hdd/
20157

 

Hi,

Could you please help me understand how you managed to determine it was process 20157?

[Erik Slagter]

fuser probably.

 

If you have the process id, look it up using ps. Or use fuser -mv but I don't think the busybox implements honours that option.

[betacentauri]

You should use

fuser -m /media/hdd

 

You can find the process with:

ps -w | grep 20157

 

By the way. In several cases you need to stop e2 (init 2) before you can umount the hdd.