From: Dave Chinner <david@fromorbit.com>
To: Linda Walsh <xfs@tlinx.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: FYI: better workaround for updating 'df' info after 'rm' on xfs-vols
Date: Tue, 26 Feb 2013 15:50:38 +1100 [thread overview]
Message-ID: <20130226045038.GN5551@dastard> (raw)
In-Reply-To: <512C12B5.3070908@tlinx.org>
On Mon, Feb 25, 2013 at 05:41:09PM -0800, Linda Walsh wrote:
> Some time ago I reported that after I deleted
> some large amount of space from one of my xfs volumes,
> 'df' still showed the original, pre-delete space, though
> 'du' only showed the expected amount.
Sure, because unlinked files might not have their second phase of
processing (which releases the disk space) done immediately.
> Mentioned that I had tried 'sync' to no avail, and had
> only found umount/mount to cause the figures to synchronize.
sync doesn't cause unlinked inodes to be reclaimed and processed,
unlike remount,ro, unmount or freeze.
> Someone suggested cat [1|3] >/proc/sys/vm/drop_caches.
echo, not cat. It does work every time, whether you see anything
obvious or not. And if you want to reclaim inodes, then you want
"echo 2 > ..."
> seemed to do the trick and cause the disk space to update without
> me having to stop processes with FD's open on the vol.
freeze/thaw should do what you want without affecting anything
running on the fs at all.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-02-26 4:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 1:41 FYI: better workaround for updating 'df' info after 'rm' on xfs-vols Linda Walsh
2013-02-26 4:50 ` Dave Chinner [this message]
2013-02-26 5:47 ` Linda Walsh
2013-02-26 20:54 ` Dave Chinner
2013-04-02 18:17 ` Linda Walsh
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=20130226045038.GN5551@dastard \
--to=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
--cc=xfs@tlinx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox