public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Coert Waagmeester <lgroups@waagmeester.co.za>
Cc: xfs@oss.sgi.com
Subject: Re: XFS status update for January 2012
Date: Mon, 27 Feb 2012 14:16:08 +0200	[thread overview]
Message-ID: <4F4B7408.8020706@waagmeester.co.za> (raw)
In-Reply-To: <4F4B5CB3.8090107@cape-horn-eng.com>

On 02/27/2012 12:36 PM, Richard Ems wrote:
> On 02/25/2012 01:02 PM, Christoph Hellwig wrote:
>> January saw the release of Linux 3.2, which as usual included a large
>> number of XFS changes, most notably an large speedup for removing files
>> that have external attribute blocks, speedups and livelock fixes for
>> sync while doing heavy I/O, and large internal cleanups of the inode
>> block map handling.  The diffstat for XFS in Linux 3.2 is:
>>
>>   54 files changed, 2414 insertions(+), 2625 deletions(-)
>>
>> which is slightly below the average of the last releases.
>>
>> In the meantime development for 3.3 went ahead full speed, including
>> the removal of the deprecated pre-delaylog logging code, various
>> quota cleanups, a shrink of the inode, a great simplification of the file
>> write path as well as the usual batch of fixes and cleanups.
>>
>> On the userland side xfs_repair saw various major fixes and speedups,
>> with few other fixes thrown in, while xfsdump got two commits fixing
>> longer standing issues recently reported on the mailing list.  For
>> xfstests January was an extremely slow month, seeing only two new test cases
>> and less than a handful of other updates.
>
> Many thanks to all of your for the good work and support on the mailing
> list !
>
> cheers,
> Richard
>
>

Hello Richard,

Here I am running gentoo with kernel 3.2
In the 2.6 era I always mounted my xfs file systems with the delaylog 
option, is this still necessary? Is delaylog now default?


Kind regards,
Coert Waagmeester

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

  reply	other threads:[~2012-02-27 12:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-25 12:02 XFS status update for January 2012 Christoph Hellwig
2012-02-27 10:36 ` Richard Ems
2012-02-27 12:16   ` Coert Waagmeester [this message]
2012-02-27 12:53     ` Richard Ems
2012-02-28  8:33       ` Christoph Hellwig

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=4F4B7408.8020706@waagmeester.co.za \
    --to=lgroups@waagmeester.co.za \
    --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