Unable to mount btrfs filesystems spread across more than one partition with lklfuse #518

Activity

1. tavip commented on Apr 11, 2023

   

   tavip

   on Apr 11, 2023

   Member

   More actions

   This requires support for adding multiple disks. Then using the physical disk and multiple partitions should work. I’ll look into more details at this tomorrow.

   Could you please share instructions on how to get btrfs split across multiple partitions?
2. tavip

   self-assigned this

   on Apr 11, 2023
3. bqv commented on Apr 11, 2023

   

   bqv

   on Apr 11, 2023

   Author

   More actions

   Assuming you have btrfsprogs, with an existing btrfs filesystem mounted at /mnt, you can add a new device as-is with btrfs device add /dev/<blk> /mnt

   Thanks!
4. bqv commented on Jun 16, 2023

   

   bqv

   on Jun 16, 2023

   Author

   More actions

   Is there a plan for implementing this?
5. ddiss commented on May 31, 2024

   

   ddiss

   on May 31, 2024

   More actions

   One option for adding devices to an existing lklfuse process at runtime is a FUSE xattr hack, e.g.:

   setfattr -n lklfuse.dev.add -v /dev/sdX /mnt/
   

   It might then also be possible to forward BTRFS_IOC_ADD_DEV ioctls through to the underlying LKL mount via a FUSE ioctl hook.
6. MathewKing commented on Sep 17, 2024

   

   MathewKing

   on Sep 17, 2024

   More actions

   I have been experimenting with lkl and btrfs and I found that the btrfs command uses ioctl to interact with the btrfs file system. In its current state the btrfs command does not recognize a lklfuse mounted btrfs volume. I created a modified version of btrfs from here https://github.com/kdave/btrfs-progs to allow sending ioctl to the lklfuse filesystem.

   From there I discovered that lklfuse does not implement ioctl. I thought that there might be a simple way to implement .ioctl in lklfuse_ops. From what I can tell there is a complication because ioctl from fuse uses 2 pointers void *arg for ioctl data from the user and void *data for ioctl data to the user but the internal call sys_ioctl uses a single pointer and the ioctl implementation will use copy_from_user() and copy_to_user().

   I think that ioctl in lklfuse can be achieved by implementing raw_copy_from_user() and raw_copy_to_user() in arch/lkl. New lkl functions will need to be implemented to map the *arg and *data pointers together so when raw_copy_from_user is called, data is read from *arg and when raw_copy_to_user is called, data is written to *data.

   I am not an expert on fuse or the kernel so I may be missing something. I am going to try and get ioctl working in lklfuse well enough that btrfs filesystem usage works and if I do I will post a pull request.

   👍React with 👍1Reacted by Tony O

   🚀React with 🚀1Reacted by Tony O
7. MathewKing commented on Oct 23, 2024

   

   MathewKing

   on Oct 23, 2024

   More actions

   I haven't had time to look into this much recently but I want to provide a quick update.

   I did finally get ioctl to start to work with lklfuse. My initial assessment of needing 2 pointers was incorrect; only the *data pointer is needed. I haven't dug into the *arg pointer but I was able to get ioctl working without it.

   I then ran into an issue where lkl stored a file handle directly in the fh field of fuse_file_info when opening files but a pointer to lkl_dir when opening a directory. I have a very crude fix for that and I have attached that patch, 0001-Crude-ioctl-support-for-lklfuse.patch. With this patch I was able to get some btrfs commands to work on an lklfuse mounted filesystem, for example I could run btrfs fi us without errors. However when I would run btrfs fi du I would get an 'Operation not supported' error.

   I dug into this a little bit but I did not get very far. Essentially there is an ioctl command, FS_IOC_FIEMAP, that is not supported by fuse in the kernel. There has been some effort to get it supported but it hasn't seemed to go anywhere, see libfuse/libfuse#72.

   To get this to work on the btrfs-progs side I just made the following change for testing purposes.

   diff --git a/common/open-utils.c b/common/open-utils.c
   index 8490be4a..448f3154 100644
   --- a/common/open-utils.c
   +++ b/common/open-utils.c
   @@ -209,7 +209,7 @@ int btrfs_open_path(const char *path, bool read_write, bool dir_only)
                   return -errno;
           }
    
   -       if (stfs.f_type != BTRFS_SUPER_MAGIC) {
   +       if (stfs.f_type != FUSE_SUPER_MAGIC) {
                   error("not a btrfs filesystem: %s", path);
                   return -EINVAL;
           }