Ok, I think I was able to reproduce the same thing that you were
seeing. Can you try the attached patch and let me know if it fixes
things on your end too?
thanks!
-Phil
On 05/06/2010 02:34 PM, Phil Carns wrote:
Actually, it might be good if you could just send me the fs.conf file
for your t
Actually, it might be good if you could just send me the fs.conf file
for your test setup.
thanks,
-Phil
On 05/06/2010 02:26 PM, Phil Carns wrote:
Thanks Bart. In your example, what are the names and ports of each of
the servers involved? Are they all on the same node (with different
ports)
Thanks Bart. In your example, what are the names and ports of each of
the servers involved? Are they all on the same node (with different
ports) by any chance?
thanks,
-Phil
On 05/04/2010 09:50 AM, Bart Taylor wrote:
The log file is attached.
I upgraded, let the file system start respondin
Can you get a server into this state (where everything works except for
> strip size files), turn on verbose logging, and then try to create a
big file?
I'd like to see the log file from the metadata server for the file in
question. That server is the one that has to come up with the
pre-cre
Yes, it does finish the Trove Migration and print similar messages. The file
system responds to requests; I just can't create files larger than one strip
size. Once I restart the file system I can, but on first start, they fail.
Bart.
On Thu, Apr 29, 2010 at 1:50 PM, Kevin Harms wrote:
> Bar
Bart,
I think the server should print out when conversion starts and ends.
examples:
Trove Migration Started: Ver=2.6.3
Trove Migration Complete: Ver=2.6.3
Trove Migration Set: 2.8.1
Does is get that far?
kevin
On Apr 29, 2010, at 1:55 PM, Bart Taylor wrote:
> Thanks for the infor
Thanks for the information and suggestion Phil. Unfortunately, I didn't get
a different result after moving that BMI init block. I also managed to
reproduce this once while leaving the trove method to alt-aio although that
doesn't seem directly related to the direction you were going.
Another thin
Sadly none of my test boxes will run 2.6 any more, but I have a theory
about what the problem might be here.
For some background, the pvfs2-server daemon does these steps in order
(among others): initializes BMI (networking), initializes Trove
(storage), and then finally starts processing requ
