On 18 May 2013, at 14:27, Goswin von Brederlow wrote: > I think the inital idea was to send a resize ioctl to the block device > on the client. The kernel would then send NBD_CMD_RESIZE to the server > and the server would reply with the new size. I don't think that will > ever work right with multiple clients for the same export. You would > have to resize each individually.
The initial idea was that the client (kernel or otherwise) would send NBD_CMD_RESIZE to the server (if the server supported it and permitted it) and then the server would resize the volume to the size requested by the client. That's simple enough when the client is file backed. In things like qemu-nbd it's also useful as backing stores such as ceph and qcow2 can be resized online. I think multiple clients for the same export only work sanely with readonly mounts (unless you are doing some crazy stuff like running ocfs2 on nbd). I would presume resize would not work on a readonly mount. -- Alex Bligh ------------------------------------------------------------------------------ AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d _______________________________________________ Nbd-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nbd-general
