You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Nils Breunese (JIRA)" <ji...@apache.org> on 2009/12/16 16:51:18 UTC
[jira] Created: (COUCHDB-602) Cannot use NFS for storage
Cannot use NFS for storage
--------------------------
Key: COUCHDB-602
URL: https://issues.apache.org/jira/browse/COUCHDB-602
Project: CouchDB
Issue Type: Bug
Components: Test Suite
Affects Versions: 0.10
Reporter: Nils Breunese
Our hosting provider claims they cannot upgrade our CouchDB installation from version 0.9.1 to 0.10 as the test suite for 0.10 is failing.
This is a translation from their report:
----
CouchDB can't handle having its data directory on NFS.
It seems CouchDB tries to do this:
1 mkdir test
2 start process X with fd under test/foo
3 do the work
4 rm test/foo
5 rmdir test
6 kill process X
When test/ is on NFS:
In step 4 an open file is being removed. NFS doesn't really support this
and the workaround is that the client implementation does
mv file .nfsXXXXXXX
However, the 'rmdir test' in step 5 then cannot succeed anymore, since
the directory is not empty. This eventually causes CouchDB to crash.
In earlier versions of CouchDB the open/rm/rmdir/kill order may have
been different, for instance open/rm/kill/rmdir.
----
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (COUCHDB-602) Cannot use NFS for storage
Posted by "Matt Chambers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845544#action_12845544 ]
Matt Chambers commented on COUCHDB-602:
---------------------------------------
I also need couch to work with NFS.
> Cannot use NFS for storage
> --------------------------
>
> Key: COUCHDB-602
> URL: https://issues.apache.org/jira/browse/COUCHDB-602
> Project: CouchDB
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 0.10
> Reporter: Nils Breunese
> Attachments: error.gz
>
>
> Our hosting provider claims they cannot upgrade our CouchDB installation from version 0.9.1 to 0.10 as the test suite for 0.10 is failing.
> This is a translation from their report:
> ----
> CouchDB can't handle having its data directory on NFS.
> It seems CouchDB tries to do this:
> 1 mkdir test
> 2 start process X with fd under test/foo
> 3 do the work
> 4 rm test/foo
> 5 rmdir test
> 6 kill process X
> When test/ is on NFS:
> In step 4 an open file is being removed. NFS doesn't really support this
> and the workaround is that the client implementation does
> mv file .nfsXXXXXXX
> However, the 'rmdir test' in step 5 then cannot succeed anymore, since
> the directory is not empty. This eventually causes CouchDB to crash.
> In earlier versions of CouchDB the open/rm/rmdir/kill order may have
> been different, for instance open/rm/kill/rmdir.
> ----
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-602) Cannot use NFS for storage
Posted by "Nils Breunese (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nils Breunese updated COUCHDB-602:
----------------------------------
Attachment: error.gz
Compressed error log.
> Cannot use NFS for storage
> --------------------------
>
> Key: COUCHDB-602
> URL: https://issues.apache.org/jira/browse/COUCHDB-602
> Project: CouchDB
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 0.10
> Reporter: Nils Breunese
> Attachments: error.gz
>
>
> Our hosting provider claims they cannot upgrade our CouchDB installation from version 0.9.1 to 0.10 as the test suite for 0.10 is failing.
> This is a translation from their report:
> ----
> CouchDB can't handle having its data directory on NFS.
> It seems CouchDB tries to do this:
> 1 mkdir test
> 2 start process X with fd under test/foo
> 3 do the work
> 4 rm test/foo
> 5 rmdir test
> 6 kill process X
> When test/ is on NFS:
> In step 4 an open file is being removed. NFS doesn't really support this
> and the workaround is that the client implementation does
> mv file .nfsXXXXXXX
> However, the 'rmdir test' in step 5 then cannot succeed anymore, since
> the directory is not empty. This eventually causes CouchDB to crash.
> In earlier versions of CouchDB the open/rm/rmdir/kill order may have
> been different, for instance open/rm/kill/rmdir.
> ----
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (COUCHDB-602) Cannot use NFS for storage
Posted by "Paul Joseph Davis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791430#action_12791430 ]
Paul Joseph Davis commented on COUCHDB-602:
-------------------------------------------
Can you get the error traceback? I'm still intrigued as to what possibly changed between 0.9.1 and 0.10.0 that changed. I find it more likely that we just weren't testing something in 0.9.1
> Cannot use NFS for storage
> --------------------------
>
> Key: COUCHDB-602
> URL: https://issues.apache.org/jira/browse/COUCHDB-602
> Project: CouchDB
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 0.10
> Reporter: Nils Breunese
>
> Our hosting provider claims they cannot upgrade our CouchDB installation from version 0.9.1 to 0.10 as the test suite for 0.10 is failing.
> This is a translation from their report:
> ----
> CouchDB can't handle having its data directory on NFS.
> It seems CouchDB tries to do this:
> 1 mkdir test
> 2 start process X with fd under test/foo
> 3 do the work
> 4 rm test/foo
> 5 rmdir test
> 6 kill process X
> When test/ is on NFS:
> In step 4 an open file is being removed. NFS doesn't really support this
> and the workaround is that the client implementation does
> mv file .nfsXXXXXXX
> However, the 'rmdir test' in step 5 then cannot succeed anymore, since
> the directory is not empty. This eventually causes CouchDB to crash.
> In earlier versions of CouchDB the open/rm/rmdir/kill order may have
> been different, for instance open/rm/kill/rmdir.
> ----
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-602) Cannot use NFS for storage
Posted by "Paul Joseph Davis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Joseph Davis updated COUCHDB-602:
--------------------------------------
Skill Level: Committers Level (Medium to Hard)
> Cannot use NFS for storage
> --------------------------
>
> Key: COUCHDB-602
> URL: https://issues.apache.org/jira/browse/COUCHDB-602
> Project: CouchDB
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 0.10
> Reporter: Nils Breunese
> Attachments: error.gz
>
>
> Our hosting provider claims they cannot upgrade our CouchDB installation from version 0.9.1 to 0.10 as the test suite for 0.10 is failing.
> This is a translation from their report:
> ----
> CouchDB can't handle having its data directory on NFS.
> It seems CouchDB tries to do this:
> 1 mkdir test
> 2 start process X with fd under test/foo
> 3 do the work
> 4 rm test/foo
> 5 rmdir test
> 6 kill process X
> When test/ is on NFS:
> In step 4 an open file is being removed. NFS doesn't really support this
> and the workaround is that the client implementation does
> mv file .nfsXXXXXXX
> However, the 'rmdir test' in step 5 then cannot succeed anymore, since
> the directory is not empty. This eventually causes CouchDB to crash.
> In earlier versions of CouchDB the open/rm/rmdir/kill order may have
> been different, for instance open/rm/kill/rmdir.
> ----
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (COUCHDB-602) Cannot use NFS for storage
Posted by "Nils Breunese (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802213#action_12802213 ]
Nils Breunese commented on COUCHDB-602:
---------------------------------------
I got this message from the hosting company:
----
when doing "Run All" in the test suite, the first test that fails is "compact" the error log is attached.
from time to time I can see quie a few .nfs files in the couchdb datastore directory:
find . | grep nfs
./.test_suite_db_design/.nfs00000000019000890039f45d
./.test_suite_db_design/.nfs00000000019000880039f45e
./.test_suite_db_design/.nfs000000000190008b0039f460
./.test_suite_db_design/.nfs000000000190008a0039f461
./.nfs00000000006800880039f45c
./.nfs000000000068008a0039f45f
----
I'll attach the error log.
> Cannot use NFS for storage
> --------------------------
>
> Key: COUCHDB-602
> URL: https://issues.apache.org/jira/browse/COUCHDB-602
> Project: CouchDB
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 0.10
> Reporter: Nils Breunese
> Attachments: error.gz
>
>
> Our hosting provider claims they cannot upgrade our CouchDB installation from version 0.9.1 to 0.10 as the test suite for 0.10 is failing.
> This is a translation from their report:
> ----
> CouchDB can't handle having its data directory on NFS.
> It seems CouchDB tries to do this:
> 1 mkdir test
> 2 start process X with fd under test/foo
> 3 do the work
> 4 rm test/foo
> 5 rmdir test
> 6 kill process X
> When test/ is on NFS:
> In step 4 an open file is being removed. NFS doesn't really support this
> and the workaround is that the client implementation does
> mv file .nfsXXXXXXX
> However, the 'rmdir test' in step 5 then cannot succeed anymore, since
> the directory is not empty. This eventually causes CouchDB to crash.
> In earlier versions of CouchDB the open/rm/rmdir/kill order may have
> been different, for instance open/rm/kill/rmdir.
> ----
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.