public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: XFS and DPX files
Date: Mon, 2 Nov 2009 12:05:27 +0100	[thread overview]
Message-ID: <200911021205.28006@zmi.at> (raw)
In-Reply-To: <20091031174836.3fc9505b@galadriel.home>

On Samstag 31 Oktober 2009 Emmanuel Florac wrote:
> Another trick is to mkfs the drive with su and sw matching the
> underlying RAID, for instance for a 15 drives RAID6 with 64K stripe
> use something like (beware, unverified syntax from memory):
>
> mkfs -t xfs -d su=65536,sw=15 /dev/sdXX

I believe for a 15 drive RAID-6, where 2 disks are used for redundancy, 
the correct mkfs would be:
mkfs -t xfs -d su=65536,sw=13 /dev/sdXX

That is, you tell XFS how many *data disks* there are, not how many 
disks the RAID uses, because the important thing is that XFS should 
distribute it's metadata over different disks.

One thing you could try: Each 2 minutes, create a new dir and store new 
files there. It could well be that XFS becomes slower when having a 
certain amount of files in a dir. If you change the dir, and now 
everything writes without drops, that should be the problem.
If you can't change the dir for your application, start a small batch 
job that moves the files to another dir, or removes them.

Another thing to try is if it would help to turn disk cache writes *on*, 
despite all warnings if the FAQ. That could also give an idea where to 
look at next time.

mfg zmi
-- 
// Michael Monnerie, Ing.BSc    -----      http://it-management.at
// Tel: 0660 / 415 65 31                      .network.your.ideas.
// PGP Key:         "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38  500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net                  Key-ID: 1C1209B4

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-11-02 11:05 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 [this message]
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

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=200911021205.28006@zmi.at \
    --to=michael.monnerie@is.it-management.at \
    --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