leoliulei
leoliulei
这个cephFS 可以通过分布式锁主动通知缓存失效的
> > ```go > > if z.SinglePool() { > > idx := z.getAvailablePoolIdx(ctx, bucket, object, data.Size()) > > if idx < 0 { > > return ObjectInfo{}, toObjectErr(errDiskFull) > >...
> The simplest way is indeed this, but we also fixed a BUG in the case of multiple pools, that is, multiple versions of files will not be restricted, just...
@vitalif Please kindly help to take a look.
Yes, in most cases, it meets the requirements. Our application usually accesses a large file in a single-threaded manner. I've found that no matter how I adjust the parameters of...
Your test result looks really good. May I ask about your test environment and your mounting parameters?
MetaEvictor: access some file cause panic when evict inodes which are still referenced by the kernel
I think the `InvalidateEntry` method of FUSE should be called when evicting an inode, and then use the `forgetInode` method to release the reference. The inode should only be deleted...
MetaEvictor: access some file cause panic when evict inodes which are still referenced by the kernel
> Hi, currently MetaEvictor only forgets expired entries. I researched FUSE behaviour during implementation and it turns out that the correct way is to forget **expired** entries **without** opened file...
MetaEvictor: access some file cause panic when evict inodes which are still referenced by the kernel
I'm using Linux 5.4 kernel here. After metadata eviction occurs (you need to wait for 60 seconds), will it panic if you access again according to my reproduction steps?