Activity
From 07/28/2019 to 08/26/2019
08/26/2019
- 06:12 PM Bug #40481: osdmap->osd_addr allocation is susceptible to memory fragmentation
- https://www.spinics.net/lists/ceph-users/msg54591.html
- 03:25 PM Bug #40862 (Pending Backport): kclient: crashed after evicted twice
- https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c95f1c5f436badb9bb87e9b30fd573f6b3d5942...
- 03:22 PM Bug #41162 (Pending Backport): checking con->peer_features in calc_target() is fundamentally racy
- https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a561372405cf6bc6f14239b3a9e57bb39f2788b...
08/21/2019
- 12:06 PM Bug #41162 (Fix Under Review): checking con->peer_features in calc_target() is fundamentally racy
- [PATCH] libceph: fix PG split vs OSD (re)connect race
08/13/2019
- 02:18 PM Bug #40481 (In Progress): osdmap->osd_addr allocation is susceptible to memory fragmentation
08/08/2019
- 12:46 PM Bug #41162 (Resolved): checking con->peer_features in calc_target() is fundamentally racy
- ...
- 12:41 PM Feature #12902 (Resolved): krbd: support object-map and fast-diff
- In 5.3-rc1.
08/07/2019
- 02:43 PM Bug #40985: xfstest generic/451 intermittently fails
- Patch submitted:
https://marc.info/?l=ceph-devel&m=156503551004608&w=2
08/06/2019
- 12:57 PM Feature #41135 (Resolved): add file capability support to kcephfs
- xfstest/093 fails:...
08/01/2019
- 01:09 PM Bug #40985: xfstest generic/451 intermittently fails
- I've been going over the nfs client code to determine why we don't see this problem there. The NFS client makes buffe...
07/31/2019
07/29/2019
- 09:53 PM Documentation #40996: Calling messenger v1 protocol legacy is misleading
- exactly, that's what confused us and it took a while to realize that port 6789 needs to be reachable in addition to p...
- 09:43 PM Documentation #40996: Calling messenger v1 protocol legacy is misleading
- ... our comments raced. Just sounds like there is confusion in that the kernel will continue to use the legacy v1 pro...
- 09:40 PM Documentation #40996: Calling messenger v1 protocol legacy is misleading
- I guess I don't understand the issue. The definition of "legacy" as per Google is "denoting or relating to software o...
- 09:37 PM Documentation #40996: Calling messenger v1 protocol legacy is misleading
- excuse me, I explained the wrong way - to be correct now:
"ceph -s" and "rbd disable feature..." uses V2
and "rbd... - 09:29 PM Documentation #40996: Calling messenger v1 protocol legacy is misleading
- Hi thanks for reply,
the claimed version is 14.2.2 (nautlius) and not a "pre-Nautilus" ceph installation.
If some... - 09:25 PM Documentation #40996: Calling messenger v1 protocol legacy is misleading
- The kernel "libceph" driver does not support the v2 protocol.
- 09:04 PM Documentation #40996: Calling messenger v1 protocol legacy is misleading
- Is there something weird going on with rbd? I imagine the example command is just invoking a kernel interface that ru...
- 01:13 PM Documentation #40996: Calling messenger v1 protocol legacy is misleading
- related github issue: https://github.com/ceph/ceph-ansible/issues/4272
- 01:10 PM Documentation #40996 (New): Calling messenger v1 protocol legacy is misleading
Ceph clients (14.2.2) still need both versions of messenger protocol (v1 and v2) in order to work
but docs pretend...
Also available in: Atom