Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 04 Jun 2012 01:56:49 -0600
From:      Gary Aitken <freebsd@dreamchaser.org>
To:        Polytropon <freebsd@edvax.de>
Cc:        FreeBSD Mailing List <freebsd-questions@freebsd.org>
Subject:   Re: umount     device busy
Message-ID:  <4FCC6A41.6030408@dreamchaser.org>
In-Reply-To: <20120604050537.f2df2af2.freebsd@edvax.de>
References:  <4FCB7BBF.7090603@dreamchaser.org> <7581F5930C4F42B28B1E4A5162491B35@astrolap> <4FCC1D4C.2020503@dreamchaser.org> <20120604050537.f2df2af2.freebsd@edvax.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On 06/03/12 21:05, Polytropon wrote:

> Good idea. However, you can do efficient backups of "Windows"
> data by using the "ntfsprogs" tools. This makes sure they can
> even be read under non-"Windows" systems.

I'll look into that. 

>>> if you are using xfce4, then you have most likely got gamin
>>> running as well, this caused the same problem for me when
>>> trying to umount an external USB drive
>>
>> gamin *is* installed, and I did have the file browser up and
>> using it to look at the ntfs disk.  I thought it might be
>> holding a file open, so first I backed it out to something
>> not on the ntfs disk, then exited it.  Made no difference.
> 
> Maybe the ganim "lock" is regarding a device file? Not sure
> about that, I'm not using it here.

I'm not sure what the deal is here, but exiting X does solve the problem.  I didn't try just killing the environment by shutting down the wm and leaving X up, but if I forget and do something like that again I'll try to remember to try it.

>> In any case, the mount was done after X was started, and switching
>> vtys crashes X so I don't do that.
> 
> That sounds a bit wrong...

Agreed, but I saw someone else was having a similar problem with 9.0 release a bit earlier on a system, and no problem with 8.3.  At least I think that was it.  Hmmm, just looked and there's a firefox-bin.core and an xfce-appfinder.core.  Timestamps look about right for when I did a vty switch.

> Typo maybe? A command like "ps2ascii" sounds more reasonable if
> we consider PS being the output format. The command

duh.  need sleep.

thanks.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FCC6A41.6030408>