Thanks Phil. I've committed a fix for this along with some other
minor changes over the course of the day. The biggest change was to
allow endpoints to be separated by comma instead of a semi-colon, for
users that don't quote the spec string. Let me know if you hit any
other problems.
Thanks for getting this stuff committed and cleaned up!
I think a new bug may have been introduced along the way, however. It
looks like the server config files "HostID" field is being set to the
alias name rather than the fully qualified BMI address. For example, if
you do a build and check
On May 31, 2006, at 9:47 PM, Sam Lang wrote:
I went ahead and committed the --metaspec and --iospec options to
pvfs2-genconfig. The changes aren't based on your patch Bart,
Errr...that was meant to say ARE based on Bart's patch...
but I did a lot of cleanup and ended up changing the code
I went ahead and committed the --metaspec and --iospec options to
pvfs2-genconfig. The changes aren't based on your patch Bart, but I
did a lot of cleanup and ended up changing the code fairly
significantly. The options themselves allow the endpoints to be
specified as follows:
[://]:
On Thu, May 18, 2006 at 06:26:02PM +0200, Phil Carns wrote:
> I just ran across this email when looking for a reference to the
> pvfs2-ping patch, but I thought I would add my 2c.
>
> I think for the range of cases that Bart was addressing it isn't
> necessarily as simple as choosing different s
Robert Latham wrote:
On Thu, Apr 06, 2006 at 02:40:01PM -0600, Bart Taylor wrote:
As an example, suppose that you are using a SAN and you want one particular
server to have a dedicated LUN for metadata. In that case you might want to
specify something like this:
--iospecs host1:3335:/mnt/data-
On Thu, Apr 06, 2006 at 02:40:01PM -0600, Bart Taylor wrote:
> As an example, suppose that you are using a SAN and you want one particular
> server to have a dedicated LUN for metadata. In that case you might want to
> specify something like this:
> --iospecs host1:3335:/mnt/data-lun,host2:3335:/m
On 4/6/06, Robert Latham <[EMAIL PROTECTED]> wrote:
Hi Bart. Thanks for the patches. A few commentsOn Mon, Apr 03, 2006 at 10:53:28AM -0600, Bart Taylor wrote:> RHEL4-compiler-warnings.patch:>> This is a few quick data type fixes so the source will also compile on
> 64 bit RHEL4 without warnings.
Hi Bart. Thanks for the patches. A few comments
On Mon, Apr 03, 2006 at 10:53:28AM -0600, Bart Taylor wrote:
> RHEL4-compiler-warnings.patch:
>
> This is a few quick data type fixes so the source will also compile on
> 64 bit RHEL4 without warnings. These changes are on test programs.
The tes
