On Tue, Nov 28, 2017 at 1:50 PM, Jens-U. Mozdzen wrote:
> Hi David,
>
> Zitat von David C :
>
>> On 27 Nov 2017 1:06 p.m., "Jens-U. Mozdzen" wrote:
>>
>> Hi David,
>>
>> Zitat von David C :
>>
>> Hi Jens
>>
>>>
Hi David,
Zitat von David C :
On 27 Nov 2017 1:06 p.m., "Jens-U. Mozdzen" wrote:
Hi David,
Zitat von David C :
Hi Jens
We also see these messages quite frequently, mainly the "replicating
dir...". Only seen "failed to open
Hi,
Zitat von "Yan, Zheng" :
On Sat, Nov 25, 2017 at 2:27 AM, Jens-U. Mozdzen wrote:
Hi all,
[...]
In the log of the active MDS, we currently see the following two inodes
reported over and over again, about every 30 seconds:
--- cut here ---
2017-11-24
On 27 Nov 2017 1:06 p.m., "Jens-U. Mozdzen" wrote:
Hi David,
Zitat von David C :
Hi Jens
>
> We also see these messages quite frequently, mainly the "replicating
> dir...". Only seen "failed to open ino" a few times so didn't do any real
>
Hi David,
Zitat von David C :
Hi Jens
We also see these messages quite frequently, mainly the "replicating
dir...". Only seen "failed to open ino" a few times so didn't do any real
investigation. Our set up is very similar to yours, 12.2.1, active/standby
MDS and
Hi Jens
We also see these messages quite frequently, mainly the "replicating
dir...". Only seen "failed to open ino" a few times so didn't do any real
investigation. Our set up is very similar to yours, 12.2.1, active/standby
MDS and exporting cephfs through KNFS (hoping to replace with Ganesha
Hi,
Zitat von "Yan, Zheng" :
On Sat, Nov 25, 2017 at 2:27 AM, Jens-U. Mozdzen wrote:
[...]
In the log of the active MDS, we currently see the following two inodes
reported over and over again, about every 30 seconds:
--- cut here ---
2017-11-24
On Sat, Nov 25, 2017 at 2:27 AM, Jens-U. Mozdzen wrote:
> Hi all,
>
> with our Ceph Luminous CephFS, we're plaqued with "failed to open ino"
> messages. These don't seem to affect daily business (in terms of "file
> access"). (There's a backup performance issue that may
Hi all,
with our Ceph Luminous CephFS, we're plaqued with "failed to open ino"
messages. These don't seem to affect daily business (in terms of "file
access"). (There's a backup performance issue that may eventually be
related, but I'll report on that in a different thread.)
Our Ceph