The problem (if that's the word) is WSL1 is expecting more from their Windows implementation of their filesystem (contrast a Real Linux user asking for Real Linux support). You could kick me back to Box on this one, but they have steadfastly refused to support linux of any kind.īoxDrive wouldn't be supporting 'Linux' in your specific scenario, which is WSL1. You can try WSL2 and see if that fares any better, as it uses a different mechanism in the WSL->Windows direction. De facto by design, because WSL does not (and practically speaking cannot) support all third-party installable filesystems. Not familiar with BoxDrive, but from your symptoms this is basically same #1954 #2163 #2999 #2896 #1962, others. See our contributing instructions for assistance. Strace of the failing command, if applicable: (If some_command is failing, then run strace -o some_command.strace -f some_command some_args, and link the contents of some_command.strace in a gist here).įor WSL launch issues, please collect detailed logs. So perhaps if Windows folks know what kind of drive protocol they are using, there might be a way to map it from WSL. You could kick me back to Box on this one, but they have steadfastly refused to support linux of any kind. I have no idea what method they are using to create the volume that appears in my C drive. \AppData\Local\Box\Box, but there aren't files there. Init: (14092) ERROR: UtilCreateProcessAndWait:360: /bin/mount failed with status 0x2000 Mount: /mnt/box: wrong fs type, bad option, bad superblock on Box, missing codepage or helper program, or other error. Ls: cannot access 'Box': Input/output error I get a permission error if I try to access the folder. What's wrong / what should be happening instead:.Trying to copy files to the new BoxDrive. Include screen shots if that helps demonstrate the problem.) What you're doing and what's happening: (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output.Your Windows build number: (Type ver at a Windows Command Prompt).Please direct all Windows crashes and security issues to Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from "C:\Windows\minidump". Important: Do not open GitHub issues for Windows crashes (BSODs) or security issues. If this is a console issue (a problem with layout, rendering, colors, etc.), please post to the console issue tracker. If you have a feature request, please post to the UserVoice.
Please fill out all the fields! Issues with missing or incomplete issue templates will be closed.
Please use the following bug reporting template to help produce issues which are actionable and reproducible, including all command-line steps necessary to induce the failure condition.
0 kommentar(er)
