Date: Tue, 14 Sep 2010 13:00:19 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Juergen Lock <nox@jelal.kn-bremen.de> Cc: freebsd-emulation@freebsd.org Subject: Re: CFT: vdfuse port (was: Re: Mounting VirtualBox vdi files [SEC=UNCLASSIFIED]) Message-ID: <alpine.BSF.2.00.1009141248370.54151@wonkity.com> In-Reply-To: <20100913211401.GA49701@triton8.kn-bremen.de> References: <alpine.BSF.2.00.1007052053090.9243@wonkity.com> <20100706032057.GA15827@stlux503.dsto.defence.gov.au> <201009022024.o82KOVni007042@triton8.kn-bremen.de> <alpine.BSF.2.00.1009081918340.25377@wonkity.com> <20100911184519.GA2100@triton8.kn-bremen.de> <alpine.BSF.2.00.1009111302590.62686@wonkity.com> <20100913211401.GA49701@triton8.kn-bremen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 13 Sep 2010, Juergen Lock wrote: >> >> Dumping the partitions of that FreeBSD system worked just now. Not what >> I'd call a thorough test, but it did read everything in the filesystem >> without problems. > > Ok that sounds promising... Someone want to do more tests or should I > just commit the port? :) Testing writes has not been as successful. fdisk and bsdlabel work fine, as does writing individual files. But trying to restore onto a vdfuse/mdconfig partition just goes away. The machine is idle, restore waits in wdrain, and further access to that device does not respond. I think I saw fuse in a fuse_msg state, but can't verify that now. That was all before applying the fusefs-kmod patch; now other processes also stop responding. In any case, I'd rather have a port that is not 100% than no port at all. Announcing possible problems in the pkg-message would be appropriate.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1009141248370.54151>