Struct OverlayFs

pub struct OverlayFs { /* private fields */ }

Implementations

impl OverlayFs

pub fn new( upper: Option<Arc<PassthroughFs>>, lowers: Vec<Arc<PassthroughFs>>, params: Config, root_inode: u64, ) -> Result<Self>

pub fn root_inode(&self) -> Inode

pub async fn push_layer(&mut self, layer: Arc<PassthroughFs>) -> Result<()>

Add a file layer and stack and merge the previous file layers.

pub async fn import(&self) -> Result<()>

pub async fn extend_inode_alloc(&self, key: u64)

Trait Implementations

impl Filesystem for OverlayFs

type DirEntryStream<'a> = Iter<IntoIter<Result<DirectoryEntry, Errno>>> where Self: 'a

dir entry stream given by readdir.

type DirEntryPlusStream<'a> = Iter<IntoIter<Result<DirectoryEntryPlus, Errno>>> where Self: 'a

dir entry stream given by readdir.

async fn init(&self, _req: Request) -> Result<ReplyInit>

initialize filesystem. Called before any other filesystem method.

async fn destroy(&self, _req: Request)

clean up filesystem. Called on filesystem exit which is fuseblk, in normal fuse filesystem, kernel may call forget for root. There is some discuss for this https://github.com/bazil/fuse/issues/82#issuecomment-88126886, https://sourceforge.net/p/fuse/mailman/message/31995737/

async fn lookup( &self, req: Request, parent: Inode, name: &OsStr, ) -> Result<ReplyEntry>

look up a directory entry by name and get its attributes.

async fn forget(&self, _req: Request, inode: Inode, nlookup: u64)

forget an inode. The nlookup parameter indicates the number of lookups previously performed on this inode. If the filesystem implements inode lifetimes, it is recommended that inodes acquire a single reference on each lookup, and lose nlookup references on each forget. The filesystem may ignore forget calls, if the inodes don’t need to have a limited lifetime. On unmount it is not guaranteed, that all referenced inodes will receive a forget message. When filesystem is normal(not fuseblk) and unmounting, kernel may send forget request for root and this library will stop session after call forget. There is some discussion for this https://github.com/bazil/fuse/issues/82#issuecomment-88126886, https://sourceforge.net/p/fuse/mailman/message/31995737/

async fn getattr( &self, req: Request, inode: Inode, fh: Option<u64>, flags: u32, ) -> Result<ReplyAttr>

get file attributes. If fh is None, means fh is not set.

async fn setattr( &self, req: Request, inode: Inode, fh: Option<u64>, set_attr: SetAttr, ) -> Result<ReplyAttr>

set file attributes. If fh is None, means fh is not set.

async fn readlink(&self, req: Request, inode: Inode) -> Result<ReplyData>

read symbolic link.

async fn symlink( &self, req: Request, parent: Inode, name: &OsStr, link: &OsStr, ) -> Result<ReplyEntry>

create a symbolic link.

async fn mknod( &self, req: Request, parent: Inode, name: &OsStr, mode: u32, rdev: u32, ) -> Result<ReplyEntry>

create file node. Create a regular file, character device, block device, fifo or socket node. When creating file, most cases user only need to implement create.

async fn mkdir( &self, req: Request, parent: Inode, name: &OsStr, mode: u32, umask: u32, ) -> Result<ReplyEntry>

create a directory.

async fn unlink(&self, req: Request, parent: Inode, name: &OsStr) -> Result<()>

remove a file.

async fn rmdir(&self, req: Request, parent: Inode, name: &OsStr) -> Result<()>

remove a directory.

async fn rename( &self, req: Request, parent: Inode, name: &OsStr, new_parent: Inode, new_name: &OsStr, ) -> Result<()>

rename a file or directory.

async fn link( &self, req: Request, inode: Inode, new_parent: Inode, new_name: &OsStr, ) -> Result<ReplyEntry>

create a hard link.

async fn open( &self, req: Request, inode: Inode, flags: u32, ) -> Result<ReplyOpen>

