Dennis Jacobfeuerborn wrote: > On 03.01.2014 15:37, Leon Fauster wrote: > >> Am 03.01.2014 um 15:04 schrieb Ken Smith<kens at kensnet.org>: >> >>> Leon Fauster wrote: >>> >>>> Am 03.01.2014 um 08:57 schrieb Mauricio Tavares<raubvogel at gmail.com>: >>>> >>>> >>>>> On Thu, Jan 2, 2014 at 10:19 PM, Leon Fauster >>>>> <leonfauster at googlemail.com> wrote: >>>>> >>>>> {snip} >>>> thats why i suggest to try it in backup. Thats not a solution, it is more >>>> a heuristic way to get close to the problem (after evaluating the results). >>>> >>>> >>>> >>>> >>> I tried it in /media. Same result. Its as if umount is doing a rm -rf >>> >> >> please try /backup, /test or /random or something that is not /mnt or /media. >> The latter dirs are common to be under control by some "processes". >> > Also try to use /bin/umount instead of just umount. That way you prevent > a potential alias for "umount" from running instead of the actual command. > > Regards, > Dennis > > > OK result. I created /TEST and mounted and umounted successfully with both /bin/umount and plain umount Interesting, as suspected something is messing with things in /mnt and /media Ken -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.