>s_blocksize_bits;
> @@ -712,7 +711,6 @@ int cachefiles_read_or_alloc_pages(struct
> fscache_retrieval *op,
>
> inode = d_backing_inode(object->backer);
> ASSERT(S_ISREG(inode->i_mode));
> - ASSERT(inode->i_mapping->a_ops->readpages);
>
>
Corcodel Marian wrote:
> Hi on function fscache_object_destroyed may run with variable undefined when
> in not set CONFIG_FSCACHE
>
> +void fscache_object_destroyed(struct fscache_cache *cache)
> +{
> +#ifdef CONFIG_FSCACHE
> + if (atomic_dec_and_test(&cache->object_count))
> +
I encountered this bug on a Debian Stretch system with an NFS 4 mount
and cachefilesd 0.10.9. NFS 4 file systems are mounted like this from
fstab:
master.cluster.ai:/home /home nfs4
_netdev,fsc,noatime,vers=4.2,nodev,nosuid 0 0
master.cluster.ai:/cluster /srv/clusternfs4
Hi!
> > * Can the kernel part of CODA can be used for this?
>
> Not if you want to intercept and redirect every single read and write
> call. That's a whole other can of worms, and I'd advise you to let the
> userspace cachemanager to act as an NFS daemon. In my opinion, the Coda
> kernel module
Jan Harkes wrote:
: > Every file on the front filesystem (NFS or so) volume will be cached
: > in two local files by cachefsd: The first one would contain the (parts of)
: > real file content, and the second one would contain file's metadata and the
: > bitmap of valid blocks (or pages) of the
odule, implementing the filesystem of the type "cachefs"
> > and a character device /dev/cachefs
> > - user-space daemon, which would communicate with the kernel
> > over /dev/cachefs and which would manage the backing store
> > in a given direct
Jan Kasprzak writes:
> Another goal is to use the Linux filesystem
> as a backing store (as opposed to the block device or single large file
> used by CODA).
...
> - kernel module, implementing the filesystem of the type "cachefs"
> an
On Thu, Jun 07, 2001 at 01:37:50PM +0200, Jan Kasprzak wrote:
> The goal is to speed-up reading of potentially slow filesystems
> (NFS, maybe even CD-based ones) by the local on-disk cache in the same way
> IRIX or Solaris CacheFS works. I would expect this to be used on clus
Hello,
a friend of mine has developed the CacheFS for Linux. His work
is a prototype read-only implementation for Linux 2.2.11 or so. I am
thinking about adapting (or partly rewriting) his work for Linux 2.4.
But before I'll start working, I'd like to ask you for comme
9 matches
Mail list logo
