From: "Łukasz Chrustek" <skidoo@tlen.pl>
To: Sage Weil <sage@newdream.net>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Problem with query and any operation on PGs
Date: Sun, 11 Jun 2017 00:45:13 +0200 [thread overview]
Message-ID: <948823304.20170611004513@tlen.pl> (raw)
In-Reply-To: <alpine.DEB.2.11.1705301315220.3646@piezo.novalocal>
Hi Sage,
> Okay, sorry I took a while to get back to you.
Sorry too - most of time I was focused on this problem.
> It looks like I gave
> you bad advice here! The 'nosnap' files means filestore was
> operating in non-snapshotting mode, and the --osd-use-stale-snap
> warning that it would lose data was real... it rolled back to an empty
> state and threw out the data on the device. :( :( I'm *very* sorry about
> this! I haven't looked at or worked with the btrfs mode is ages (we
> don't recommend it and almost nobody uses it) but I should have been
> paying close attention.
Thank You for Your time and effort, it was important to have such
help. There were many errors in setup of this cluster. We didn't
relize that there could be so much strange things, which were f...ed
up...
> What is the state of the cluster now?
Cluster is dead. After few more days of fight with cluster we decieded
to shut it down and we fixed scripts for recovering volumes from
turned off ceph cluster (this one:
https://github.com/cmgitdream/ceph-rbd-recover-tool) and make it
running for jewel version (10.2.7). I setup brand new cluster on other
hardware and now images are importing to new cluster. With some direct
edition of mysql in openstack systems we didn't had to change
everything for our clients from horizon point of view. Once the dust
settles, we will add changes to github for this tool.
After end of migration we will try to run this dead cluster and make
some more agressive action to make it work anyway.
--
Regards,,
Lukasz
prev parent reply other threads:[~2017-06-10 22:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <175484591.20170523135449@tlen.pl>
2017-05-23 12:48 ` Problem with query and any operation on PGs Łukasz Chrustek
2017-05-23 14:17 ` Sage Weil
2017-05-23 14:43 ` Łukasz Chrustek
[not found] ` <1464688590.20170523185052@tlen.pl>
2017-05-23 17:40 ` Sage Weil
2017-05-23 21:43 ` Łukasz Chrustek
2017-05-23 21:48 ` Sage Weil
2017-05-24 13:19 ` Łukasz Chrustek
2017-05-24 13:37 ` Sage Weil
2017-05-24 13:58 ` Łukasz Chrustek
2017-05-24 14:02 ` Sage Weil
2017-05-24 14:18 ` Łukasz Chrustek
2017-05-24 14:47 ` Sage Weil
2017-05-24 15:00 ` Łukasz Chrustek
2017-05-24 15:07 ` Łukasz Chrustek
2017-05-24 15:11 ` Sage Weil
2017-05-24 15:24 ` Łukasz Chrustek
2017-05-24 15:54 ` Łukasz Chrustek
2017-05-24 16:02 ` Łukasz Chrustek
2017-05-24 17:07 ` Łukasz Chrustek
2017-05-24 17:16 ` Sage Weil
2017-05-24 17:28 ` Łukasz Chrustek
2017-05-24 18:16 ` Sage Weil
2017-05-24 19:47 ` Łukasz Chrustek
2017-05-24 17:30 ` Łukasz Chrustek
2017-05-24 17:35 ` Łukasz Chrustek
2017-05-24 21:38 ` Łukasz Chrustek
2017-05-24 21:53 ` Sage Weil
2017-05-24 22:09 ` Łukasz Chrustek
2017-05-24 22:27 ` Sage Weil
2017-05-24 22:46 ` Łukasz Chrustek
2017-05-25 2:06 ` Sage Weil
2017-05-25 11:22 ` Łukasz Chrustek
2017-05-29 15:31 ` Łukasz Chrustek
2017-05-30 13:21 ` Sage Weil
2017-06-10 22:45 ` Łukasz Chrustek [this message]
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=948823304.20170611004513@tlen.pl \
--to=skidoo@tlen.pl \
--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.