From: Guy Waugh <gwaugh@scu.edu.au>
To: linux-admin@vger.kernel.org
Subject: Re: How to access contents of directory underneath mounted volume?
Date: Wed, 27 Aug 2008 10:10:01 +1000 [thread overview]
Message-ID: <48B49B59.6030801@scu.edu.au> (raw)
In-Reply-To: <18611.29022.835143.552260@cerise.gclements.plus.com>
Glynn Clements wrote:
> Guy Waugh wrote:
>
>> On a RHEL4 host, I have a mountpoint, /thing, with a SAN volume mounted
>> at this mountpoint.
>>
>> The local volume that contains the mountpoint (i.e. the volume that is
>> mounted at /) is nearly full, and I'm suspecting it is because there are
>> files on the local volume in the /thing directory. Of course, I can't
>> get to the /thing directory by normal means (at least AFAIK), because
>> there is currently a volume mounted at that mountpoint.
>>
>> Does anyone know if it possible to access (i.e. see and delete) the
>> files in the /thing directory without having to umount the SAN volume
>> that is mounted at /thing?
>
> If some existing process has its CWD underneath /thing, then you can
> access that directory via /proc/<pid>/cwd.
>
> You could use debugfs on the root fs, but I wouldn't recommend trying
> to modify a filesystem while it's mounted r/w.
>
> If you can't unmount the SAN because it's busy, you may still be able
> to move its mount point with "mount --move". If you can allow for it
> being unavailable briefly you could move it off just long enough to
> rename the underlying directory, e.g.:
>
> mkdir /thing.tmp
> mount --move /thing /thing.tmp
> mv /thing /thing.orig
> mkdir /thing
> mount --move /thing.tmp /thing
> rmdir /thing.tmp
Thanks Glynn, the last suggestion using "mount --move" looks like the
most useful. However, it's sounding like it's going to be easiest for me
to schedule some downtime.
Cheers,
Guy.
prev parent reply other threads:[~2008-08-27 0:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 1:32 How to access contents of directory underneath mounted volume? Guy Waugh
2008-08-26 2:58 ` Glynn Clements
2008-08-27 0:10 ` Guy Waugh [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=48B49B59.6030801@scu.edu.au \
--to=gwaugh@scu.edu.au \
--cc=linux-admin@vger.kernel.org \
/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.