On Fri, Feb 5, 2016 at 10:19 PM, Michael Metz-Martini | SpeedPartner
GmbH wrote:
> Hi,
>
> Am 06.02.2016 um 07:15 schrieb Yan, Zheng:
>>> On Feb 6, 2016, at 13:41, Michael Metz-Martini | SpeedPartner GmbH
>>> wrote:
>>> Am 04.02.2016 um 15:38 schrieb Yan, Zheng:
> On Feb 4, 2016, at 17:00, M
Hi,
Am 06.02.2016 um 07:15 schrieb Yan, Zheng:
>> On Feb 6, 2016, at 13:41, Michael Metz-Martini | SpeedPartner GmbH
>> wrote:
>> Am 04.02.2016 um 15:38 schrieb Yan, Zheng:
On Feb 4, 2016, at 17:00, Michael Metz-Martini | SpeedPartner GmbH
wrote:
Am 04.02.2016 um 09:43 schrieb Y
> On Feb 6, 2016, at 13:41, Michael Metz-Martini | SpeedPartner GmbH
> wrote:
>
> Hi,
>
> sorry for the delay - productional system unfortunately ;-(
>
> Am 04.02.2016 um 15:38 schrieb Yan, Zheng:
>>> On Feb 4, 2016, at 17:00, Michael Metz-Martini | SpeedPartner GmbH
>>> wrote:
>>> Am 04.02
Hi,
sorry for the delay - productional system unfortunately ;-(
Am 04.02.2016 um 15:38 schrieb Yan, Zheng:
>> On Feb 4, 2016, at 17:00, Michael Metz-Martini | SpeedPartner GmbH
>> wrote:
>> Am 04.02.2016 um 09:43 schrieb Yan, Zheng:
>>> On Thu, Feb 4, 2016 at 4:36 PM, Michael Metz-Martini | Spe
> On Feb 4, 2016, at 17:00, Michael Metz-Martini | SpeedPartner GmbH
> wrote:
>
> Hi,
>
> Am 04.02.2016 um 09:43 schrieb Yan, Zheng:
>> On Thu, Feb 4, 2016 at 4:36 PM, Michael Metz-Martini | SpeedPartner
>> GmbH wrote:
>>> Am 03.02.2016 um 15:55 schrieb Yan, Zheng:
> On Feb 3, 2016, at 21
Hi,
Am 04.02.2016 um 09:43 schrieb Yan, Zheng:
> On Thu, Feb 4, 2016 at 4:36 PM, Michael Metz-Martini | SpeedPartner
> GmbH wrote:
>> Am 03.02.2016 um 15:55 schrieb Yan, Zheng:
On Feb 3, 2016, at 21:50, Michael Metz-Martini | SpeedPartner GmbH
wrote:
Am 03.02.2016 um 12:11 schrie
On Thu, Feb 4, 2016 at 4:36 PM, Michael Metz-Martini | SpeedPartner
GmbH wrote:
> Hi,
>
> Am 03.02.2016 um 15:55 schrieb Yan, Zheng:
>>> On Feb 3, 2016, at 21:50, Michael Metz-Martini | SpeedPartner GmbH
>>> wrote:
>>> Am 03.02.2016 um 12:11 schrieb Yan, Zheng:
> On Feb 3, 2016, at 17:39, Mi
Hi,
Am 03.02.2016 um 15:55 schrieb Yan, Zheng:
>> On Feb 3, 2016, at 21:50, Michael Metz-Martini | SpeedPartner GmbH
>> wrote:
>> Am 03.02.2016 um 12:11 schrieb Yan, Zheng:
On Feb 3, 2016, at 17:39, Michael Metz-Martini | SpeedPartner GmbH
wrote:
Am 03.02.2016 um 10:26 schrieb G
> On Feb 3, 2016, at 21:50, Michael Metz-Martini | SpeedPartner GmbH
> wrote:
>
> Hi,
>
> Am 03.02.2016 um 12:11 schrieb Yan, Zheng:
>>> On Feb 3, 2016, at 17:39, Michael Metz-Martini | SpeedPartner GmbH
>>> wrote:
>>> Am 03.02.2016 um 10:26 schrieb Gregory Farnum:
On Tue, Feb 2, 2016 a
Hi,
Am 03.02.2016 um 12:11 schrieb Yan, Zheng:
>> On Feb 3, 2016, at 17:39, Michael Metz-Martini | SpeedPartner GmbH
>> wrote:
>> Am 03.02.2016 um 10:26 schrieb Gregory Farnum:
>>> On Tue, Feb 2, 2016 at 10:09 PM, Michael Metz-Martini | SpeedPartner
>>> GmbH wrote:
>>> Or maybe your kernels are
> On Feb 3, 2016, at 17:39, Michael Metz-Martini | SpeedPartner GmbH
> wrote:
>
> Hi,
>
> Am 03.02.2016 um 10:26 schrieb Gregory Farnum:
>> On Tue, Feb 2, 2016 at 10:09 PM, Michael Metz-Martini | SpeedPartner
>> GmbH wrote:
>>> Putting some higher load via cephfs on the cluster leads to messa
Hi,
Am 03.02.2016 um 10:26 schrieb Gregory Farnum:
> On Tue, Feb 2, 2016 at 10:09 PM, Michael Metz-Martini | SpeedPartner
> GmbH wrote:
>> Putting some higher load via cephfs on the cluster leads to messages
>> like mds0: Client X failing to respond to capability release after some
>> minutes. Re
On Tue, Feb 2, 2016 at 10:09 PM, Michael Metz-Martini | SpeedPartner
GmbH wrote:
> Hi,
>
> we're experiencing some strange issues running ceph 0.87 in our, I
> think, quite large cluster (taking number of objects as a measurement).
>
> mdsmap e721086: 1/1/1 up {0=storagemds01=up:active}, 2 up
Hi,
we're experiencing some strange issues running ceph 0.87 in our, I
think, quite large cluster (taking number of objects as a measurement).
mdsmap e721086: 1/1/1 up {0=storagemds01=up:active}, 2 up:standby
osdmap e143048: 92 osds: 92 up, 92 in
flags noout,noscrub,nodeep-s
14 matches
Mail list logo