[
https://issues.apache.org/jira/browse/QPID-5997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097179#comment-14097179
]
Andrew Stitcher commented on QPID-5997:
---------------------------------------
This is very likely caused by the filesystem for --store-dir not supporting
O_DIRECT.
There was also a report on IRC of this happening with XFS and ext4 over a Xen
block device. In this case it seems likely that the issue is the block device
somehoe, not the fs. This implies that the broker with store may not work in
some VM situations.
The possible solutions I can see are:
* Fall back to opening without O_DIRECT if the open fails - there is no change
in reliability guarantees just a possible loss of performance.
* Detect EINVAL here and print a more useful warning/error message, but this
won't help if you can't change your underlying block device.
> [linearstore] Cannot write to journal files when store dir is located in /tmp
> -----------------------------------------------------------------------------
>
> Key: QPID-5997
> URL: https://issues.apache.org/jira/browse/QPID-5997
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: Future
> Reporter: Kim van der Riet
> Assignee: Kim van der Riet
>
> When starting a broker using linearstore, and which has *\-\-store-dir* set
> to /tmp, the store fails with {{JERR_JNLF_OPEN: Unable to open file for
> write... errno=22 (Invalid argument)...}} It is also possible that using /tmp
> in *\-\-data-dir* may have the same effect if there is no separate
> *\-\-store-dir* parameter, this remains to be tested.
> This may be an issue with tempfs, but the nature of the problem is unknown at
> this time. Some anecdotal evidence from Alan Conway suggests that if /tmp is
> a part of the regular root file system, it works ok, but if it is mounted in
> a separate partition, then this error occurs.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
