Home
last modified time | relevance | path

Searched hist:e548e9b93d3e565e42b938a99804114565be1f81 (Results 1 – 3 of 3) sorted by relevance

/linux/fs/ceph/
H A Dsuper.hdiff fc927cd32feca2acefd90a4ac317fa4f0a2e5955 Mon Jul 20 03:50:58 CEST 2015 Yan, Zheng <zyan@redhat.com> ceph: always re-send cap flushes when MDS recovers

commit e548e9b93d3e565e42b938a99804114565be1f81 makes the kclient
only re-send cap flush once during MDS failover. If the kclient sends
a cap flush after MDS enters reconnect stage but before MDS recovers.
The kclient will skip re-sending the same cap flush when MDS recovers.

This causes problem for newly created inode. The MDS handles cap
flushes before replaying unsafe requests, so it's possible that MDS
find corresponding inode is missing when handling cap flush. The fix
is reverting to old behaviour: always re-send when MDS recovers

Signed-off-by: Yan, Zheng <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
diff e548e9b93d3e565e42b938a99804114565be1f81 Wed Jun 10 09:17:56 CEST 2015 Yan, Zheng <zyan@redhat.com> ceph: re-send flushing caps (which are revoked) in reconnect stage

if flushing caps were revoked, we should re-send the cap flush in
client reconnect stage. This guarantees that MDS processes the cap
flush message before issuing the flushing caps to other client.

Signed-off-by: Yan, Zheng <zyan@redhat.com>
H A Dcaps.cdiff fc927cd32feca2acefd90a4ac317fa4f0a2e5955 Mon Jul 20 03:50:58 CEST 2015 Yan, Zheng <zyan@redhat.com> ceph: always re-send cap flushes when MDS recovers

commit e548e9b93d3e565e42b938a99804114565be1f81 makes the kclient
only re-send cap flush once during MDS failover. If the kclient sends
a cap flush after MDS enters reconnect stage but before MDS recovers.
The kclient will skip re-sending the same cap flush when MDS recovers.

This causes problem for newly created inode. The MDS handles cap
flushes before replaying unsafe requests, so it's possible that MDS
find corresponding inode is missing when handling cap flush. The fix
is reverting to old behaviour: always re-send when MDS recovers

Signed-off-by: Yan, Zheng <zyan@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
diff e548e9b93d3e565e42b938a99804114565be1f81 Wed Jun 10 09:17:56 CEST 2015 Yan, Zheng <zyan@redhat.com> ceph: re-send flushing caps (which are revoked) in reconnect stage

if flushing caps were revoked, we should re-send the cap flush in
client reconnect stage. This guarantees that MDS processes the cap
flush message before issuing the flushing caps to other client.

Signed-off-by: Yan, Zheng <zyan@redhat.com>
H A Dmds_client.cdiff e548e9b93d3e565e42b938a99804114565be1f81 Wed Jun 10 09:17:56 CEST 2015 Yan, Zheng <zyan@redhat.com> ceph: re-send flushing caps (which are revoked) in reconnect stage

if flushing caps were revoked, we should re-send the cap flush in
client reconnect stage. This guarantees that MDS processes the cap
flush message before issuing the flushing caps to other client.

Signed-off-by: Yan, Zheng <zyan@redhat.com>