Managing Shares

Shares are created for Filesystem-type volumes in vStor. When creating a Filesystem volume, you’re prompted to establish a share.

Prerequisites

• A filesystem-type volume must exist or be created.

• Hosts should be network accessible.

Creating a new share using the vStor Web Interface

1. Open the vStor Web Interface at https://<vStor_hostname_or_IP>:8900.

2. Log in as admin.

3. In the navigation menu, click Storage and locate a Filesystem volume.

4. Click More Actions (•••) and select Share.

5. In the New share volume dialog:

   • For nfs: Choose Read-only, All hosts for universal access, or Add Host for specific IPs.

6. Click OK to add the share.

Note. An NFS and SMB share cannot exist for the same volume simultaneously.

After completing the steps, a share is established. Click Shares in the navigation pane and the share will appear in the Shares table.

Creating a new share using vStor CLI

1. Show the list of defined volumes using:

vstor volume show

This command will return the following output:

ID | TYPE       | POOL | IS CLONE | TOTAL   | FREE    | USED     | NAME
-------------------------------------------------------------------------
1  | filesystem | 1    | No       | 96.39GB | 96.39GB | 421.00KB | v1
2  | filesystem | 1    | No       | 96.39GB | 96.39GB | 53.00KB  | v2
3  | lun        | 1    | No       | 64.00KB | 52.00KB | 12.00KB  | lun1 
5  | filesystem | 1    | No       | 96.39GB | 96.39GB | 24.00KB  | myvol1

1. Create a share for a selected volume using:

vstor share create --vol_id=5 --share_type=nfs –-allowed_hosts all

Alternatively, use:

vstor share create --vol_id=5 --share_type=nfs –-allowed_hosts  <comma separated IP address list>

The output of this command is structured in the following way:

ID: 3
NAME: /vstor/vpool1/fs5
SHARE TYPE: nfs
VOLUME ID: 5
CREATED: 2018-01-26 21:23:46 UTC
UPDATED: 2018-01-26 21:23:46 UTC
SHARE OPTIONS: ALLOWED HOSTS: all

Note. --share_type nfs is the only share type supported by DPX.

Attention! Do not use --read_only as a share should not be read-only.