open a file. Open flags (with the exception of O_CREAT, O_EXCL and O_NOCTTY) are available in flags. Filesystem may store an arbitrary file handle (pointer, index, etc) in fh, and use this in other all other file operations (read, write, flush, release, fsync). Filesystem may also implement stateless file I/O and not store anything in fh. There are also some flags (direct_io, keep_cache) which the filesystem may set, to change the way the file is opened. A filesystem need not implement this method if it sets [MountOptions::no_open_support][crate::MountOptions::no_open_support] and if the kernel supports FUSE_NO_OPEN_SUPPORT.

Notes:

See fuse_file_info structure in fuse_common.h for more details.

async fn read( &self, req: Request, inode: Inode, fh: u64, offset: u64, size: u32, ) -> Result<ReplyData>

read data. Read should send exactly the number of bytes requested except on EOF or error, otherwise the rest of the data will be substituted with zeroes. An exception to this is when the file has been opened in direct_io mode, in which case the return value of the read system call will reflect the return value of this operation. fh will contain the value set by the open method, or will be undefined if the open method didn’t set any value.

async fn write( &self, req: Request, inode: Inode, fh: u64, offset: u64, data: &[u8], write_flags: u32, flags: u32, ) -> Result<ReplyWrite>

write data. Write should return exactly the number of bytes requested except on error. An exception to this is when the file has been opened in direct_io mode, in which case the return value of the write system call will reflect the return value of this operation. fh will contain the value set by the open method, or will be undefined if the open method didn’t set any value. When write_flags contains FUSE_WRITE_CACHE, means the write operation is a delay write.

async fn statfs(&self, req: Request, inode: Inode) -> Result<ReplyStatFs>

get filesystem statistics.

async fn release( &self, req: Request, _inode: Inode, fh: u64, flags: u32, lock_owner: u64, flush: bool, ) -> Result<()>

release an open file. Release is called when there are no more references to an open file: all file descriptors are closed and all memory mappings are unmapped. For every open call there will be exactly one release call. The filesystem may reply with an error, but error values are not returned to close() or munmap() which triggered the release. fh will contain the value set by the open method, or will be undefined if the open method didn’t set any value. flags will contain the same flags as for open. flush means flush the data or not when closing file.

async fn fsync( &self, req: Request, inode: Inode, fh: u64, datasync: bool, ) -> Result<()>

synchronize file contents. If the datasync is true, then only the user data should be flushed, not the metadata.

async fn setxattr( &self, req: Request, inode: Inode, name: &OsStr, value: &[u8], flags: u32, position: u32, ) -> Result<()>

set an extended attribute.

async fn getxattr( &self, req: Request, inode: Inode, name: &OsStr, size: u32, ) -> Result<ReplyXAttr>

Get an extended attribute. If size is too small, return Err<ERANGE>. Otherwise, use ReplyXAttr::Data to send the attribute data, or return an error.

async fn listxattr( &self, req: Request, inode: Inode, size: u32, ) -> Result<ReplyXAttr>

List extended attribute names.

If size is too small, return Err<ERANGE>. Otherwise, use ReplyXAttr::Data to send the attribute list, or return an error.

async fn removexattr( &self, req: Request, inode: Inode, name: &OsStr, ) -> Result<()>

remove an extended attribute.

async fn flush( &self, req: Request, inode: Inode, fh: u64, lock_owner: u64, ) -> Result<()>

flush method. This is called on each close() of the opened file. Since file descriptors can be duplicated (dup, dup2, fork), for one open call there may be many flush calls. Filesystems shouldn’t assume that flush will always be called after some writes, or that if will be called at all. fh will contain the value set by the open method, or will be undefined if the open method didn’t set any value.

Notes:

the name of the method is misleading, since (unlike fsync) the filesystem is not forced to flush pending writes. One reason to flush data, is if the filesystem wants to return write errors. If the filesystem supports file locking operations ([setlk][Filesystem::setlk], [getlk][Filesystem::getlk]) it should remove all locks belonging to lock_owner.

async fn opendir( &self, req: Request, inode: Inode, flags: u32, ) -> Result<ReplyOpen>

open a directory. Filesystem may store an arbitrary file handle (pointer, index, etc) in fh, and use this in other all other directory stream operations (readdir, releasedir, fsyncdir). Filesystem may also implement stateless directory I/O and not store anything in fh. A file system need not implement this method if it sets [MountOptions::no_open_dir_support][crate::MountOptions::no_open_dir_support] and if the kernel supports FUSE_NO_OPENDIR_SUPPORT.

