From: Linda Walsh <xfs@tlinx.org>
To: xfs-oss <xfs@oss.sgi.com>
Subject: Re: FYI: better workaround for updating 'df' info after 'rm' on xfs-vols
Date: Mon, 25 Feb 2013 21:47:38 -0800 [thread overview]
Message-ID: <512C4C7A.60002@tlinx.org> (raw)
In-Reply-To: <20130226045038.GN5551@dastard>
>> 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 > ..."
----
Erk...meant echo... too much draino on the braino
(doesn't 3 include '2'? I thought it was a bit mask?)
> freeze/thaw should do what you want without affecting anything
> running on the fs at all.
---
Thanks... will have to remember / script that ..
Have seen the space not drop for hours!....(literally)..
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-02-26 5:47 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
2013-02-26 5:47 ` Linda Walsh [this message]
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=512C4C7A.60002@tlinx.org \
--to=xfs@tlinx.org \
--cc=xfs@oss.sgi.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