From: LA Walsh <xfs@tlinx.org>
To: xfs-oss <xfs@oss.sgi.com>
Subject: Re: Q: about xfs pre-allocation
Date: Tue, 10 Dec 2013 20:12:13 -0800 [thread overview]
Message-ID: <52A7E61D.3040900@tlinx.org> (raw)
In-Reply-To: <20131211014638.GG10988@dastard>
On 12/10/2013 5:46 PM, Dave Chinner wrote:
> On Tue, Dec 10, 2013 at 10:06:24AM -0800, LA Walsh wrote:
>> Could someone comment on my [mis-]understanding in regards to
>> what the note below said
>
> It's mostly wrong information.
>
> Just a suggestion: take anything advice given about XFS on lists
> other than this one with a grain of salt. There's lots of people out
> there who *think* they know how XFS works, but there's very few who
> actually know how XFS works.
---
Well, even thinking I had a clue, I wanted to check here, cuz, things
change and I might give out totally wrong info... yuck...
I appreciate your expertise and tireless[?] efforts on a great FS.
=====
Brian,
Thanks for the different detail and emphasis...
Sometimes I need to read something in multiple ways to fully get it
(assuming I 'get' it...)
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-12-11 4:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 18:06 Q: about xfs pre-allocation LA Walsh
2013-12-11 1:46 ` Dave Chinner
2013-12-11 4:12 ` LA Walsh [this message]
2013-12-11 1:49 ` 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=52A7E61D.3040900@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