search for: nbdfuse

Displaying 11 results from an estimated 11 matches for "nbdfuse".

2019 Oct 12
3
[PATCH libnbd] nbdfuse: New tool to present a network block device in a FUSE filesystem.
This program allows you to turn a network block device source into a FUSE filesystem containing a virtual file: $ nbdkit memory 128M $ mkdir mp $ nbdfuse mp/ramdisk nbd://localhost & $ ls -l mp total 0 -rw-rw-rw-. 1 rjones rjones 134217728 Oct 12 15:09 ramdisk $ dd if=/dev/urandom bs=1M count=128 of=mp/ramdisk conv=notrunc,nocreat 128+0 records in 128+0 records out 134217728 bytes (134 MB, 128 MiB) copied, 3.10171 s, 43.3 MB/s $...
2019 Oct 14
0
Re: [PATCH libnbd] nbdfuse: New tool to present a network block device in a FUSE filesystem.
On 10/12/19 9:21 AM, Richard W.M. Jones wrote: > This program allows you to turn a network block device source into a > FUSE filesystem containing a virtual file: > > $ nbdkit memory 128M > $ mkdir mp > $ nbdfuse mp/ramdisk nbd://localhost & > $ ls -l mp > total 0 > -rw-rw-rw-. 1 rjones rjones 134217728 Oct 12 15:09 ramdisk > $ dd if=/dev/urandom bs=1M count=128 of=mp/ramdisk conv=notrunc,nocreat > 128+0 records in > 128+0 records out > 134217728 bytes (134 MB,...
2019 Oct 18
0
[PATCH libnbd 2/2] api: Add support for AF_VSOCK.
...For example: nbd_connect_vsock (nbd, 2, 10809); There is no test of this feature because it only works between guest and host. You cannot start a server and client on the host and talk between them, which is what we'd need to write a sane test. --- configure.ac | 2 ++ fuse/nbdfuse.c | 26 +++++++++++++++++++ fuse/nbdfuse.pod | 8 ++++++ generator/generator | 51 ++++++++++++++++++++++++++++++++++++-- generator/states-connect.c | 22 ++++++++++++++++ lib/connect.c | 20 +++++++++++++++ lib/internal.h | 3 +++ 7 files cha...
2019 Oct 18
5
[PATCH libnbd 0/2] api: Add support for AF_VSOCK.
...stance which listens on a virtio-vsock socket: $ ./nbdkit -fv --vsock memory 1G ... nbdkit: debug: bound to vsock 2:10809 On the guest side you can then use libnbd to connect to the server: $ ./run nbdsh -c 'h.connect_vsock(2, 10809)' -c 'print(h.get_size())' 1073741824 $ ./run nbdfuse mp --vsock 2 10809 & $ ll mp/ total 0 -rw-rw-rw-. 1 rjones rjones 1073741824 Oct 18 16:23 nbd $ dd if=/dev/random of=mp/nbd bs=1024 count=100 conv=notrunc,nocreat dd: warning: partial read (84 bytes); suggest iflag=fullblock 0+100 records in 0+100 records out 6851 bytes (6.9 kB, 6.7 KiB) copied...
2023 Apr 14
1
[libnbd PATCH 1/4] copy: rename (LONG|SHORT)_OPTIONS to (LONG|SHORT)_OPTIONS_OPTION
...printf ("-%c\n", short_options[i]); > > Assuming (from the cover message) that the same will be done later for > nbdinfo, fuse etc then ACK. Hmm. I didn't intend to do that. It seems that the following further files use the _OPTION suffix: dump/dump.c fuse/nbdfuse.c info/main.c ublk/nbdublk.c >From these, "dump/dump.c" and "info/main.c" don't exceed 80 chars, so I didn't plan to modify them at all. "fuse/nbdfuse.c" and "ublk/nbdublk.c" need wrapping, but not in their option tables. Renaming the options...
2023 Apr 14
1
[libnbd PATCH 1/4] copy: rename (LONG|SHORT)_OPTIONS to (LONG|SHORT)_OPTIONS_OPTION
On Fri, Apr 14, 2023 at 09:59:53AM +0200, Laszlo Ersek wrote: > Two of the enum constants that denote command line options are > inconsistently named with the rest: all identifiers should be > <purpose>_OPTION, but LONG_OPTIONS and SHORT_OPTIONS (which are supposed > to list the long and short options) don't conform. Rename them. > > Bugzilla:
2023 Aug 11
2
[libnbd PATCH] golang: Bump minimum Go version to 1.17
...ret[i] = uint32(item) + } return ret } "; diff --git a/README.md b/README.md index c7166613..8524038e 100644 --- a/README.md +++ b/README.md @@ -105,7 +105,7 @@ ## Building from source * Python >= 3.3 to build the Python 3 bindings and NBD shell (nbdsh). * FUSE 3 to build the nbdfuse program. * Linux >= 6.0 and ublksrv library to build nbdublk program. -* go and cgo, for compiling the golang bindings and tests. +* go and cgo >= 1.17, for compiling the golang bindings and tests. * bash-completion >= 1.99 for tab completion. Optional, only needed to run the test suit...
2019 Nov 08
0
Planning for libnbd 1.2
...in RHEL AV 8.2 and CentOS 8.2 or 8.3. It would be nice to get some of the new features added upstream since 1.0 was released, such as: - fast zeroing - ability to negotiate SRs, handshake flags - connect to systemd socket activated servers like qemu-nbd - vsock support - NBD URI filtering - nbdfuse - much improved documentation - reproducible builds Upstream-only changes, but still useful: - fuzzing support - common nbd-protocol.h - wider test coverage, particularly TLS interop - more examples So I think in the next week or two we could do a libnbd 1.2 (stable) release. The main tas...
2019 Nov 14
1
ANNOUNCE: libnbd 1.2 & nbdkit 1.16 - high performance NBD client and server
...ted(3) Did we actually negotiate a TLS connection? nbd_set_uri_allow_local_file(3) nbd_set_uri_allow_tls(3) nbd_set_uri_allow_transports(3) These can be used to filter NBD URIs before calling nbd_connect_uri(3). New features New tool nbdfuse(1) lets you create a loop-mounted file backed by an NBD server without needing root. "AF_VSOCK" is now a supported protocol (thanks Stefan Hajnoczi and Stefano Garzarella). Support for the "FAST_ZERO" flag (Eric Blake). Allow disabling certa...
2019 Oct 18
2
[PATCH nbdkit] Add support for AF_VSOCK.
...stance which listens on a virtio-vsock socket: $ ./nbdkit -fv --vsock memory 1G ... nbdkit: debug: bound to vsock 2:10809 On the guest side you can then use libnbd to connect to the server: $ ./run nbdsh -c 'h.connect_vsock(2, 10809)' -c 'print(h.get_size())' 1073741824 $ ./run nbdfuse mp --vsock 2 10809 & $ ll mp/ total 0 -rw-rw-rw-. 1 rjones rjones 1073741824 Oct 18 16:23 nbd $ dd if=/dev/random of=mp/nbd bs=1024 count=100 conv=notrunc,nocreat dd: warning: partial read (84 bytes); suggest iflag=fullblock 0+100 records in 0+100 records out 6851 bytes (6.9 kB, 6.7 KiB) copied...
2020 Jan 22
3
[PATCH libnbd] PROPOSAL Add nbdcp (NBD copying) tool.
This is a proposal for an NBD to/from file copying tool (not actually written). Obviously this would duplicate functionality which is already available in qemu-img convert. The reasons for writing this tool would be: - to produce a tool which is very focused on the specific needs of virt-v2v and similar migration scenarios - to have a small tool with minimal dependencies - fix some of