On Aug 12 02:59:38, frantisek holop wrote:
hi there,
it seems that i have found the sequence to reliably
reproduce this problem.
# mount /adata
# cd /adata
# vnconfig svnd0 install46.iso
# mount /dev/svnd0c /mnt
# umount /mnt
# umount /adata
umount: /adata: Device busy
/adata is
hmm, on Wed, Aug 12, 2009 at 09:53:57AM +0200, Jan Stary said that
On Aug 12 02:59:38, frantisek holop wrote:
hi there,
it seems that i have found the sequence to reliably
reproduce this problem.
# mount /adata
# cd /adata
# vnconfig svnd0 install46.iso
# mount /dev/svnd0c
On Wed, Aug 12, 2009 at 1:17 AM, patrick keshishianpkesh...@gmail.com
wrote:
fstat reports on open files, not files in use. as you've discovered,
there are ways for a file to be in use without being open by a
process.
This seems educational; could you please elaborate?
The kernel keeps a
hi there,
it seems that i have found the sequence to reliably
reproduce this problem.
# mount /adata
# cd /adata
# vnconfig svnd0 install46.iso
# mount /dev/svnd0c /mnt
# umount /mnt
# umount /adata
umount: /adata: Device busy
# vnconfig -u svnd0
# umount /adata
why wasn't fstat showing this
On Tue, Aug 11, 2009 at 8:59 PM, frantisek holopmin...@obiit.org wrote:
# vnconfig svnd0 install46.iso
why wasn't fstat showing this information?
even doing fstat -f /adata/install46.iso returned
nothing.
fstat reports on open files, not files in use. as you've discovered,
there are ways
On Tue, Aug 11, 2009 at 8:48 PM, Ted Unangstted.unan...@gmail.com wrote:
On Tue, Aug 11, 2009 at 8:59 PM, frantisek holopmin...@obiit.org wrote:
# vnconfig svnd0 install46.iso
why wasn't fstat showing this information?
even doing fstat -f /adata/install46.iso returned
nothing.
fstat
On Wed, Jul 29, 2009 at 04:12:56PM +0200, frantisek holop wrote:
hmm, on Wed, Jul 29, 2009 at 09:56:29AM -0400, Dan Harnett said that
On Wed, Jul 29, 2009 at 06:06:16AM +0200, frantisek holop wrote:
amaaq$ sudo fstat /adata
USER CMD PID FD MOUNTINUM MODE
hmm, on Thu, Jul 30, 2009 at 12:20:51PM +0200, Jurjen Oskam said that
On Wed, Jul 29, 2009 at 04:12:56PM +0200, frantisek holop wrote:
hmm, on Wed, Jul 29, 2009 at 09:56:29AM -0400, Dan Harnett said that
On Wed, Jul 29, 2009 at 06:06:16AM +0200, frantisek holop wrote:
amaaq$ sudo
hmm, on Wed, Jul 29, 2009 at 12:58:42AM -0400, Brynet said that
I've never had this problem before.. but according to the man page,
you can forcefully remove the mount using.. your signature.. '-f'.
If this fails, unplug the USB cable or power down the drive..
detaching it from the system.
On Wed, Jul 29, 2009 at 06:06:16AM +0200, frantisek holop wrote:
amaaq$ sudo fstat /adata
USER CMD PID FD MOUNTINUM MODE R/WSZ|DV NAME
You should use the '-f' option to fstat.
$ sudo fstat -f /adata
One possibility is shared libraries or objects.
hmm, on Wed, Jul 29, 2009 at 09:56:29AM -0400, Dan Harnett said that
On Wed, Jul 29, 2009 at 06:06:16AM +0200, frantisek holop wrote:
amaaq$ sudo fstat /adata
USER CMD PID FD MOUNTINUM MODE R/WSZ|DV
NAME
You should use the '-f' option to fstat.
$
hi there,
amaaq$ uname -a
OpenBSD amaaq 4.6 GENERIC#29 i386
amaaq$ sudo fstat /adata
USER CMD PID FD MOUNTINUM MODE R/WSZ|DV NAME
amaaq$ sudo umount /adata/
umount: /adata: Device busy
what are my other choices hunting down the process that makes
the mount
On Tue, Jul 28, 2009 at 9:06 PM, frantisek holopmin...@obiit.org wrote:
hi there,
amaaq$ uname -a
OpenBSD amaaq 4.6 GENERIC#29 i386
amaaq$ sudo fstat /adata
USER CMD PID FD MOUNTINUM MODE R/WSZ|DV
NAME
amaaq$ sudo umount /adata/
umount: /adata: Device
Type pwd, make sure you're not in it. Do the same for any terminals
you have accessing that machine.
On 7/29/09, frantisek holop min...@obiit.org wrote:
hi there,
amaaq$ uname -a
OpenBSD amaaq 4.6 GENERIC#29 i386
amaaq$ sudo fstat /adata
USER CMD PID FD MOUNTINUM
hmm, on Wed, Jul 29, 2009 at 02:18:56PM +1000, Aaron Mason said that
Type pwd, make sure you're not in it. Do the same for any terminals
you have accessing that machine.
no, i am not there. i closed all the shells too.
but that would show up in fstat anyway:
amaaq$ cd /adata/
amaaq$ fstat
Hi,
I've never had this problem before.. but according to the man page,
you can forcefully remove the mount using.. your signature.. '-f'.
If this fails, unplug the USB cable or power down the drive..
detaching it from the system.
HTH.
-Brynet
16 matches
Mail list logo