async fn readdir( &self, req: Request, parent: Inode, fh: u64, offset: i64, ) -> Result<ReplyDirectory<Self::DirEntryStream<'_>>>

read directory. offset is used to track the offset of the directory entries. fh will contain the value set by the opendir method, or will be undefined if the opendir method didn’t set any value.

async fn readdirplus( &self, req: Request, parent: Inode, fh: u64, offset: u64, _lock_owner: u64, ) -> Result<ReplyDirectoryPlus<Self::DirEntryPlusStream<'_>>>

read directory entries, but with their attribute, like readdir

• lookup at the same time.

async fn releasedir( &self, _req: Request, _inode: Inode, fh: u64, _flags: u32, ) -> Result<()>

release an open directory. For every opendir call there will be exactly one releasedir call. fh will contain the value set by the opendir method, or will be undefined if the opendir method didn’t set any value.

async fn fsyncdir( &self, req: Request, inode: Inode, fh: u64, datasync: bool, ) -> Result<()>

synchronize directory contents. If the datasync is true, then only the directory contents should be flushed, not the metadata. fh will contain the value set by the opendir method, or will be undefined if the opendir method didn’t set any value.

async fn access(&self, req: Request, inode: Inode, mask: u32) -> Result<()>

check file access permissions. This will be called for the access() system call. If the default_permissions mount option is given, this method is not be called. This method is not called under Linux kernel versions 2.4.x.

async fn create( &self, req: Request, parent: Inode, name: &OsStr, mode: u32, flags: u32, ) -> Result<ReplyCreated>

create and open a file. If the file does not exist, first create it with the specified mode, and then open it. Open flags (with the exception of O_NOCTTY) are available in flags. Filesystem may store an arbitrary file handle (pointer, index, etc) in fh, and use this in other all other file operations (read, write, flush, release, fsync). There are also some flags (direct_io, keep_cache) which the filesystem may set, to change the way the file is opened. If this method is not implemented or under Linux kernel versions earlier than 2.6.15, the mknod and open methods will be called instead.

Notes:

See fuse_file_info structure in fuse_common.h for more details.

async fn batch_forget(&self, _req: Request, inodes: &[(Inode, u64)])

forget more than one inode. This is a batch version forget

async fn fallocate( &self, req: Request, inode: Inode, fh: u64, offset: u64, length: u64, mode: u32, ) -> Result<()>

allocate space for an open file. This function ensures that required space is allocated for specified file.

Notes:

more information about fallocate, please see man 2 fallocate

async fn lseek( &self, req: Request, inode: Inode, fh: u64, offset: u64, whence: u32, ) -> Result<ReplyLSeek>

find next data or hole after the specified offset.

async fn interrupt(&self, _req: Request, _unique: u64) -> Result<()>

handle interrupt. When a operation is interrupted, an interrupt request will send to fuse server with the unique id of the operation.

fn bmap( &self, req: Request, inode: u64, blocksize: u32, idx: u64, ) -> impl Future<Output = Result<ReplyBmap, Errno>> + Send

map block index within file to block index within device.

fn poll( &self, req: Request, inode: u64, fh: u64, kh: Option<u64>, flags: u32, events: u32, notify: &Notify, ) -> impl Future<Output = Result<ReplyPoll, Errno>> + Send

poll for IO readiness events.

fn notify_reply( &self, req: Request, inode: u64, offset: u64, data: Bytes, ) -> impl Future<Output = Result<(), Errno>> + Send

receive notify reply from kernel.

fn rename2( &self, req: Request, parent: u64, name: &OsStr, new_parent: u64, new_name: &OsStr, flags: u32, ) -> impl Future<Output = Result<(), Errno>> + Send

rename a file or directory with flags.

fn copy_file_range( &self, req: Request, inode: u64, fh_in: u64, off_in: u64, inode_out: u64, fh_out: u64, off_out: u64, length: u64, flags: u64, ) -> impl Future<Output = Result<ReplyCopyFileRange, Errno>> + Send

copy a range of data from one file to another. This can improve performance because it reduce data copy: in normal, data will copy from FUSE server to kernel, then to user-space, then to kernel, finally send back to FUSE server. By implement this method, data will only copy in FUSE server internal.