From: Phil Turmel <philip@turmel.org>
To: simonmcnair@gmail.com
Cc: Roman Mamedov <rm@romanrm.ru>, linux-raid@vger.kernel.org
Subject: Re: flummoxed why I can't umount my md device. fuser and lsof show no files locked
Date: Mon, 20 Jun 2011 15:06:35 -0400 [thread overview]
Message-ID: <4DFF9A3B.5040605@turmel.org> (raw)
In-Reply-To: <4DFF8E6C.8080100@gmail.com>
Hi Simon,
On 06/20/2011 02:16 PM, Simon McNair wrote:
> Hi Roman,
> Sorry for the stupid omission, I did try running umount /media/local/Raid to no avail. The other thing I also tried was the lazy dismount option, but it never unmounted, I did a force, then remount and dismount, but it didn't make any difference to the errors. none of the processes have a working directory in the Raid folder as it is just for storage, the OS and apps are on a separate drive entirely. I also ensured that my ssh session was not in the /media/local folder either.
>
> I am pretty sure that I actually want the array running in order to run a mkfs against it (obviously) I just tried that as a last ditch attempt. I'm really just trying to figure out how I can find out what process has the folder locked if lsof and fuser can't tell me :-)
You have to consider that the kernel itself may be holding it open. The most common cause in my experience is a loop mounted file, or stacked userspace filesystem. What does lsdrv[1] say? If a loop device is active, run "losetup -a".
Phil
[1] http://github.com/pturmel/lsdrv
prev parent reply other threads:[~2011-06-20 19:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 17:48 flummoxed why I can't umount my md device. fuser and lsof show no files locked Simon McNair
2011-06-20 18:03 ` Roman Mamedov
2011-06-20 18:16 ` Simon McNair
2011-06-20 19:06 ` Phil Turmel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DFF9A3B.5040605@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=rm@romanrm.ru \
--cc=simonmcnair@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.