Virtualization people seem to like needless complication. Take for example <i...
Virtualization people seem to like needless complication. Take for example virt-manager storage configuration. The options here are:
- disk: physical disk
- iscsi: iscsi target
- logical: LVM group
- fs: pre-formatted block device
- mpath: multipath enumerator
That's the first part. And on Linux this is all the same! It just a block device node somewhere in /dev[/mapper]. The rest is even more confusing:
- dir: directory
- netfs: network-exported filesystem
Again, it's all the same. It just a directory mounted in tree. Underlying technology (NFS, plain disk, CODA...) shouldn't matter. What if I have iSCSI target mounted in directory? Or mounted LVM volume? Or, God forbid, preformatted device mounted? Which option should I choose?
- disk: physical disk
- iscsi: iscsi target
- logical: LVM group
- fs: pre-formatted block device
- mpath: multipath enumerator
That's the first part. And on Linux this is all the same! It just a block device node somewhere in /dev[/mapper]. The rest is even more confusing:
- dir: directory
- netfs: network-exported filesystem
Again, it's all the same. It just a directory mounted in tree. Underlying technology (NFS, plain disk, CODA...) shouldn't matter. What if I have iSCSI target mounted in directory? Or mounted LVM volume? Or, God forbid, preformatted device mounted? Which option should I choose?
Shared with: Public
+1'd by: Remigiusz Świc
Comments
Comments powered by Disqus