Re: how client handle the errors with OSD and MDS?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This is very good information. Thanks!

Ming


On Tue, Jun 26, 2012 at 1:46 PM, Sage Weil <sage@xxxxxxxxxxx> wrote:
> On Tue, 26 Jun 2012, ming zhang wrote:
>> Hi All
>>
>> I am trying to read the code to understand this.
>>
>> A scenario like this.
>>
>> client opens the file and finishes the write with OSD. But for some
>> reason Client could not contact MDS and fails to update MDS. What will
>> client do now in order to maintain the rightness of metadata in MDS?
>>
>> Wonder which code this error handling is implemented?
>
> When the client session times out, the MDS will probe the file objects to
> recover the file size and mtime.  The NEEDSRECOVER flag gets set by
> Locker::revoke_stale_caps() on those files, and they are queued via
> MDCache::queue_file_recover().  You should be able to pick up the trail
> from there.
>
> sage
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux