Right, the storage engine isn’t started since the backend storage hasn’t been formatted:

waiting for storage format on server 0

Even with no NVDIMMs in the system, we still need to wipe out the SSDs so that all blocks are marked as not allocated (i.e. for wear leveling). The following command should allow you to format & start the engine:

$ daos_shell storage format

As suggested by Xuezhao, you should create your own daos_server.yml with the list of SSDs you want to use.

To list the SSDs available on the system, you can run the following commands:

$ daos_server storage prep-nvme

2019/06/20 19:06:24 storage_nvme.go:96: debug: spdk setup with _NRHUGE=1024

2019/06/20 19:06:24 storage_nvme.go:100: debug: spdk setup with _TARGET_USER=root

$ daos_server storage scan

[…]

NVMe:

- model: 'INTEL SSDPED1K375GA '

  serial: 'PHKS7335009W375AGN  '

  pciaddr: 0000:87:00.0

  fwrev: E2010324

  namespaces:

  - id: 1

    capacity: 375

- model: 'INTEL SSDPEDMD016T4 '

  serial: 'CVFT5226001C1P6DGN  '

  pciaddr: 0000:da:00.0

  fwrev: 8DV10171

  namespaces:

  - id: 1

    capacity: 1600

- model: 'INTEL SSDPEDMD016T4 '

  serial: 'CVFT5506004Z1P6DGN  '

  pciaddr: 0000:81:00.0

  fwrev: 8DV10171

  namespaces:

  - id: 1

    capacity: 1600

And then populate the yaml file with the devices that you want to use, for instance:

  bdev_class: nvme

  bdev_list: ["0000:81:00.0", "0000:da:00.0"]

We are working on automatic storage configuration with CPU affinity detection, but this feature isn’t available yet.

HTH

Cheers,

Johann

looks like your daos_server was not started successfully.
you may check the details in the config file /usr/local/etc/daos_server.yml, try to change some setting to see if it can work, for example can test to comment out (add "#" to start of the line) all the "bdev_" started options.
If still cannot work, you may post your daos_server.yml and the daos log (path configured by "log_file" option, can set "log_mask: DEBUG") to jira ticket or here if jira does not work for you.

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

Hello,

I got first issue resolved after run: $ daos_shell storage format

I think you could add this step into the quick start document.

Yes I have already created daos_server.yml, from the one at install/etc/daos_server.yml.

Now the storage server seems formatted, but there is new issue happen :

When I run dmg create, it encounter another issue :

failed to create pool: -1007
-------------------------------------------------------
Primary job  terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
-------------------------------------------------------
--------------------------------------------------------------------------
orterun detected that one or more processes exited with non-zero status, thus causing
the job to be terminated. The first process to do so was:

  Process name: [[27363,1],0]
  Exit code:    1

If I execute: daos_shell pool create –s 1G

It says:

2019/06/21 17:29:19 config.go:122: debug: DAOS Client config read from /usr/local/etc/daos.yml

Active connections: [localhost:10001]

Creating DAOS pool with 1GB SCM and 0B NvMe storage (1.000 ratio)

parsing rank list: element 0: strconv.ParseUint: parsing "": invalid syntax

I’m trying to resolve by my ways, any hints will be appreciated.

Regards,

Shengyu

Right, the storage engine isn’t started since the backend storage hasn’t been formatted:

waiting for storage format on server 0

Even with no NVDIMMs in the system, we still need to wipe out the SSDs so that all blocks are marked as not allocated (i.e. for wear leveling). The following command should allow you to format & start the engine:

$ daos_shell storage format

As suggested by Xuezhao, you should create your own daos_server.yml with the list of SSDs you want to use.

To list the SSDs available on the system, you can run the following commands:

$ daos_server storage prep-nvme

2019/06/20 19:06:24 storage_nvme.go:96: debug: spdk setup with _NRHUGE=1024

2019/06/20 19:06:24 storage_nvme.go:100: debug: spdk setup with _TARGET_USER=root

$ daos_server storage scan

