[Rear-users] stopping rear ends with empty usb disk

Jeroen Hoekx jeroen.hoekx at hamok.be
Wed Jul 13 09:09:36 CEST 2011


It's pretty clear with this log, no?

On 12 July 2011 17:57, upen <upendra.gandhi at gmail.com> wrote:

> umount2: Device or resource busy
> umount.nfs: /tmp/rear.uwp7Fm5m4EeZHvr/netfs: device is busy
> umount2: Device or resource busy
> umount.nfs: /tmp/rear.uwp7Fm5m4EeZHvr/netfs: device is busy
> 2011-07-12 10:43:43 Finished in 43 seconds.
> 2011-07-12 10:43:43 Removing build area /tmp/rear.uwp7Fm5m4EeZHvr
> rm: cannot remove `/tmp/rear.uwp7Fm5m4EeZHvr/netfs/upendra_ots':
> Directory not empty
> 2011-07-12 10:43:50 End of program reached

umount fails twice; ReaR does an rm -rf on the build area...

Why does the umount fail? I don't know for sure, but yesterday while
we were testing on tape, tar kept running for some time after we
cancelled our ReaR run. I guess the problem is similar, but we should
really detect if anything is still mounted in
'cleanup_build_area_and_end_program'

Thanks for providing the logs!

Jeroen
(we also cleared our USB stick once while developing, doing an rm -rf
of the temp dir with the stick still mounted. We seriously considered
contributing an option to rm to stay on one filesystem!)




More information about the rear-users mailing list