crossmeta/cxfuse

Crossmeta FUSE Windows Port

cxfuse's Issues

Add s3backer to crossmeta fuse

From @archiecobbs

s3backer is a filesystem that contains a single file backed by the Amazon Simple Storage Service (Amazon S3). As a filesystem, it is very simple: it provides a single normal file having a fixed size. Underneath, the file is divided up into blocks, and the content of each block is stored in a unique Amazon S3 object. In other words, what s3backer provides is really more like an S3-backed virtual hard disk device, rather than a filesystem.

Add support for s3backer that can work with S3, Azure Blobs and Google cloud storage. This will be used with Crossmeta FUSE on Windows with NTFS file system on top of it.

s3backer: Unable to create ntfs volume on VHDX file

Unable to create NTFS volume on s3backer windows initialized as vhdx file.
The format tool fails with 0xC0000185L (STATUS_IO_DEVICE_ERROR)

1. start s3backer windows with --filename file.vhdx
2. Use qemu-img windows port and create VHDX file
   qemu-img create -f vhdx v:\mnt\file.vhdx 50G
3. Used Windows disk management and Attach VHD file with v:\mnt\file.vhdx
4. Initialize Disk OK
5. Create Simple Volume and do quick format NTFS
   The above step is unsuccessful due to IO errors

Lost fork support for busybox in newer windows builds

With newer windows builds after 14393 busybox fork is not working as expected. The forked process would silently exit and ash functionality is broken. The rest of the features are working as expected.

The fork functionality is dependent on RtlCloneUserProcess and we don't know how to use it with the newer builds. On other hand with Windows 2019 (17763) the WSL bash can recognize crossmeta namespace.

sshfs: update _plink.exe

The plink used by sshfs in Crossmeta is very old and needs to be updated.

plink: Unidentified build, May 1 2012 22:11:03

Error 577 when trying to start cxvfs service

Hello,

During installation, a window appears with errors "VerInstallFile retval 0x800". I think this is due to the fact that the V: drive is not created.
I execute the command "sc query cxvfs". The conclusion says that the service is stopped. When I execute "net start cxvfs", I get an error 577:
"Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source."

I tried to disable driver signature verification through group policies, also specified the parameter through bcdedit - it did not help.
My configuration: Windows 10 Pro Workstation, Crossmeta FUSE 2.0.3

Feature Request

Please support Crossmeta like this, can access any filesystems(Mac, Linux,...) throught user-friendly interface with full access(write, read volume). Sorry for my English.

https://github.com/matt-wu/Ext3Fsd, or
https://www.paragon-software.com/us/home/linuxfs-windows/

Add "comparison" to WinFsp and Dokany

How does this compare e.g. to https://github.com/billziss-gh/winfsp or Dokany? See also winfsp/winfsp#19 .

I mean general quality differences, speed differences, maintenance/deployment constraints/requirements, licenses & prices, caveats or (architectural) shortcomings, goals & non-goals, future directions & support, ...

Drive letter

Hello,
How can I change a drive letter other than V:

Error during setup: VerInstallFile retval 0x800

When installing crossmeta-fuse-2_0_3 on Windows 10, the setup program presents the following error:

---------------------------
setup
---------------------------
Setup encountered the following errors.
VerInstallFile: busybox.exe: retval: 0x800

VerInstallFile: df.exe: retval: 0x800

VerInstallFile: dmesg.exe: retval: 0x800

VerInstallFile: fsck.exe: retval: 0x800

VerInstallFile: hexdump.exe: retval: 0x800

VerInstallFile: id.exe: retval: 0x800

VerInstallFile: losetup.exe: retval: 0x800

VerInstallFile: mount.exe: retval: 0x800

VerInstallFile: newfs.exe: retval: 0x800

VerInstallFile: nfsstat.exe: retval: 0x800

VerInstallFile: pwd_mkdb.exe: retval: 0x800

VerInstallFile: pw.exe: retval: 0x800

VerInstallFile: rpcinfo.exe: retval: 0x800

VerInstallFile: showmount.exe: retval: 0x800

VerInstallFile: sysctl.exe: retval: 0x800

VerInstallFile: umount.exe: retval: 0x800

VerInstallFile: xargs.exe: retval: 0x800

VerInstallFile: ypcat.exe: retval: 0x800

VerInstallFile: ypmatch.exe: retval: 0x800

VerInstallFile: sash.exe: retval: 0x800

VerInstallFile: mke2fs.exe: retval: 0x800

VerInstallFile: e2fsck.exe: retval: 0x800

VerInstallFile: dumpe2fs.exe: retval: 0x800

VerInstallFile: xfs_mkfs.exe: retval: 0x800

VerInstallFile: xfs_repair.exe: retval: 0x800

VerInstallFile: newfs_hfs.exe: retval: 0x800

VerInstallFile: fsck_hfs.exe: retval: 0x800

VerInstallFile: postinstall.sh: retval: 0x800

VerInstallFile: postinstall.cmd: retval: 0x800

VerInstallFile: cmd.exe: retval: 0x800

VerInstallFile: group: retval: 0x800

VerInstallFile: fstab: retval: 0x800

VerInstallFile: license.txt: retval: 0x800

VerInstallFile: networks: retval: 0x800

VerInstallFile: master.passwd: retval: 0x800

VerInstallFile: profile: retval: 0x800

VerInstallFile: rpc: retval: 0x800

VerInstallFile: exec: retval: 0x800

VerInstallFile: libdb.dll: retval: 0x800

VerInstallFile: rpclib40.dll: retval: 0x800

VerInstallFile: cxfuse.dll: retval: 0x800


Click Yes to ignore error and proceed with installation or click No to terminate setup program.
---------------------------
Yes   No   
---------------------------

sshfs: low performance with plink.exe for large file transfers

Since crossmeta sshfs is using plink.exe for the sftp transfers it can be notoriously slow for large file transfers. This appears to be plink.exe related as in @FauxFaux/PuTTYTray#274

Try updating plink.exe #3 or explore using win32-openssh sftp

How to mount XFS?

I had installed crossmeta-fuse-2_0_3 and relogin. My explorer have V volume.
But when I try mount -t xfs /dev/da1s3 /home, it looks nothing happend. And /home is empty still.

Do you can help mount xfs on windows10 64 bits?