nbdkit-split-plugin(1)

πŸ’– nbdkit-split-plugin(1) πŸ’–

okay bestie, so this is the manual page for nbdkit-split-plugin, which is a whole thing in the nbdkit family (that's nbdkit(1), iykyk). It's giving ✨glue✨ energy, and honestly? Iconic.


🌸 NAME 🌸

nbdkit-split-plugin β€” an nbdkit plugin that concatenates split files into one disk. no cap, that's literally its whole job 🫢


✨ SYNOPSIS ✨

nbdkit split [file=]file1 [[file=]file2 [file=]file3 ...]

πŸ¦‹ DESCRIPTION πŸ¦‹

nbdkit-split-plugin is a file plugin for nbdkit(1). You hand it one or more filenames using the FILENAME parameter, and it logically concatenates those files into a single disk image. one disk, many files, slay πŸ’…

and like, if what you actually want is to add a virtual partition table on top of that? go look at nbdkit-partitioning-plugin(1). different vibe, different page πŸ’œ

πŸ’€ Differences from nbdkit-file-plugin πŸ’€

normally, if you just wanna serve one single file, you should be using nbdkit-file-plugin(1). this plugin is a different creature entirely, and here's the tea on how they differ:

  • nbdkit-file-plugin is faster and more efficient. it has a fully parallel implementation and doesn't have to deal with the complexity of locating the correct file to serve or splitting requests across files. the split plugin is out here doing all that extra mental labor 😭
  • nbdkit-file-plugin lets you resize the underlying file dynamically. with the split plugin, the underlying files must not be resized. periodt, do not touch 🚫
  • nbdkit-file-plugin can handle block devices, but the split plugin can only handle plain files. that's the boundary, bestie.
  • nbdkit-file-plugin handles writes of blocks of zeroes efficiently, but the split plugin cannot. πŸ’€
  • nbdkit-file-plugin can "punch holes" in the backing file in response to a trim request from the client, but the split plugin does not support this. not in its repertoire, nope.

πŸŽ€ PARAMETERS πŸŽ€

  • [file=]FILENAME β€” one or more files to open. they get logically concatenated in the order they appear on the command line, so the order is the moment, okay? this parameter must appear at least once β€” it's not optional, it's the whole point 🫢

the file= prefix may be omitted in most cases. see "Magic parameters" in nbdkit(1) for the deets ✨


πŸ“ FILES πŸ“

  • $plugindir/nbdkit-split-plugin.so β€” the plugin itself. that's the file, the moment, the icon πŸ‘‘

use nbdkit --dump-config to find the location of $plugindir. it'll tell you where it's at, no guessing needed πŸ’…


⭐ VERSION ⭐

nbdkit-split-plugin first appeared in nbdkit 1.2. a classic, an OG, we love her 🌈


🌈 SEE ALSO 🌈

nbdkit(1), nbdkit-plugin(3), nbdkit-file-plugin(1), nbdkit-partitioning-plugin(1).

go read them, they're all connected, it's a whole ecosystem bestie 🧚


πŸ‘‘ AUTHORS πŸ‘‘

Richard W.M. Jones πŸ’œ


Copyright Red Hat


πŸ“œ LICENSE πŸ“œ

redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  • Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  • Neither the name of Red Hat nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY RED HAT AND CONTRIBUTORS ''AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL RED HAT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

okay that's the whole page, we ate and left no crumbs πŸ½οΈπŸ’– this one's from nbdkit-1.48.1, dated 2026-08-29 β€” so like, go forth and concatenate those files, bestie. bye babes πŸŽ€πŸ¦‹βœ¨

πŸ“¦ where this page comes from