search for: abyssm

...ase. > > I hope to get to the point where future qemu doesn't send the req-one > flag. There's several threads on the qemu list about how qemu-img is > slower than it needs to be because it is throwing away useful > information, and where it is aggravated by the kernel's abyssmal lseek() > performance on tmpfs. But until qemu learns useful caching, you're > right that most existing NBD clients that request block status do so one > extent at a time (because I don't know of any other existing NBD clients > that use BLOCK_STATUS yet). Is it ever possibl...

I think the extents map is just too complicated and is unnecessarily so. How about instead we define the plugin interface to be: int can_extents (void *handle); // as before int extents (void *handle, uint32_t count, uint64_t offset, uint32_t flags, struct nbdkit_extents_list *list); and have the extents_list be a simple list. The first extent you add must start at offset.

...gt; I hope to get to the point where future qemu doesn't send the req-one >> flag. There's several threads on the qemu list about how qemu-img is >> slower than it needs to be because it is throwing away useful >> information, and where it is aggravated by the kernel's abyssmal lseek() >> performance on tmpfs. But until qemu learns useful caching, you're >> right that most existing NBD clients that request block status do so one >> extent at a time (because I don't know of any other existing NBD clients >> that use BLOCK_STATUS yet). &gt...

...optimize for > that case. I hope to get to the point where future qemu doesn't send the req-one flag. There's several threads on the qemu list about how qemu-img is slower than it needs to be because it is throwing away useful information, and where it is aggravated by the kernel's abyssmal lseek() performance on tmpfs. But until qemu learns useful caching, you're right that most existing NBD clients that request block status do so one extent at a time (because I don't know of any other existing NBD clients that use BLOCK_STATUS yet). -- Eric Blake, Principal Software Eng...

I am receiving this error randomly when using smbclient to access pc shares : FINDFIRST gave ERRSRV - (Non-specific error code.) I use smbclient with Amanda to backup pc shares. For amanda to work, it uses smbclient to recursively scan through the entire directory tree and get total MB size of each directory. The problem is that when trying to enter some directories it gives the above error and

...o get to the point where future qemu doesn't send the req-one >>> flag. There's several threads on the qemu list about how qemu-img is >>> slower than it needs to be because it is throwing away useful >>> information, and where it is aggravated by the kernel's abyssmal lseek() >>> performance on tmpfs. But until qemu learns useful caching, you're >>> right that most existing NBD clients that request block status do so one >>> extent at a time (because I don't know of any other existing NBD clients >>> that use BLOCK_...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 zpool and zfs report different free space because zfs takes into account an internal reservation of 32MB or 1/64 of the capacity of the pool, what is bigger. So in a 2TB Harddisk, the reservation would be 32 gigabytes. Seems a bit excessive to me... - -- Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea at jcea.es -