You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Thomas Mueller (JIRA)" <ji...@apache.org> on 2009/11/17 10:30:39 UTC
[jira] Issue Comment Edited: (JCR-2396) File Journal workaround for
misbehaving NFS implementations
[ https://issues.apache.org/jira/browse/JCR-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778787#action_12778787 ]
Thomas Mueller edited comment on JCR-2396 at 11/17/09 9:28 AM:
---------------------------------------------------------------
This patch used FileChannel.lock(..) as a workaround.
The patch is against Jackrabbit 1.4.10.
was (Author: tmueller):
This patch used FileChannel.lock(..) as a workaround.
> File Journal workaround for misbehaving NFS implementations
> -----------------------------------------------------------
>
> Key: JCR-2396
> URL: https://issues.apache.org/jira/browse/JCR-2396
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: clustering
> Affects Versions: core 1.4.10
> Environment: Some versions of NFS
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Priority: Minor
> Attachments: diff.patch
>
>
> After one NFS client wrote data to a file, reading from another client results in blocks of zero
> in some NFS implementations. This is a known issue:
> http://markmail.org/search/blocks+of+zeros+%28NULLs%29+in+NFS+files+in+kernels
> The Jackrabbit file journal implementation does not work properly in this situation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.