-
Type:
Bug
-
Resolution: Not a bug
-
Priority:
Medium
-
None
-
Affects Version/s: 4.0.1
-
Component/s: Issue - Attachments
-
Environment:
Red Hat Enterprise Server on i686
Kernel version 2.6.18-164.6.1.el5
-
4
-
4
-
Severity 2 - Major
-
2
Hi everyone, we have reviewed this bug report recently and realized that this bug request was created before it was explicitly indicated that NFS are not supported in Jira, and also that Jira 4 (the version where this bug was reported) reached End of Life quite some time ago, so this bug ticket is no longer valid, and we will proceed to close it.
If there are is any feedback for the support of NFS in Jira, please see the feature request JRASERVER-33887 Implement JIRA Lucene Index NFS Support where the interest for this is being gathered.
Thanks,
René Chiquete - Atlassian Support.
To facilitate access to attachments in JIRA by the deployment team, a LUN was shared from the NetApp SAN as NFS to the JIRA host and as CIFS to the Windows hosts. NetApp also has a number of facilities that better allow the management of files in backups to provide mminimum downtime on the server as well as the minimal amount of space used for backups.
The mount was successful on both the Linux and the Windows systems. We were able to copy files from the local filesystems on the Linux host to the NFS mount and read them from Windows.
The JIRA attachments directory was changed to use the NFS mount. JIRA failed to create the attachment with a permission denied error. We tried a different locally-mountd attachments directory which worked fine.
We were able to resolve this by using a CIFS mount of the same LUN. This is not ideal as smbmount is generally considered to be less secure on Linux than is NFS. We would like to have this addressed so that we can use properly use NFS in the future.