[…]

NVMe:

- model: 'INTEL SSDPED1K375GA '

  serial: 'PHKS7335009W375AGN  '

  pciaddr: 0000:87:00.0

  fwrev: E2010324

  namespaces:

  - id: 1

    capacity: 375

- model: 'INTEL SSDPEDMD016T4 '

  serial: 'CVFT5226001C1P6DGN  '

  pciaddr: 0000:da:00.0

  fwrev: 8DV10171

  namespaces:

  - id: 1

    capacity: 1600

- model: 'INTEL SSDPEDMD016T4 '

  serial: 'CVFT5506004Z1P6DGN  '

  pciaddr: 0000:81:00.0

  fwrev: 8DV10171

  namespaces:

  - id: 1

    capacity: 1600

And then populate the yaml file with the devices that you want to use, for instance:

  bdev_class: nvme

  bdev_list: ["0000:81:00.0", "0000:da:00.0"]

We are working on automatic storage configuration with CPU affinity detection, but this feature isn’t available yet.

HTH

Cheers,

Johann

looks like your daos_server was not started successfully.
you may check the details in the config file /usr/local/etc/daos_server.yml, try to change some setting to see if it can work, for example can test to comment out (add "#" to start of the line) all the "bdev_" started options.
If still cannot work, you may post your daos_server.yml and the daos log (path configured by "log_file" option, can set "log_mask: DEBUG") to jira ticket or here if jira does not work for you.

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

Hi Shengyu,

