linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Max Veprinsky <max.veprinsky@livetext.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: releasing space after rapid grwoth
Date: Mon, 24 Jan 2011 13:05:24 -0500	[thread overview]
Message-ID: <20110124180524.GA15056@fieldses.org> (raw)
In-Reply-To: <AANLkTi=R_j3_hZ-7RpSn0_Mee43nU0njPRBSn=DiEf8R@mail.gmail.com>

On Fri, Jan 21, 2011 at 05:06:45PM -0600, Max Veprinsky wrote:
> Hello all,
> 
> I'm trying to reclaim disk space on stable storage which was consumed
> by a crashed apache process at a rate of ~100GB/hour. This issue has
> happened a few times before and normally resolved by discovering a
> .nfsXXXXX file, stopping the process on the the application server
> that was holding the file. Sometimes the used filespace is recovered
> quickly without manual intervention, other times I had to delete the
> .nfsXXXX file manually.
> 
> Last time this happened 3 TB of disk space was consumed and no
> .nfsXXXX file of that size was discovered, nor. I dismounted all of
> the volumes from the clients 1/2 of the space was recovered.
> 
> showmount shows clients connected but there are no network nfs
> connections open to any client.

And all the clients *have* unmounted, right?

> I have not restarted nfs server
> service fearing that the used space would not be recovered.
> 
> Any suggestion greatly appreciated

More details about the setup?  Are clients and server all Linux, and
what kernel versions?

--b.

      reply	other threads:[~2011-01-24 18:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21 23:06 releasing space after rapid grwoth Max Veprinsky
2011-01-24 18:05 ` J. Bruce Fields [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=20110124180524.GA15056@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=max.veprinsky@livetext.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).