You can use the lsblk command to get a concise listing of your disks, partitions, LVM volumes, and what is where.

There are many options for creating Informix chunks. I have basically no knowledge there, but a quick search for "informix" and "chunk" leads here.

So, /dev/sdc is an unformatted disk.

If you want to create normal (not LVM based) partitions, you'd use the fdisk cmd to partition the disk, then mkfs.ext4 to put an ext4 filesystem on each partition.

For LVM based, you'd create one partition across the whole disk using fdisk, the use pvcreate to add it to the vg (assuming you want to stick with one vg), then vgextend http://tldp.org/HOWTO/LVM-HOWTO/addpvstovg.html to add pv in, then lvcreate, then finally mkfs.ext4 on the Lv eg https://access.redhat.com/documentat...pnfs-HAAA.html

Try linuxtopia.org for a LOT of online readable manuals; this one is for you http://www.linuxtopia.org/online_boo...l_6_lvm_admin/
HTH

Not necessarily. All that is known from that is that it is not partitioned. That's the danger of putting a filesystem or an LVM volume directly on an unpartitioned device. You can get fooled into thinking that the device is unformatted and unused.

In my humble, you should always use LVM, even on "your own" machine. And you'll thank me for it, the moment that your main drive does begin to run out of space. (It's a very difficult situation to get out of ...)

The concept of LVM is extremely simple: a Linux "mount point," such as /usr, now does not correspond to "a single physical device." Rather, it refers to what's called a logical volume.

Physically, the contents of that logical volume may be spread over many different devices ... and you can safely shuffle things around without rebooting the computer.

Each physical device is placed into a "storage pool," and that "storage pool" is associated with a logical volume. The operating system (except within the LVM layer itself) is not aware that it is accessing multiple physical devices when it accesses what it perceives to be "a single, seamless, uninterrupted region of available storage."

It's simple (although the commands are strange), and it works very well. It becomes very simple to add storage, and to deal with a hardware device that is beginning to "(click, click ...) (click, click ...) (click, click ...)."

Sorry; mind freeze there; I meant unpartitioned of course ...