From: ArmedAviator <ArmedAviator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: glusterfs: update to 8.1
Date: Tue, 20 Oct 2020 02:48:35 +0200 [thread overview]
Message-ID: <20201020004835.tr79j2G9vcMSAwV0Kt1wUO_wlRF4o13kwKeUR4kJ93U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25617@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 702 bytes --]
New comment by ArmedAviator on void-packages repository
https://github.com/void-linux/void-packages/pull/25617#issuecomment-712520231
Comment:
I've been running this PR on 22TB data replicated across 2 machines and an arbiter VM since I submitted the PR. No issues, as usual with Gluster major version upgrades.
Just remember, once you increase the op-version (manual input required), there's no going back.
```
rich@proton ~ $ sudo gluster volume get all cluster.op-version
Option Value
------ -----
cluster.op-version 80000
```
next prev parent reply other threads:[~2020-10-20 0:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 3:28 [PR PATCH] " ArmedAviator
2020-10-15 3:55 ` ArmedAviator
2020-10-15 4:38 ` ericonr
2020-10-15 6:12 ` [PR PATCH] [Updated] " ArmedAviator
2020-10-15 6:15 ` ArmedAviator
2020-10-15 6:20 ` ArmedAviator
2020-10-15 8:49 ` fosslinux
2020-10-15 13:26 ` [PR PATCH] [Updated] " ArmedAviator
2020-10-15 13:30 ` ArmedAviator
2020-10-16 1:49 ` fosslinux
2020-10-17 5:03 ` ericonr
2020-10-19 23:42 ` nilium
2020-10-19 23:42 ` nilium
2020-10-19 23:42 ` nilium
2020-10-20 0:48 ` ArmedAviator [this message]
2020-11-16 19:29 ` [PR PATCH] [Updated] " ArmedAviator
2020-11-16 19:32 ` ArmedAviator
2020-11-16 19:36 ` ArmedAviator
2020-11-16 19:39 ` ArmedAviator
2020-11-22 3:24 ` [PR PATCH] [Merged]: " the-maldridge
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=20201020004835.tr79j2G9vcMSAwV0Kt1wUO_wlRF4o13kwKeUR4kJ93U@z \
--to=armedaviator@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).