public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Linda Walsh <xfs@tlinx.org>
To: xfs-oss <xfs@oss.sgi.com>
Subject: FYI: better workaround for updating 'df' info after 'rm' on xfs-vols
Date: Mon, 25 Feb 2013 17:41:09 -0800	[thread overview]
Message-ID: <512C12B5.3070908@tlinx.org> (raw)

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.

Mentioned that I had tried 'sync' to no avail, and had
only found umount/mount to cause the figures to synchronize.

Someone suggested cat [1|3] >/proc/sys/vm/drop_caches.
That works as a 1 time event, but I've found that doing
so only works once/system uptime (if you 'cat' drop_caches'
it retains the last value you put there, and doesn't accept
a new value with fewer bits set than what you echo'd to it
originally (you can change from 1>3, but then not from 3>1 or
(3|1)>0.  So not so useful.

Prob w/unmounting was inuse file descriptors (being exported
by samba to clients being the most likely culprit).

This might not be wise if the FS was actively being written
to for a backup, but temporarily doing a

    mount -o remount,ro /backups && mount -o remount,rw /backups

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.


_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2013-02-26  1:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26  1:41 Linda Walsh [this message]
2013-02-26  4:50 ` FYI: better workaround for updating 'df' info after 'rm' on xfs-vols Dave Chinner
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=512C12B5.3070908@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