Thanks for your answer. The problem is actually solved.
Using the default settings creates the storage areas in root-only
privileged directories, so i am forced to use root (or sudo) with the
pvfs2-server -f command. But I did not use superuser to start the server
in normal work mode, to avoid possible security problems. Starting the
server from root account actually worked fine, so it was a simple 'wrong
permissions' issue :) .
I will try from now on creating all necessary files in
'non-root-allowed folders', to avoid using the server with a privileged
account.
I think that it would be good if the errors where a little more clear
about the origin of the problem, but I guess it probably would take a
lot of not-really-necessary rewrite of a lot of code.
Also, just for completeness' sake, this is the answer to some of your
other questions:
The storage data and metadata files where successfully created whith
the -f option. Use of the server's -r option successfully removed the
storage files. Obviously I need to use those options with root
privileges because of the reason I mentioned.
I actually recreated it several dozen times without errors except for
this:
Two or three times when using -r to delete, there was one leftover file
(always the same one):
<pvfs2-storage folder>/<random number>/__db.001
I don't know how to reproduce this error. I tried to understand why,
thinking it may be a hint to the real problem; however I could not find
a way to make it happen on purpose. It only happend 2 or 3 times among
several dozens, as stated above.
Weird, but since it seems to not be the cause of my original problem
and it happens only after deleting the storage, I don't think it really
matters.
In any case, thanks kindly for all your quick answers.
-------- Mensaje original --------
Asunto: RE: [Pvfs2-users] trove collection not initialized
Fecha: 2013-08-23 19:29
Remitente: "Elaine Quarles" <[email protected]>
Destinatario: 'Carlos Outes Durán' <[email protected]>,
<[email protected]>
Can you confirm that running the server with the -f option successfully
initialized the storage area? You should be able to see *.db files that
were created.
Are you trying to start the server with the same userid that you used
when you initialized the storage area? If not permissions may be causing
a problem.
Hope that helps,
Elaine
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Carlos
Outes Durán
Sent: Wednesday, August 21, 2013 1:41 PM
To: [email protected]
Subject: [Pvfs2-users] trove collection not initialized
Hello. I am trying to adapt a previously parallelized program to use
pvfs2 (orange 2.8.7). I never used the pvfs2 filesystem before.
When I install Berkeley DB then orange, I receive no noticeable error.
I can use genconfig and then start the server with -f to create
storage.
No errors either. However, when launching pvfs2-server, it does not
output anything but one line ('...pvfs2 server on node .... starting'),
but does not start.
This is the /tmp/pvfs2-server.log file (logging was set to 'trove', to
increase info):
[D 08/21/2013 19:03:18] PVFS2 Server version 2.8.7-orangefs starting.
[D 08/21/2013 19:03:18] dbpf_thread_initialize: initialized [D
08/21/2013 19:03:18] dbpf_collection_lookup of coll: pvfs2-fs [D
08/21/2013 19:03:18] lookup got error (22) [E 08/21/2013 19:03:18] Error
initializing trove for filesystem pvfs2-fs [E 08/21/2013 19:03:18]
Error: Could not initialize server subsystems [E 08/21/2013 19:03:18]
Error: Could not initialize server; aborting.
[D 08/21/2013 19:03:18] dbpf_thread_function started [E 08/21/2013
19:03:18] Trove collection not defined.
[D 08/21/2013 19:03:18] dbpf_thread_function ending [D 08/21/2013
19:03:18] dbpf_thread_finalize: finalized [E 08/21/2013 19:03:18]
dbpf_finalize attr sync: Invalid argument
Since the server does not start, I cannot use any of the utilities.
Only pvfs2-showcoll gives a hint:
Error from trove_initialize is -1073742082
pvfs2-showcoll: error: trove initialize failed; aborting!
I am using a virtual machine (VM oracle VirtualBox) running on windows
8. I tried installing several distros (ubuntu 10.04 server and 10.10,
fedora 11), either updated and without updates. Berkeley db was 4.8.30,
then tried 5.3.21.
The odd thing is, about a month or so ago I instaled everything with
the same sources and it worked like a charm (after several errors and
retrials, ehem). I used the ping utility and tested files with pvfs2-ls
and pvfs2-cp with no problems. Then I went on working on something else,
but when I tried to use pvfs2 again recently, it failed as you can see.
Unfortunately, the VM in which I installed the first time got corrupted
(can't even mount partition, hangs the VM) so I can't compare to see if
i did something diferent then. I think I simply followed the guide, and
always used the default configurations like I am doing now.
Any thoughts on what is the problem? Without the use of pvfs2, the
project has no meaning, so I'm in a quandary. Any help would be greatly
apreciated. If you need me to give more data, please tell me what you
want to know and if posible how to obtain it.
Thanks in advance for your attention. (Sidenote: my home language is
not english, so I'm sorry for any weird spelling I may have used)
_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
