Project

General

Profile

Bug #38597

fs: "log [WRN] : failed to reconnect caps for missing inodes"

Added by Patrick Donnelly about 5 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
-
Target version:
% Done:

0%

Source:
Q/A
Tags:
Backport:
mimic
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Client, MDS
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

2019-03-03 10:11:45.105 7f54d004e700 10 mds.0.cache  unlisting unwanted/capless inode [inode 0x1000000db92 [...27d,head] /client.0/tmp/linux-2.6.33/net/dccp/ccids/lib/ auth v14 pv26 ap=2 dirtyparent f(v0 m2019-03-03 10:11:21.196966 1=1+0)->f(v0 m2019-03-03 10:11:21.196966 1=1+0) n(v0 rc2019-03-03 10:11:21.196966 2=1+1)->n(v1 rc2019-03-03 10:11:21.200848 b5652 2=1+1) (iauth sync r=1) (isnap sync r=1) (inest sync->lock w=1 flushing) (ifile excl w=1) (iversion lock) caps={4710=pAsLsXsFsx/-@0},l=4710 | dirtyscattered=1 lock=4 dirfrag=1 caps=1 dirtyparent=1 dirty=1 waiter=1 authpin=1 0x5e76700]
2019-03-03 10:11:45.105 7f54d004e700 10 mds.0.cache  unlisting unwanted/capless inode [inode 0x1000000db93 [27d,head] /client.0/tmp/linux-2.6.33/net/dccp/ccids/lib/loss_interval.c auth v2 pv6 ap=3 dirtyparent s=0 n(v0 1=1+0)->n(v0 rc2019-03-03 10:11:21.200848 b5652 1=1+0) (ifile excl->lock w=1) (iversion lock) cr={4710=0-4194304@27c} caps={4710=pAsLsXsFc/pAsLsXsFsc/-@1} | ptrwaiter=3 lock=1 caps=1 dirtyrstat=0 dirtyparent=1 dirty=1 waiter=1 authpin=1 0x468fc00]
2019-03-03 10:11:45.105 7f54d004e700 10 mds.0.cache export_remaining_imported_caps
2019-03-03 10:11:45.105 7f54d004e700 10 mds.0.166 send_message_client_counted client.4710 seq 1278 client_caps(export ino 0x1000000db94 0 seq 0 caps=- dirty=- wanted=- follows 0 size 0/0 mtime 0.000000) v11
2019-03-03 10:11:45.105 7f54d004e700  1 -- [v2:172.21.15.63:6832/2903972050,v1:172.21.15.63:6833/2903972050] --> 172.21.15.156:0/2501445370 -- client_caps(export ino 0x1000000db94 0 seq 0 caps=- dirty=- wanted=- follows 0 size 0/0 mtime 0.000000) v11 -- 0x4cb5800 con 0x1cc0480
2019-03-03 10:11:45.105 7f54d004e700  0 log_channel(cluster) log [WRN] : failed to reconnect caps for missing inodes:
2019-03-03 10:11:45.105 7f54d004e700  0 log_channel(cluster) log [WRN] :  ino 0x1000000db94

From:

cat /ceph/teuthology-archive/pdonnell-2019-03-02_00:35:27-fs-wip-pdonnell-testing-20190301.150213-distro-basic-smithi/3655115/remote/smithi063/log/ceph-mds.b.log.2.gz | zgrep -E '^2019-03-03 10:11'

Related issues

Related to CephFS - Bug #18461: failed to reconnect caps during snapshot tests Resolved 01/09/2017
Copied to CephFS - Backport #38643: mimic: fs: "log [WRN] : failed to reconnect caps for missing inodes" Resolved

History

#1 Updated by Patrick Donnelly about 5 years ago

  • Related to Bug #18461: failed to reconnect caps during snapshot tests added

#2 Updated by Patrick Donnelly about 5 years ago

Adding tag to #18461 in case they're related. Feel free to disconnect if they're not Zheng.

#3 Updated by Zheng Yan about 5 years ago

  • Status changed from 12 to Fix Under Review
  • Pull request ID set to 26781

#4 Updated by Patrick Donnelly about 5 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport changed from mimic to mimic,luminous

#6 Updated by Nathan Cutler about 5 years ago

  • Copied to Backport #38643: mimic: fs: "log [WRN] : failed to reconnect caps for missing inodes" added

#7 Updated by Zheng Yan about 5 years ago

  • Backport changed from mimic,luminous to mimic

luminous does not need backport

#8 Updated by Nathan Cutler about 4 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Also available in: Atom PDF