https://tracker.ceph.com/https://tracker.ceph.com/favicon.ico2020-03-03T16:52:24ZCeph CephFS - Bug #44389: client: fuse mount will print call trace with incorrect optionshttps://tracker.ceph.com/issues/44389?journal_id=1601742020-03-03T16:52:24ZPatrick Donnellypdonnell@redhat.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/160174/diff?detail_id=164128">diff</a>)</li><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Target version</strong> set to <i>v16.0.0</i></li><li><strong>Backport</strong> set to <i>octopus,nautilus</i></li></ul> CephFS - Bug #44389: client: fuse mount will print call trace with incorrect optionshttps://tracker.ceph.com/issues/44389?journal_id=1608772020-03-12T12:31:45ZXiubo Lixiubli@redhat.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Fix Under Review</i></li></ul><p><a class="external" href="https://github.com/ceph/ceph/pull/33915">https://github.com/ceph/ceph/pull/33915</a></p> CephFS - Bug #44389: client: fuse mount will print call trace with incorrect optionshttps://tracker.ceph.com/issues/44389?journal_id=1609352020-03-13T01:31:29ZXiubo Lixiubli@redhat.com
<ul></ul><p>The objecter_finisher is already started in Client::Client(), but in the failure path when initializing and starting the Client object, we may not get a chance to call the Client::shutdown() to stop the Finisher thread, which maybe still holding the mutex lock in it. Then when destrucing the Finisher object the pthread_mutex_destroy() will fail.</p> CephFS - Bug #44389: client: fuse mount will print call trace with incorrect optionshttps://tracker.ceph.com/issues/44389?journal_id=1625302020-04-03T19:50:25ZGreg Farnumgfarnum@redhat.com
<ul><li><strong>Status</strong> changed from <i>Fix Under Review</i> to <i>Resolved</i></li></ul> CephFS - Bug #44389: client: fuse mount will print call trace with incorrect optionshttps://tracker.ceph.com/issues/44389?journal_id=1648242020-05-04T16:50:11ZPatrick Donnellypdonnell@redhat.com
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Pending Backport</i></li></ul> CephFS - Bug #44389: client: fuse mount will print call trace with incorrect optionshttps://tracker.ceph.com/issues/44389?journal_id=1654912020-05-11T14:26:14ZNathan Cutlerncutler@suse.cz
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-9 status-3 priority-4 priority-default closed" href="/issues/45495">Backport #45495</a>: octopus: client: fuse mount will print call trace with incorrect options</i> added</li></ul> CephFS - Bug #44389: client: fuse mount will print call trace with incorrect optionshttps://tracker.ceph.com/issues/44389?journal_id=1654932020-05-11T14:26:21ZNathan Cutlerncutler@suse.cz
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-9 status-3 priority-4 priority-default closed" href="/issues/45496">Backport #45496</a>: nautilus: client: fuse mount will print call trace with incorrect options</i> added</li></ul> CephFS - Bug #44389: client: fuse mount will print call trace with incorrect optionshttps://tracker.ceph.com/issues/44389?journal_id=1655932020-05-11T16:13:11ZNathan Cutlerncutler@suse.cz
<ul><li><strong>Pull request ID</strong> set to <i>33915</i></li></ul> CephFS - Bug #44389: client: fuse mount will print call trace with incorrect optionshttps://tracker.ceph.com/issues/44389?journal_id=1673332020-06-03T12:21:14ZNathan Cutlerncutler@suse.cz
<ul><li><strong>Status</strong> changed from <i>Pending Backport</i> to <i>Resolved</i></li></ul><p>While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".</p>