From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: inode64 directory placement determinism
Date: Sun, 17 Aug 2014 22:29:21 -0500 [thread overview]
Message-ID: <e1eeba7b0fb97c63e41f40ed9ac162d7@localhost> (raw)
Say I have a single 4TB disk in an md linear device. The md device has a
filesystem on it formatted with defaults. It has 4 AGs, 0-3. I have
created 4 directories. Each should reside in a different AG, the first in
AG0. Now I expand the linear device with an identical 4TB disk and execute
xfs_growfs. I now have 4 more AGs, 4-7. I create 4 more directories.
Will these 4 new dirs be created sequentially in AGs 4-7, or in the first
4 AGs? Is this deterministic, or is there any chance involved? On the
real system these 4TB drives are actually 48TB LUNs. I'm after
deterministic parallel bandwidth to subsequently added RAIDs after each
grow operation by simply writing to the proper directory.
Currently we have kernel 3.4.26 to work with if that's relevant. I may be
able to get the kernel team to go for 3.4.103 for the bugfixes, but I don't
know about anything newer. This is an embedded type development process.
Thanks,
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2014-08-18 3:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 3:29 Stan Hoeppner [this message]
2014-08-18 7:01 ` inode64 directory placement determinism Dave Chinner
2014-08-18 16:16 ` Stan Hoeppner
2014-08-18 22:48 ` Dave Chinner
2014-08-19 0:02 ` Stan Hoeppner
2014-08-24 20:14 ` stan hoeppner
2014-08-25 2:15 ` Stan Hoeppner
2014-08-25 2:19 ` Dave Chinner
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=e1eeba7b0fb97c63e41f40ed9ac162d7@localhost \
--to=stan@hardwarefreak.com \
--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