From: "Janos Haar" <janos.haar@netcenter.hu>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-xfs@oss.sgi.com
Subject: Re: 2 question about XFS fragmentation and _fsr: Q2
Date: Tue, 26 Apr 2011 23:49:53 +0200 [thread overview]
Message-ID: <367BBF55D8CD426888E671F8C7422966@myXP> (raw)
In-Reply-To: 20110411233705.GA29358@infradead.org
----- Original Message -----
From: "Christoph Hellwig" <hch@infradead.org>
To: "Dave Chinner" <david@fromorbit.com>
Cc: "Janos Haar" <janos.haar@netcenter.hu>; <linux-xfs@oss.sgi.com>
Sent: Tuesday, April 12, 2011 1:37 AM
Subject: Re: 2 question about XFS fragmentation and _fsr
> On Tue, Apr 12, 2011 at 07:42:38AM +1000, Dave Chinner wrote:
>> Depends on your samba configuration to how it does writes. If it is
>> conigured to do sync writes then it will have all sorts of
>> fragmentation problems. So without more details about the workload,
>> the kernel that is being used, the fragmentation occurring (xfs_bmap
>> is your friend) and the samba config, there's little that can be
>> suggested here.
>
> Very few people configure Samba to do sync writes, but even without
> that I see files written by Samba heavily fragmented when the systems
> operates under intense memory pressure. The CIFS protocol has very
> small write sizes, and it seems like they do not always arrive in order.
> If the system is under enough memory pressure to write them out already
> before the previous fragment arrive it can cause very fragmented
> extent maps. Enabling the "strict allocate" option in newer Samba
> version fixes that problem by doing fallocates in larger chunks, which
> from my observation always happen in order. The downside is that
> current fallocate in XFS is not designed to be used in a fastpath,
> and thus causes performance degradations during the actual write.
Is there anything what i can do in proc/sys/vm configuration to solve the
fragment write problem?
Thanks,
Janos
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-04-26 21:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 17:39 2 question about XFS fragmentation and _fsr Janos Haar
2011-04-11 20:37 ` Stan Hoeppner
2011-04-26 21:21 ` 2 question about XFS fragmentation and _fsr: SPLITTED Q2:normal files, samba share Janos Haar
2011-04-26 21:50 ` 2 question about XFS fragmentation and _fsr: SPLITTED Q1:sparese files Janos Haar
2011-04-11 21:42 ` 2 question about XFS fragmentation and _fsr Dave Chinner
2011-04-11 23:37 ` Christoph Hellwig
2011-04-26 21:49 ` Janos Haar [this message]
2011-04-26 21:51 ` 2 question about XFS fragmentation and _fsr: SPLITTED Q1:sparse files Janos Haar
2011-04-27 20:18 ` Eric Sandeen
2011-04-27 20:37 ` Eric Sandeen
2011-04-26 21:51 ` 2 question about XFS fragmentation and _fsr: SPLITTED Q2:normal files, samba share Janos Haar
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=367BBF55D8CD426888E671F8C7422966@myXP \
--to=janos.haar@netcenter.hu \
--cc=hch@infradead.org \
--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