<keyname="error_0254">Failed to read the lvm.conf file. The reason why should be logged above.</key>
<keyname="error_0255">Failed to write the lvm.conf file. The reason why should be logged above.</key>
<!-- Files templates -->
<!-- NOTE: Translating these files requires an understanding of which likes are translatable -->
@ -745,6 +747,8 @@ It should be provisioned in the next minute or two.</key>
<keyname="job_0270">All machines are now available on the first BCN!</key>
<keyname="job_0271">One of the Striker dashboards has not yet updated network information in the database. We need this to know which IP to tell the peer to use to connect to us. We'll wait a moment and check again.</key>
<keyname="job_0272">The cluster still hasn't started. Calling startup again (will try once per minute).</key>
<keyname="job_0273">Successfully added/confirmed the filter in lvm.conf.</key>
<keyname="job_0274">Failed to add/confirmed the filter in lvm.conf! This should be corrected later by 'scan-drbd' though.</key>
@ -1432,6 +1436,8 @@ The file: [#!variable!file!#] needs to be updated. The difference is:
<keyname="log_0591">Wiping any file system signatures and then deleting the logical volume: [#!variable!device_path!#].</key>
<keyname="log_0592">The resource name: [#!variable!resource_name!#] was found, returning the first TCP port and minor number.</key>
<keyname="log_0593">The job: [#!variable!command!#] with UUID: [#!variable!job_uuid!#] is a start-time job, not running it now.</key>
<keyname="log_0594">The lvm.conf already has the filter: [#!variable!filter!#], will not change it.</key>
<keyname="log_0595">Updated the lvm.conf file to add the filter: [#!variable!filter!#] to prevent LVM from seeing the DRBD devices as LVM devices.</key>
<!-- Messages for users (less technical than log entries), though sometimes used for logs, too. -->
<keyname="message_0001">The host name: [#!variable!target!#] does not resolve to an IP address.</key>