similar to: mkfs.ext2 succeeds despite nbd write errors?

On Sat, Nov 07, 2015 at 12:21:29AM -0600, Jason Pepas wrote: > Hi, > > So I've been hacking together an nbdkit plugin (similar to the "file" > plugin, but it splits the file up into chunks): > https://github.com/pepaslabs/nbdkit-chunks-plugin > > I got it to the point of being a working prototype. Then I threw it > onto a raspberry pi, which it turns out

On Sat, Nov 7, 2015 at 5:03 AM, Richard W.M. Jones <rjones@redhat.com> wrote: > How about 'strace mkfs.ext2 ..' and see if any system calls are > returning errors. That would show you whether nbd-client is throwing > errors away, or whether mkfs is getting the errors and ignoring them > (seems pretty unlikely, but you never know). > > After that, it'd be down

[Adding linux-ext4 mailing list. The original bug report is here: https://www.redhat.com/archives/libguestfs/2015-November/msg00078.html ] On Sat, Nov 07, 2015 at 01:22:45PM -0600, Jason Pepas wrote: > On Sat, Nov 7, 2015 at 5:03 AM, Richard W.M. Jones <rjones@redhat.com> wrote: > > How about 'strace mkfs.ext2 ..' and see if any system calls are > > returning errors.

On Sat, Nov 7, 2015 at 3:02 PM, Richard W.M. Jones <rjones@redhat.com> wrote: >> I'm not sure where to start with hunting down why mkfs's pwrite() >> calls aren't failing. I'd look to the kernel source for that? > > It looks like it's really an e2fsprogs problem, not a kernel problem. > That's pretty surprising - I wasn't expecting it. I

Hi All, I am unable to figure out the issue here, when I try to create a filesystem (ext4) on a virtual disk using qemu-nbd. This happens intermittently. Following is the sequence of commands:- $> qemu-img create -f qcow2 test.qcow2 30G $> qemu-nbd --connect=/dev/nbd0 test.qcow2 $> *mkfs.ext4 /dev/nbd0* * mkfs.ext4: Device size reported to be zero. Invalid partition specified, or*

On Sat, Nov 07, 2015 at 05:09:52PM -0600, Jason Pepas wrote: > On Sat, Nov 7, 2015 at 3:02 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > >> I'm not sure where to start with hunting down why mkfs's pwrite() > >> calls aren't failing. I'd look to the kernel source for that? > > > > It looks like it's really an e2fsprogs problem, not a

Unfinished (needs tests). This is my attempt to make a "remote tmpfs" plugin as outlined in this prior email: https://www.redhat.com/archives/libguestfs/2020-March/msg00134.html Although it would be possible to construct something a bit like this using existing plugins and filters (perhaps with some new features in those filters) I think it may be nicer to have a dedicated plugin for

On Thu, Jun 27, 2019 at 16:22:27 +0530, Tanmoy Sinha wrote: > Hi All, > > I am unable to figure out the issue here, when I try to create a filesystem > (ext4) on a virtual disk using qemu-nbd. This happens intermittently. > > Following is the sequence of commands:- > > $> qemu-img create -f qcow2 test.qcow2 30G > > > $> qemu-nbd --connect=/dev/nbd0

This can be used for creating temporary disks to thin clients, as a kind of "remote tmpfs". See also: https://www.redhat.com/archives/libguestfs/2020-March/msg00134.html --- plugins/data/nbdkit-data-plugin.pod | 1 + plugins/file/nbdkit-file-plugin.pod | 1 + plugins/linuxdisk/nbdkit-linuxdisk-plugin.pod | 7 +- plugins/memory/nbdkit-memory-plugin.pod |

On Mon, Oct 15, 2018 at 10:28:25AM -0400, Raghuram Devarakonda wrote: > On Mon, Oct 15, 2018 at 3:54 AM Richard W.M. Jones <rjones@redhat.com> wrote: > > > > [Adding libguestfs mailing list] > > > > On Sun, Oct 14, 2018 at 11:53:17AM -0400, Raghuram Devarakonda wrote: > > > Hi, > > > > > > In our project, we deal with quite large sparse

v2 was here: https://www.redhat.com/archives/libguestfs/2020-March/msg00154.html v3: - Micro-optimize tmpdir. - Quote $disk in default command shell fragment. - Don't redirect mkfs output to /dev/null. Instead use exec </dev/null >/dev/null before the shell fragment. We may want to do this in other places where we run external shell scripts, or more generally for all

On 10/20/19 6:06 AM, Richard W.M. Jones wrote: > New APIs are added which let you enable or disable features of NBD > URIs, mainly for security reasons. > > tls-psk-file is *disabled* by default for obvious security reasons. > All other features are enabled by default. > --- > @@ -1445,6 +1453,75 @@ C<\"qemu:dirty-bitmap:...\"> for qemu-nbd >

Hi. We get the errors below in the kernel logs. WARNING: Kernel Errors Present Buffer I/O error on device nbd0, ...: 27 Time(s) Buffer I/O error on device nbd16,...: 3 Time(s) end_request: I/O error, dev nbd0, secto...: 13 Time(s) end_request: I/O error, dev nbd1, secto...: 7 Time(s) end_request: I/O error, dev nbd10, sect...: 7 Time(s) I see someone else has reported this error message. E.g.

Previous discussion: https://www.redhat.com/archives/libguestfs/2019-August/msg00102.html Last night I experimentally added support for URIs that contain the query parameter tls-psk-file, as part of rewriting the tests to cover more of the URI code. So you can now have a URI like: nbds://alice@localhost/?tls-psk-file=keys.psk However there's an obvious security problem here because now

2017-07-27 20:18 GMT+08:00 Richard W.M. Jones <rjones@redhat.com>: > On Thu, Jul 27, 2017 at 06:34:13PM +0800, lampahome wrote: > > I can mount qcow2 img to nbd devices through guestfish or qemu-nbd > > > > I'm curious about which performance is better? > > They do quite different things, they're not comparable. > > Can you specifically give the

2017-07-28 0:31 GMT+08:00 Richard W.M. Jones <rjones@redhat.com>: > On Fri, Jul 28, 2017 at 12:23:04AM +0800, lampahome wrote: > > 2017-07-27 20:18 GMT+08:00 Richard W.M. Jones <rjones@redhat.com>: > > > > > On Thu, Jul 27, 2017 at 06:34:13PM +0800, lampahome wrote: > > > > I can mount qcow2 img to nbd devices through guestfish or qemu-nbd > >

I have a system with a large LVM VG partition. I was wondering if there is a way i could share the partition using nbd and have the nbd-client have access the LVM as if it was local. SYSTEM A: /dev/sda3 is a LVM partition and is assigned to VG volgroup1. I want to share /dev/sda3 via nbd-server SYSTEM B: receives A''s /dev/sda3 as /dev/nbd0. I want to access it as VG volgroup1. I am

On Mon, 15 Oct 2018, Nir Soffer wrote: > On Sat, Oct 13, 2018 at 9:45 PM Eric Wheeler <nbd@lists.ewheeler.net> wrote: > Hello all, > > It might be neat to attach ISOs to KVM guests via websockets.  Basically > the  browser would be the NBD "server" and an NBD client would run on the > hypervisor, then use `virsh change-media vm1 hdc

On 08/03/2018 02:28 PM, Nir Soffer wrote: > File systems not supporting FALLOC_FL_ZERO_RANGE yet fall back to manual > zeroing. > > We can avoid this by combining two fallocate calls: > > fallocate(FALLOC_FL_PUNCH_HOLE) > fallocate(0) > > Based on my tests this is much more efficient compared to manual > zeroing. The idea came from this qemu patch: >

https://bugzilla.samba.org/show_bug.cgi?id=12305 Bug ID: 12305 Summary: --fallocate and --sparse works wrong Product: rsync Version: 3.1.1 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter: