All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Kooman <stefan-68+x73Hep80@public.gmane.org>
To: Abhishek Lekshmanan <abhishek-IBi9RG/b67k@public.gmane.org>
Cc: ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	ceph-users-Qp0mS5GaXlQ@public.gmane.org,
	ceph-maintainers-Qp0mS5GaXlQ@public.gmane.org,
	ceph-announce-Qp0mS5GaXlQ@public.gmane.org
Subject: Re: v12.2.7 Luminous released
Date: Tue, 17 Jul 2018 20:24:19 +0200	[thread overview]
Message-ID: <20180717182419.GA1559@shell.dmz.bit.nl> (raw)
In-Reply-To: <87tvox968t.fsf-IBi9RG/b67k@public.gmane.org>

Quoting Abhishek Lekshmanan (abhishek-IBi9RG/b67k@public.gmane.org):

> *NOTE* The v12.2.5 release has a potential data corruption issue with
> erasure coded pools. If you ran v12.2.5 with erasure coding, please see
> below.

< snip >

> Upgrading from v12.2.5 or v12.2.6
> ---------------------------------
> 
> If you used v12.2.5 or v12.2.6 in combination with erasure coded
> pools, there is a small risk of corruption under certain workloads.
> Specifically, when:

< snip >

One section mentions Luminous clusters _with_ EC pools specifically, the other
section mentions Luminous clusters running 12.2.5. I might be
misreading this, but to make  things clear for current Ceph Luminous
12.2.5 users. Is the following statement correct?

If you do _NOT_ use EC in your 12.2.5 cluster (only replicated pools), there is
no need to quiesce IO (ceph osd pause).

http://docs.ceph.com/docs/master/releases/luminous/#upgrading-from-other-versions
If your cluster did not run v12.2.5 or v12.2.6 then none of the above
issues apply to you and you should upgrade normally.

^^ Above section would indicate all 12.2.5 luminous clusters.

Please clarify,

Thanks,

Stefan

-- 
| BIT BV  http://www.bit.nl/        Kamer van Koophandel 09090351
| GPG: 0xD14839C6                   +31 318 648 688 / info-68+x73Hep80@public.gmane.org

  parent reply	other threads:[~2018-07-17 18:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-17 16:28 v12.2.7 Luminous released Abhishek Lekshmanan
     [not found] ` <87tvox968t.fsf-IBi9RG/b67k@public.gmane.org>
2018-07-17 18:24   ` Stefan Kooman [this message]
     [not found]     ` <20180717182419.GA1559-VkyGEX2O1ez1kYbDYJMsfg@public.gmane.org>
2018-07-17 18:42       ` Sage Weil
     [not found]         ` <alpine.DEB.2.11.1807171838180.15696-qHenpvqtifaMSRpgCs4c+g@public.gmane.org>
2018-07-18  1:04           ` Linh Vu
     [not found]             ` <MEAPR01MB3333E2C456B441629674B2BE81530-6Cj2JuxXxgYyJjs6S75NOcNU+h3Mz0HLvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2018-07-18 11:33               ` Oliver Freyermuth
2018-07-18 12:20               ` Sage Weil
2018-07-18 23:35               ` [Ceph-maintainers] " Sage Weil
     [not found]                 ` <alpine.DEB.2.11.1807182333190.17411-qHenpvqtifaMSRpgCs4c+g@public.gmane.org>
2018-07-19  0:36                   ` Linh Vu
2018-07-18 14:47   ` Nicolas Huillard

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=20180717182419.GA1559@shell.dmz.bit.nl \
    --to=stefan-68+x73hep80@public.gmane.org \
    --cc=abhishek-IBi9RG/b67k@public.gmane.org \
    --cc=ceph-announce-Qp0mS5GaXlQ@public.gmane.org \
    --cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ceph-maintainers-Qp0mS5GaXlQ@public.gmane.org \
    --cc=ceph-users-Qp0mS5GaXlQ@public.gmane.org \
    /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.