From: Chris Wedgwood <cw@f00f.org>
To: Cosmo Nova <cs_mcc98@hotmail.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: file system defragmentation
Date: Mon, 17 Jul 2006 12:08:27 -0700 [thread overview]
Message-ID: <20060717190827.GA7845@tuatara.stupidest.org> (raw)
In-Reply-To: <5356806.post@talk.nabble.com>
On Mon, Jul 17, 2006 at 12:36:09AM -0700, Cosmo Nova wrote:
> If I have a DVR system of 16 channels. They keep writing data to the
> disk in pieces of video files.
I did some work for someone who does a similar thing (they write 96
channels in parallel and have to be able to do read back up to 32 of
them at the same time of something).
By default concurrent writes into the same directory will cause the
files to get badly interleaved, and trying to get one file per-ag
doesn't work so well if the agcount < n-files.
I ended up getting them to change their code to preallocate and AFAIK
it works very well now (you can throw away any space you over allocate
when you're closing the file too).
next prev parent reply other threads:[~2006-07-17 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4f52331f050826001612f8e323@mail.gmail.com>
[not found] ` <20050826101131.GA24544@ii.uib.no>
[not found] ` <4f52331f0508260848782f240a@mail.gmail.com>
[not found] ` <43128F82.4010004@tlinx.org>
[not found] ` <4312913F.6040205@coremetrics.com>
[not found] ` <43311567.3060208@tlinx.org>
2006-07-17 7:36 ` file system defragmentation Cosmo Nova
2006-07-17 9:32 ` David Chatterton
2006-07-17 14:19 ` David Chinner
2006-07-18 7:59 ` Cosmo Nova
2006-07-18 21:33 ` Chris Wedgwood
2006-07-19 10:33 ` Cosmo Nova
2006-07-17 19:08 ` Chris Wedgwood [this message]
[not found] ` <E4E12CD035E14A4AB8C36E0F4B7143F7277DED@iu-mssg-mbx09.exchange.iu.edu>
[not found] ` <43112C5D.8090202@sgi.com>
[not found] ` <20050829001723.GA10587@xiao.rsnet>
2006-07-20 4:22 ` Cosmo Nova
[not found] ` <20050828034108.73921.qmail@web34103.mail.mud.yahoo.com>
2006-07-20 4:23 ` Cosmo Nova
2006-08-08 23:34 ` David 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=20060717190827.GA7845@tuatara.stupidest.org \
--to=cw@f00f.org \
--cc=cs_mcc98@hotmail.com \
--cc=linux-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