From: Martin Steigerwald <martin@lichtvoll.de>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: fuser ct1 <fuserct1@gmail.com>, linux-xfs@vger.kernel.org
Subject: Re: Safe XFS limits (100TB+)
Date: Thu, 02 Feb 2017 20:14:34 +0100 [thread overview]
Message-ID: <9176347.zh1PoPzZKX@merkaba> (raw)
In-Reply-To: <20170202191627.42c50e67@harpe.intellique.com>
Am Donnerstag, 2. Februar 2017, 19:16:27 CET schrieb Emmanuel Florac:
> Use recent xfs progs and kernel, use xfs v5 if possible. Don't forget
> proper optimisations (use noop scheduler, enlarge nr_requests and
> read_ahead_kb a lot) for high sequential throughput (video is all about
> sequential throughput) and you should be happy and safe.
Just adding some Debian hints:
For Debian Jessie that means backport kernel – that means 4.8 currently. There
is not backport of xfsprogs available tough and 3.2 is pretty old. I am not
sure since when xfsprogs was switched to create xfs v5 by default – so maybe
the proper options to activate xfs v5 are needed. There is always the option
to compile xfsprogs yourself, or well just start out with Debian Testing as
that in the process of being frozen more and more before release of Debian
Stretch. I would be surprised of any major hichups regarding XFS in Debian
Testing before the release. It will very likely have kernel 4.9 and xfsprogs
4.9.
Thanks,
--
Martin
next prev parent reply other threads:[~2017-02-02 19:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 16:46 Safe XFS limits (100TB+) fuser ct1
2017-02-02 17:16 ` Eric Sandeen
2017-02-02 17:52 ` fuser ct1
2017-02-02 17:55 ` Eric Sandeen
2017-02-02 18:16 ` Emmanuel Florac
2017-02-02 19:14 ` Martin Steigerwald [this message]
[not found] ` <CAL8yqih36vWy-Z1PESVZOqDEoW8G9=k5LBM0aToe4JhBM755bA@mail.gmail.com>
2017-02-03 17:10 ` Emmanuel Florac
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=9176347.zh1PoPzZKX@merkaba \
--to=martin@lichtvoll.de \
--cc=eflorac@intellique.com \
--cc=fuserct1@gmail.com \
--cc=linux-xfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).