On 05/02/16 11:43, John Spray wrote:
On Fri, Feb 5, 2016 at 9:36 AM, Kenneth Waegeman
wrote:
On 04/02/16 16:17, Gregory Farnum wrote:
On Thu, Feb 4, 2016 at 1:42 AM, Kenneth Waegeman
wrote:
Hi,
Hi, we are running ceph 9.2.0.
On Fri, Feb 5, 2016 at 3:48 PM, Kenneth Waegeman
wrote:
> Hi,
>
> In my attempt to retry, I ran 'ceph mds newfs' because removing the fs was
> not working (because the mdss could not be stopped).
> With the new fs, I could again start syncing. After 10-15min it all
Hi,
In my attempt to retry, I ran 'ceph mds newfs' because removing the fs
was not working (because the mdss could not be stopped).
With the new fs, I could again start syncing. After 10-15min it all
crashed again. The log now shows some other stacktrace.
-9> 2016-02-05 15:26:29.015197
On Fri, Feb 5, 2016 at 9:36 AM, Kenneth Waegeman
wrote:
>
>
> On 04/02/16 16:17, Gregory Farnum wrote:
>>
>> On Thu, Feb 4, 2016 at 1:42 AM, Kenneth Waegeman
>> wrote:
>>>
>>> Hi,
>>>
>>> Hi, we are running ceph 9.2.0.
>>> Overnight, our ceph
On 04/02/16 16:17, Gregory Farnum wrote:
On Thu, Feb 4, 2016 at 1:42 AM, Kenneth Waegeman
wrote:
Hi,
Hi, we are running ceph 9.2.0.
Overnight, our ceph state went to 'mds mds03 is laggy' . When I checked the
logs, I saw this mds crashed with a stacktrace. I
Hi,
Hi, we are running ceph 9.2.0.
Overnight, our ceph state went to 'mds mds03 is laggy' . When I checked
the logs, I saw this mds crashed with a stacktrace. I checked the other
mdss, and I saw the same there.
When I try to start the mds again, I get again a stacktrace and it won't
come up:
On Thu, Feb 4, 2016 at 1:42 AM, Kenneth Waegeman
wrote:
> Hi,
>
> Hi, we are running ceph 9.2.0.
> Overnight, our ceph state went to 'mds mds03 is laggy' . When I checked the
> logs, I saw this mds crashed with a stacktrace. I checked the other mdss,
> and I saw the