From: Eric Sandeen <sandeen@sandeen.net>
To: "AndrewL733@aol.com" <AndrewL733@aol.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS and DPX files
Date: Mon, 02 Nov 2009 15:34:34 -0600 [thread overview]
Message-ID: <4AEF506A.8060803@sandeen.net> (raw)
In-Reply-To: <4AEC4BAA.20606@aol.com>
AndrewL733@aol.com wrote:
>
>> Maybe you should try mounting the XFS filesystem with these options :
>> nobarrier,noatime
>>
>>
> Thanks. Already doing that -- 3ware controller does not support
> barriers, so that's automatically ruled out (you see a message in the
> syslog when mounting the filesystem that barriers will not be used).
> Already mounting with "noatime". Also have been trying "filestreams".
Filestreams is really only useful if you have multiple threads writing
in this manner - for example 2 different movie streams.
Normally an allocation group is chosen for all new files in a directory,
so if you have 2 streams to 2 directories you are writing to 2 ag's ...
all is good until those ags get full and things spill over. At that
point you may wind up interleaving those files from both streams in a
3rd ag.
the filestreams option more or less locks out the new ag from other
streams, so that stuff stays segregated.
If this is your situation (multiple streams, each to their own
directory), then filestreams may help. I think for a single stream of
files, for a single video source, it won't matter.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-11-02 21:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 12:26 XFS and DPX files AndrewL733
2009-10-31 14:18 ` Emmanuel Florac
2009-10-31 14:37 ` AndrewL733
2009-10-31 16:48 ` Emmanuel Florac
2009-11-02 11:05 ` Michael Monnerie
2009-11-02 17:52 ` Emmanuel Florac
2009-11-02 21:50 ` AndrewL733
2009-11-02 22:26 ` Emmanuel Florac
2009-11-03 3:09 ` Eric Sandeen
2009-11-02 21:58 ` Michael Monnerie
2009-11-03 11:19 ` Emmanuel Florac
2009-11-03 20:58 ` Michael Monnerie
2009-12-14 16:17 ` Martin Spott
2009-12-14 17:49 ` Michael Weissenbacher
2009-11-02 21:34 ` Eric Sandeen [this message]
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=4AEF506A.8060803@sandeen.net \
--to=sandeen@sandeen.net \
--cc=AndrewL733@aol.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