So it's not trivial code to write; it's quite possible for LVM or the filesystem to have a bug that corrupts your data under the right circumstances.
2014-01-02 13:29:54.257 Main:0x1fcb2db0 <WARNING> @v_dev_node0003: 01000/3938: MiniRos 54043196826332083 does not have proper SAL files2014-01-02 13:29:54.278 Main:0x1fcb2db0 <PANIC> @v_dev_node0003: VX001/2973: Data consistency problems found; startup aborted HINT: Check that all file systems are properly mounted. Also, the --force option can be used to delete corrupted data and recover from the cluster LOCATION: mainEntryPoint, /scratch_a/release/vbuild/vertica/Basics/vertica.cpp:10822014-01-02 13:29:54.305 Main:0x1fcb2db0 [Main] <PANIC> Wrote backtrace to ErrorReport.txt
You said to accomplish this challenge, run the installer, which installer did you mean?
And you also said, HP will not this configuration, correct?!
aseering wrote:Hi Bill,Vertica will run on LVM. You can accomplish this by running the installer, pointing it at an LVM volume, and following the displayed instructions to ignore the warning that you receive.That said, we don't provide support for the configuration. The reason that we don't support it isn't fundamental to Vertica. It's because, among other reasons, many older versions of LVM (shipped with Linux distributions that we still support) have known limitations in them that can lead to data corruption. For one specific technical example, LVM did not properly/fully support write barriers prior to the Linux 2.6.33 kernel. (As always, vendor kernels may vary; that's the upstream version number.) This limitation affects all applications, including databases, running the affected kernels.Vertica will work on just about anything, more so than many other products because of our design. (I've seen Vertica run on a FUSE-backed older version of encfs, for example. It didn't run well, but it ran, which is more than I can say for many applications on that particular installation...) But we have a high standard for what we list as supported.Given all that -- many things are possible; but if you want a commitment, why trust me :-) Talk to your sales rep.Out of curiosity, why is LVM important to your use case? The typical use cases for LVM are partitioning of disk space among multiple services on a single machine, and fast snapshot-based backup/restore. Vertica is intended for large data sets and workloads; you wouldn't generally use Vertica on part of a machine, you use it on part of a data center. For snapshots, our backup tool is able to perform fast, efficient snapshots on regular ext3/4.Adam
Missed the word "support", my apolology!
HP will not support this configuration, correct?!
Which version of Vertica?
For RHL 7.4 you'll need Vertica 8.1.1-7 or later.
Also, your LVM version must be 2.02.66 or later, and must include device-mapper version 1.02.48 or later.