From: Brian Foster <bfoster@redhat.com>
To: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
Cc: xfs@oss.sgi.com
Subject: Re: [FAQ v2] XFS speculative preallocation
Date: Mon, 7 Apr 2014 15:58:20 -0400 [thread overview]
Message-ID: <20140407195819.GE48184@bfoster.bfoster> (raw)
In-Reply-To: <201404072108.59322.arekm@maven.pl>
On Mon, Apr 07, 2014 at 09:08:59PM +0200, Arkadiusz Miśkiewicz wrote:
> On Monday 07 of April 2014, Brian Foster wrote:
>
> > Q: How can I speed up or avoid delayed removal of speculative
> > preallocation?
> >
> > A:
> >
> > Remove the inode from the VFS cache or unmount the filesystem to remove
> > speculative preallocations associated with an inode.
>
> "Remove all inodes from the VFS cache" + ? AFAIK there is no way to remove
> single inode from cache. Example would be nice, too.
>
Yeah, that's confusing. If people prefer this bit to stay (I prefer to
nuke it, as noted in my previous reply), then I'll have to word it more
accurately and cautiously. Thanks.
Brian
> --
> Arkadiusz Miśkiewicz, arekm / maven.pl
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-04-07 19:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 15:39 [FAQ v2] XFS speculative preallocation Brian Foster
2014-04-07 19:08 ` Eric Sandeen
2014-04-07 19:56 ` Brian Foster
2014-04-07 19:08 ` Arkadiusz Miśkiewicz
2014-04-07 19:58 ` Brian Foster [this message]
2014-04-07 19:58 ` Mark Tinguely
2014-04-07 21:45 ` Brian Foster
2014-04-07 22:21 ` Mark Tinguely
2014-04-07 22:57 ` Dave Chinner
2014-04-08 12:04 ` Brian Foster
2014-04-07 22:54 ` Dave Chinner
2014-04-17 13:07 ` Brian Foster
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=20140407195819.GE48184@bfoster.bfoster \
--to=bfoster@redhat.com \
--cc=arekm@maven.pl \
--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 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.