We are about to retire the quick start document in favor of the admin guide that has been integrated into the source code (https://github.com/daos-stack/daos/tree/master/doc/admin)

The documentation for format was actually landed this morning: https://github.com/daos-stack/daos/blob/master/doc/admin/deployment.md#basic-workflow

As for the -1007 error, it means that you don’t have enough space available to allocate the pool (https://github.com/daos-stack/daos/blob/master/doc/admin/troubleshooting.md#daos-errors).

How much space have you allocated with tmpfs under /mnt/daos?

Cheers,

Johann

Hello,

I got first issue resolved after run: $ daos_shell storage format

I think you could add this step into the quick start document.

Yes I have already created daos_server.yml, from the one at install/etc/daos_server.yml.

Now the storage server seems formatted, but there is new issue happen :

When I run dmg create, it encounter another issue :

failed to create pool: -1007
-------------------------------------------------------
Primary job  terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
-------------------------------------------------------
--------------------------------------------------------------------------
orterun detected that one or more processes exited with non-zero status, thus causing
the job to be terminated. The first process to do so was:

  Process name: [[27363,1],0]
  Exit code:    1

If I execute: daos_shell pool create –s 1G

It says:

2019/06/21 17:29:19 config.go:122: debug: DAOS Client config read from /usr/local/etc/daos.yml

Active connections: [localhost:10001]

Creating DAOS pool with 1GB SCM and 0B NvMe storage (1.000 ratio)

parsing rank list: element 0: strconv.ParseUint: parsing "": invalid syntax

I’m trying to resolve by my ways, any hints will be appreciated.

Regards,

Shengyu

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

I’m afraid the patch for this has not landed yet (regarding the handling of the request), it’s going through a round of reviews, https://github.com/daos-stack/daos/pull/637 .

Please feel free to experiment with the patch, as it should work, otherwise please use the "dmg" tool to create pools in the interim

Hello,

I got first issue resolved after run: $ daos_shell storage format

I think you could add this step into the quick start document.

Yes I have already created daos_server.yml, from the one at install/etc/daos_server.yml.

Now the storage server seems formatted, but there is new issue happen :

When I run dmg create, it encounter another issue :

failed to create pool: -1007
-------------------------------------------------------
Primary job  terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
-------------------------------------------------------
--------------------------------------------------------------------------
orterun detected that one or more processes exited with non-zero status, thus causing
the job to be terminated. The first process to do so was:

  Process name: [[27363,1],0]
  Exit code:    1

If I execute: daos_shell pool create –s 1G

It says:

2019/06/21 17:29:19 config.go:122: debug: DAOS Client config read from /usr/local/etc/daos.yml

Active connections: [localhost:10001]

Creating DAOS pool with 1GB SCM and 0B NvMe storage (1.000 ratio)

parsing rank list: element 0: strconv.ParseUint: parsing "": invalid syntax

I’m trying to resolve by my ways, any hints will be appreciated.

Regards,

Shengyu

Right, the storage engine isn’t started since the backend storage hasn’t been formatted:

waiting for storage format on server 0

Even with no NVDIMMs in the system, we still need to wipe out the SSDs so that all blocks are marked as not allocated (i.e. for wear leveling). The following command should allow you to format & start the engine:

$ daos_shell storage format

As suggested by Xuezhao, you should create your own daos_server.yml with the list of SSDs you want to use.

To list the SSDs available on the system, you can run the following commands:

$ daos_server storage prep-nvme

2019/06/20 19:06:24 storage_nvme.go:96: debug: spdk setup with _NRHUGE=1024

2019/06/20 19:06:24 storage_nvme.go:100: debug: spdk setup with _TARGET_USER=root

$ daos_server storage scan

[…]

NVMe:

- model: 'INTEL SSDPED1K375GA '

  serial: 'PHKS7335009W375AGN  '

  pciaddr: 0000:87:00.0

  fwrev: E2010324

  namespaces:

  - id: 1

    capacity: 375

- model: 'INTEL SSDPEDMD016T4 '

  serial: 'CVFT5226001C1P6DGN  '

  pciaddr: 0000:da:00.0

  fwrev: 8DV10171

  namespaces:

  - id: 1

    capacity: 1600

- model: 'INTEL SSDPEDMD016T4 '

  serial: 'CVFT5506004Z1P6DGN  '

  pciaddr: 0000:81:00.0

  fwrev: 8DV10171

  namespaces:

  - id: 1

    capacity: 1600

And then populate the yaml file with the devices that you want to use, for instance:

  bdev_class: nvme

  bdev_list: ["0000:81:00.0", "0000:da:00.0"]

We are working on automatic storage configuration with CPU affinity detection, but this feature isn’t available yet.

HTH

Cheers,

Johann

looks like your daos_server was not started successfully.
you may check the details in the config file /usr/local/etc/daos_server.yml, try to change some setting to see if it can work, for example can test to comment out (add "#" to start of the line) all the "bdev_" started options.
If still cannot work, you may post your daos_server.yml and the daos log (path configured by "log_file" option, can set "log_mask: DEBUG") to jira ticket or here if jira does not work for you.

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

Hello Tom,

Thank you for the infor.

Now I’m able to create storage pool, via dmg tool, I’ll try the patch later time when I need.

Regards,

Shengyu.

I’m afraid the patch for this has not landed yet (regarding the handling of the request), it’s going through a round of reviews, https://github.com/daos-stack/daos/pull/637 .

Please feel free to experiment with the patch, as it should work, otherwise please use the "dmg" tool to create pools in the interim

Hello,

I got first issue resolved after run: $ daos_shell storage format

I think you could add this step into the quick start document.

Yes I have already created daos_server.yml, from the one at install/etc/daos_server.yml.

Now the storage server seems formatted, but there is new issue happen :

When I run dmg create, it encounter another issue :

failed to create pool: -1007
-------------------------------------------------------
Primary job  terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
-------------------------------------------------------
--------------------------------------------------------------------------
orterun detected that one or more processes exited with non-zero status, thus causing
the job to be terminated. The first process to do so was:

  Process name: [[27363,1],0]
  Exit code:    1

If I execute: daos_shell pool create –s 1G

It says:

2019/06/21 17:29:19 config.go:122: debug: DAOS Client config read from /usr/local/etc/daos.yml

Active connections: [localhost:10001]

Creating DAOS pool with 1GB SCM and 0B NvMe storage (1.000 ratio)

parsing rank list: element 0: strconv.ParseUint: parsing "": invalid syntax

I’m trying to resolve by my ways, any hints will be appreciated.

Regards,

Shengyu

Right, the storage engine isn’t started since the backend storage hasn’t been formatted:

waiting for storage format on server 0

Even with no NVDIMMs in the system, we still need to wipe out the SSDs so that all blocks are marked as not allocated (i.e. for wear leveling). The following command should allow you to format & start the engine:

$ daos_shell storage format

As suggested by Xuezhao, you should create your own daos_server.yml with the list of SSDs you want to use.

To list the SSDs available on the system, you can run the following commands:

$ daos_server storage prep-nvme

2019/06/20 19:06:24 storage_nvme.go:96: debug: spdk setup with _NRHUGE=1024

2019/06/20 19:06:24 storage_nvme.go:100: debug: spdk setup with _TARGET_USER=root

$ daos_server storage scan

[…]

NVMe:

- model: 'INTEL SSDPED1K375GA '

  serial: 'PHKS7335009W375AGN  '

  pciaddr: 0000:87:00.0

  fwrev: E2010324

  namespaces:

  - id: 1

    capacity: 375

- model: 'INTEL SSDPEDMD016T4 '

  serial: 'CVFT5226001C1P6DGN  '

  pciaddr: 0000:da:00.0

  fwrev: 8DV10171

  namespaces:

  - id: 1

    capacity: 1600

- model: 'INTEL SSDPEDMD016T4 '

  serial: 'CVFT5506004Z1P6DGN  '

  pciaddr: 0000:81:00.0

  fwrev: 8DV10171

  namespaces:

  - id: 1

    capacity: 1600

And then populate the yaml file with the devices that you want to use, for instance:

  bdev_class: nvme

  bdev_list: ["0000:81:00.0", "0000:da:00.0"]

We are working on automatic storage configuration with CPU affinity detection, but this feature isn’t available yet.

HTH

Cheers,

Johann

looks like your daos_server was not started successfully.
you may check the details in the config file /usr/local/etc/daos_server.yml, try to change some setting to see if it can work, for example can test to comment out (add "#" to start of the line) all the "bdev_" started options.
If still cannot work, you may post your daos_server.yml and the daos log (path configured by "log_file" option, can set "log_mask: DEBUG") to jira ticket or here if jira does not work for you.

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

Hello Tom,

Thank you for the infor.

Now I’m able to create storage pool, via dmg tool, I’ll try the patch later time when I need.

Regards,

Shengyu.

I’m afraid the patch for this has not landed yet (regarding the handling of the request), it’s going through a round of reviews, https://github.com/daos-stack/daos/pull/637 .

Please feel free to experiment with the patch, as it should work, otherwise please use the "dmg" tool to create pools in the interim

Hello,

I got first issue resolved after run: $ daos_shell storage format

I think you could add this step into the quick start document.

Yes I have already created daos_server.yml, from the one at install/etc/daos_server.yml.

Now the storage server seems formatted, but there is new issue happen :

When I run dmg create, it encounter another issue :

failed to create pool: -1007
-------------------------------------------------------
Primary job  terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
-------------------------------------------------------
--------------------------------------------------------------------------
orterun detected that one or more processes exited with non-zero status, thus causing
the job to be terminated. The first process to do so was:

  Process name: [[27363,1],0]
  Exit code:    1

If I execute: daos_shell pool create –s 1G

It says:

2019/06/21 17:29:19 config.go:122: debug: DAOS Client config read from /usr/local/etc/daos.yml

Active connections: [localhost:10001]

Creating DAOS pool with 1GB SCM and 0B NvMe storage (1.000 ratio)

parsing rank list: element 0: strconv.ParseUint: parsing "": invalid syntax

I’m trying to resolve by my ways, any hints will be appreciated.

Regards,

Shengyu

Right, the storage engine isn’t started since the backend storage hasn’t been formatted:

waiting for storage format on server 0

Even with no NVDIMMs in the system, we still need to wipe out the SSDs so that all blocks are marked as not allocated (i.e. for wear leveling). The following command should allow you to format & start the engine:

$ daos_shell storage format

As suggested by Xuezhao, you should create your own daos_server.yml with the list of SSDs you want to use.

To list the SSDs available on the system, you can run the following commands:

$ daos_server storage prep-nvme

2019/06/20 19:06:24 storage_nvme.go:96: debug: spdk setup with _NRHUGE=1024

2019/06/20 19:06:24 storage_nvme.go:100: debug: spdk setup with _TARGET_USER=root

$ daos_server storage scan

[…]

NVMe:

- model: 'INTEL SSDPED1K375GA '

  serial: 'PHKS7335009W375AGN  '

  pciaddr: 0000:87:00.0

  fwrev: E2010324

  namespaces:

  - id: 1

    capacity: 375

- model: 'INTEL SSDPEDMD016T4 '

  serial: 'CVFT5226001C1P6DGN  '

  pciaddr: 0000:da:00.0

  fwrev: 8DV10171

  namespaces:

  - id: 1

    capacity: 1600

- model: 'INTEL SSDPEDMD016T4 '

  serial: 'CVFT5506004Z1P6DGN  '

  pciaddr: 0000:81:00.0

  fwrev: 8DV10171

  namespaces:

  - id: 1

    capacity: 1600

And then populate the yaml file with the devices that you want to use, for instance:

  bdev_class: nvme

  bdev_list: ["0000:81:00.0", "0000:da:00.0"]

We are working on automatic storage configuration with CPU affinity detection, but this feature isn’t available yet.

HTH

Cheers,

Johann

looks like your daos_server was not started successfully.
you may check the details in the config file /usr/local/etc/daos_server.yml, try to change some setting to see if it can work, for example can test to comment out (add "#" to start of the line) all the "bdev_" started options.
If still cannot work, you may post your daos_server.yml and the daos log (path configured by "log_file" option, can set "log_mask: DEBUG") to jira ticket or here if jira does not work for you.

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

Hi Shengyu,

I assume that you have followed the instructions to set up /var/run/daos_agent, correct?

If not, please check https://github.com/daos-stack/daos/blob/master/doc/admin/deployment.md#runtime-directory-setup

We also landed support for the daos_agent to v0.5 (David sent an email to the list), but the admin guide hasn’t been updated yet:

https://github.com/daos-stack/daos/blob/master/doc/admin/deployment.md#agent-configuration

On the compute nodes, you should just run “daos_agent &”. A systemd script to automate this should be available soon.

David, could you please submit a PR to document in the admin guide how to setup & start the daos_agent? Thanks in advance.

Cheers,

Johann

Hello,

I hope to get additional help in how to make DAOS working in its ecosystem, run it fuse, or hdfs, or testing for iops.

dmg query and fuse not work in my environment, and I noticed the admin document of DAOS is mismatch with code of fuse part.

Pool created OK however dmg query and fuse mount always returns invalid parameters error code (1003).

orterun … dmg query --pool 06c10125-c3ea-4040-a030-10a9e5f10004 --svc 1

Therefor as for now if I can get any guides to test/run DAOS in its ecosystem is better to learn more about the project, any information will be appreciated.

Best Regards,

Shengyu

Hello Tom,

Thank you for the infor.

Now I’m able to create storage pool, via dmg tool, I’ll try the patch later time when I need.

Regards,

Shengyu.

I’m afraid the patch for this has not landed yet (regarding the handling of the request), it’s going through a round of reviews, https://github.com/daos-stack/daos/pull/637 .

Please feel free to experiment with the patch, as it should work, otherwise please use the "dmg" tool to create pools in the interim

Hello,

I got first issue resolved after run: $ daos_shell storage format

I think you could add this step into the quick start document.

Yes I have already created daos_server.yml, from the one at install/etc/daos_server.yml.

Now the storage server seems formatted, but there is new issue happen :

When I run dmg create, it encounter another issue :

failed to create pool: -1007
-------------------------------------------------------
Primary job  terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
-------------------------------------------------------
--------------------------------------------------------------------------
orterun detected that one or more processes exited with non-zero status, thus causing
the job to be terminated. The first process to do so was:

  Process name: [[27363,1],0]
  Exit code:    1

If I execute: daos_shell pool create –s 1G

It says:

2019/06/21 17:29:19 config.go:122: debug: DAOS Client config read from /usr/local/etc/daos.yml

Active connections: [localhost:10001]

Creating DAOS pool with 1GB SCM and 0B NvMe storage (1.000 ratio)

parsing rank list: element 0: strconv.ParseUint: parsing "": invalid syntax

I’m trying to resolve by my ways, any hints will be appreciated.

Regards,

Shengyu

Right, the storage engine isn’t started since the backend storage hasn’t been formatted:

waiting for storage format on server 0

Even with no NVDIMMs in the system, we still need to wipe out the SSDs so that all blocks are marked as not allocated (i.e. for wear leveling). The following command should allow you to format & start the engine:

$ daos_shell storage format

As suggested by Xuezhao, you should create your own daos_server.yml with the list of SSDs you want to use.

To list the SSDs available on the system, you can run the following commands:

$ daos_server storage prep-nvme

2019/06/20 19:06:24 storage_nvme.go:96: debug: spdk setup with _NRHUGE=1024

2019/06/20 19:06:24 storage_nvme.go:100: debug: spdk setup with _TARGET_USER=root

$ daos_server storage scan

[…]

NVMe:

- model: 'INTEL SSDPED1K375GA '

  serial: 'PHKS7335009W375AGN  '

  pciaddr: 0000:87:00.0

  fwrev: E2010324

  namespaces:

  - id: 1

    capacity: 375

- model: 'INTEL SSDPEDMD016T4 '

  serial: 'CVFT5226001C1P6DGN  '

  pciaddr: 0000:da:00.0

  fwrev: 8DV10171

  namespaces:

  - id: 1

    capacity: 1600

- model: 'INTEL SSDPEDMD016T4 '

  serial: 'CVFT5506004Z1P6DGN  '

  pciaddr: 0000:81:00.0

  fwrev: 8DV10171

  namespaces:

  - id: 1

    capacity: 1600

And then populate the yaml file with the devices that you want to use, for instance:

  bdev_class: nvme

  bdev_list: ["0000:81:00.0", "0000:da:00.0"]

We are working on automatic storage configuration with CPU affinity detection, but this feature isn’t available yet.

HTH

Cheers,

Johann

looks like your daos_server was not started successfully.
you may check the details in the config file /usr/local/etc/daos_server.yml, try to change some setting to see if it can work, for example can test to comment out (add "#" to start of the line) all the "bdev_" started options.
If still cannot work, you may post your daos_server.yml and the daos log (path configured by "log_file" option, can set "log_mask: DEBUG") to jira ticket or here if jira does not work for you.

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

Hi,

I am trying to build using Docker on Mac. I am seeing the following error:

$ docker build -t daos -f Dockerfile.centos\:7 github.com/daos-stack/daos#:utils/docker

unable to prepare context: unable to 'git clone' to temporary context directory: error initializing submodules: Submodule 'scons_local' (https://github.com/daos-stack/scons_local.git) registered for path 'scons_local'

Submodule 'raft' (https://github.com/daos-stack/raft.git) registered for path 'src/rdb/raft'

https://groups.io

Cloning into '/private/var/folders/b5/b52tjd4j71z15bj53sms7jrw006f5s/T/docker-build-git049590752/scons_local'...

Cloning into '/private/var/folders/b5/b52tjd4j71z15bj53sms7jrw006f5s/T/docker-build-git049590752/src/rdb/raft'...

error: Server does not allow request for unadvertised object 171c9b254d9c40463c77d7e7567fd93633a9d78a

Fetched in submodule path 'scons_local', but it did not contain 171c9b254d9c40463c77d7e7567fd93633a9d78a. Direct fetching of that commit failed.

: exit status 1

Thanks.

Colin

Hi,

I am trying to build using Docker on Mac. I am seeing the following error:

$ docker build -t daos -f Dockerfile.centos\:7 github.com/daos-stack/daos#:utils/docker

unable to prepare context: unable to 'git clone' to temporary context directory: error initializing submodules: Submodule 'scons_local' (https://github.com/daos-stack/scons_local.git) registered for path 'scons_local'

Submodule 'raft' (https://github.com/daos-stack/raft.git) registered for path 'src/rdb/raft'

https://groups.io

Cloning into '/private/var/folders/b5/b52tjd4j71z15bj53sms7jrw006f5s/T/docker-build-git049590752/scons_local'...

Cloning into '/private/var/folders/b5/b52tjd4j71z15bj53sms7jrw006f5s/T/docker-build-git049590752/src/rdb/raft'...

error: Server does not allow request for unadvertised object 171c9b254d9c40463c77d7e7567fd93633a9d78a

Fetched in submodule path 'scons_local', but it did not contain 171c9b254d9c40463c77d7e7567fd93633a9d78a. Direct fetching of that commit failed.

: exit status 1

Thanks.

Colin

Hi,

I can do this manually:

cngam@cngam daos $ git clone https://github.com/daos-stack/daos.git

Cloning into 'daos'...

remote: Enumerating objects: 229, done.

remote: Counting objects: 100% (229/229), done.

remote: Compressing objects: 100% (201/201), done.

remote: Total 35637 (delta 103), reused 64 (delta 28), pack-reused 35408

Receiving objects: 100% (35637/35637), 24.55 MiB | 6.29 MiB/s, done.

Resolving deltas: 100% (27005/27005), done.

cngam@cngam daos $ cd daos

cngam@cngam daos $ git submodule init

Submodule 'scons_local' (https://github.com/daos-stack/scons_local.git) registered for path 'scons_local'

Submodule 'raft' (https://github.com/daos-stack/raft.git) registered for path 'src/rdb/raft'

cngam@cngam daos $ git submodule update

Cloning into '/Users/cngam/DAOS/daos/scons_local'...

Cloning into '/Users/cngam/DAOS/daos/src/rdb/raft'...

Submodule path 'scons_local': checked out '171c9b254d9c40463c77d7e7567fd93633a9d78a'

Submodule path 'src/rdb/raft': checked out 'e6c4369635d5ca8cbe71173eb4eb15fb3809510f'

So, I do not believe it is a https proxy issue.

Thanks.

Colin

Hi Colin,

I’ve not seen that before but after cloning DAOS, the build should be doing a git submodule update which would clone scons_local and raft submodules using the urls you see in the messages.   The scons_local repository has that git hash so I’m wondering if something is happening at the initial clone step.  Do you have an https proxy that needs to be set perhaps?

-Jeff

Hi,

I am trying to build using Docker on Mac. I am seeing the following error:

$ docker build -t daos -f Dockerfile.centos\:7 github.com/daos-stack/daos#:utils/docker

unable to prepare context: unable to 'git clone' to temporary context directory: error initializing submodules: Submodule 'scons_local' (https://github.com/daos-stack/scons_local.git) registered for path 'scons_local'

Submodule 'raft' (https://github.com/daos-stack/raft.git) registered for path 'src/rdb/raft'

https://groups.io

Cloning into '/private/var/folders/b5/b52tjd4j71z15bj53sms7jrw006f5s/T/docker-build-git049590752/scons_local'...

Cloning into '/private/var/folders/b5/b52tjd4j71z15bj53sms7jrw006f5s/T/docker-build-git049590752/src/rdb/raft'...

error: Server does not allow request for unadvertised object 171c9b254d9c40463c77d7e7567fd93633a9d78a

Fetched in submodule path 'scons_local', but it did not contain 171c9b254d9c40463c77d7e7567fd93633a9d78a. Direct fetching of that commit failed.

: exit status 1

Thanks.

Colin