On Sat, Apr 08, 2006 at 02:23:48PM +0700, Surachai Locharoen wrote:
> Andrew Sackville-West wrote:
> >On Fri, Apr 07, 2006 at 05:53:06PM -0700, charles norwood wrote:
> >
> >>On Fri, 2006-04-07 at 16:22 -0500, Hugo Vanwoerkom wrote:
> >>
> >>>Hi,
> >>>
> >>>I do:
> >>>
> >>>umount /hda14
> >>
Luis R Finotti wrote:
Hugo Vanwoerkom wrote:
Hi,
I do:
umount /hda14
and get:
umount: /hda14: device is busy
umount: /hda14: device is busy
Is there a way of finding out *why* it is busy? Obviously it is linked
to someplace, but where?
Thanks!
H
You can try "lsof" to find what is kee
Andrew Sackville-West wrote:
On Fri, Apr 07, 2006 at 05:53:06PM -0700, charles norwood wrote:
On Fri, 2006-04-07 at 16:22 -0500, Hugo Vanwoerkom wrote:
Hi,
I do:
umount /hda14
and get:
umount: /hda14: device is busy
umount: /hda14: device is busy
Is there a wa
On Fri, Apr 07, 2006 at 05:53:06PM -0700, charles norwood wrote:
> On Fri, 2006-04-07 at 16:22 -0500, Hugo Vanwoerkom wrote:
> > Hi,
> >
> > I do:
> >
> > umount /hda14
> >
> > and get:
> >
> > umount: /hda14: device is busy
> > umount: /hda14: device is busy
> >
> >
> > Is there a way of fin
Hugo Vanwoerkom wrote:
Hi,
I do:
umount /hda14
and get:
umount: /hda14: device is busy
umount: /hda14: device is busy
Is there a way of finding out *why* it is busy? Obviously it is linked
to someplace, but where?
Thanks!
H
You can try "lsof" to find what is keeping the device busy:
On Fri, 2006-04-07 at 16:22 -0500, Hugo Vanwoerkom wrote:
> Hi,
>
> I do:
>
> umount /hda14
>
> and get:
>
> umount: /hda14: device is busy
> umount: /hda14: device is busy
>
>
> Is there a way of finding out *why* it is busy? Obviously it is linked
> to someplace, but where?
>
> Thanks!
>
On Fri, 2006-04-07 at 16:22 -0500, Hugo Vanwoerkom wrote:
> Hi,
>
> I do:
>
> umount /hda14
>
> and get:
>
> umount: /hda14: device is busy
> umount: /hda14: device is busy
>
>
> Is there a way of finding out *why* it is busy? Obviously it is linked
> to someplace, but where?
>
> Thanks!
>
7 matches
Mail list logo