All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wido den Hollander <wido@42on.com>
To: Sage Weil <sage@newdream.net>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: inode64 mount option for XFS
Date: Mon, 03 Nov 2014 15:32:51 +0100	[thread overview]
Message-ID: <54579213.5070900@42on.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1411030619220.15135@cobra.newdream.net>

On 11/03/2014 03:20 PM, Sage Weil wrote:
> On Mon, 3 Nov 2014, Wido den Hollander wrote:
>> Hi,
>>
>> While look at init-ceph and ceph-disk I noticed a discrepancy between them.
>>
>> init-ceph mounts XFS filesystems with rw,noatime,inode64, but
>> ceph-disk(-active) with rw,noatime
>>
>> As inode64 gives the best performance, shouldn't ceph-disk do the same?
> 
> I noticed this a while back but didn't finish fixing it.. can you take a 
> look at wip-xfs-inode64 and see if it looks right?
>  

Looks good to me. Simple fix, but that should do it.

>> Any implications if we add inode64 on running deployments?
> 
> I don't think so!  Note that on new kernels I think inode64 is now the 
> default, so this is really about performance on older systems (precise, 
> rhel6, probably).
> 

Yes, I noticed that later on. But it gives consistency. Ubuntu precise
and RHEL 6 will be around for quite some time, so it would be better to
enable it for those systems as well.

Wido

> sage
> 
>>
>> -- 
>> Wido den Hollander
>> 42on B.V.
>> Ceph trainer and consultant
>>
>> Phone: +31 (0)20 700 9902
>> Skype: contact42on
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


-- 
Wido den Hollander
42on B.V.
Ceph trainer and consultant

Phone: +31 (0)20 700 9902
Skype: contact42on

  reply	other threads:[~2014-11-03 14:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03 12:28 inode64 mount option for XFS Wido den Hollander
2014-11-03 12:34 ` Stefan Priebe - Profihost AG
2014-11-03 12:38   ` Wido den Hollander
2014-11-03 14:20 ` Sage Weil
2014-11-03 14:32   ` Wido den Hollander [this message]
2014-11-05 13:01     ` Sage Weil

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=54579213.5070900@42on.com \
    --to=wido@42on.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sage@newdream.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.