[ovirt-users] Re: oVirt 4.2.3 to 4.2.4 failed

On 07/02/2018 12:55 PM, Yuval Turgeman wrote: I believe that I have all the default options, and I have one extra partition for images. # # /etc/fstab # Created by anaconda on Sat Oct 31 18:04:29 2015 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # /dev/onn_node1-g8-h4/ovirt-node-ng-4.2.3.1-0.20180530.0+1 / ext4 defaults,discard 1 1 UUID=84ca8776-61d6-4b19-9104-99730932b45a /boot ext4    defaults        1 2 /dev/mapper/onn_node1--g8--h4-home /home ext4 defaults,discard 1 2 /dev/mapper/onn_node1--g8--h4-tmp /tmp ext4 defaults,discard 1 2 /dev/mapper/onn_node1--g8--h4-var /var ext4 defaults,discard 1 2 /dev/mapper/onn_node1--g8--h4-var_local_images /var/local/images       ext4    defaults        1 2 /dev/mapper/onn_node1--g8--h4-var_log /var/log ext4 defaults,discard 1 2 /dev/mapper/onn_node1--g8--h4-var_log_audit /var/log/audit ext4 defaults,discard 1 2 At this point I don't have a /var/crash mounted (or a LV even).  I assume I should re-create. I noticed on another server with the same problem, the var_crash LV isn't available.  Could this be part of the problem?   --- Logical volume ---   LV Path                /dev/onn/var_crash   LV Name                var_crash   VG Name                onn   LV UUID                X1TPMZ-XeZP-DGYv-woZW-3kvk-vWZu-XQcFhL   LV Write Access        read/write   LV Creation host, time node1-g7-h1.srihosting.com, 2018-04-05 07:03:35 -0700   LV Pool name           pool00   LV Status              NOT available   LV Size                10.00 GiB   Current LE             2560   Segments               1   Allocation             inherit   Read ahead sectors     auto Thanks Matt