New-PveNodesDisksZfs
Create a ZFS pool.
API: POST /nodes/{node}/disks/zfs, Proxmox VE API viewer
Syntax
Section titled “Syntax”New-PveNodesDisksZfs [-PveTicket <PveTicket>] [-AddStorage <bool>] [-Ashift <int>] [-Compression <string>] -Devices <string> [-DraidConfig <string>] -Name <string> -Node <string> -Raidlevel <string> [<CommonParameters>]Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
-PveTicket |
PveTicket |
No | Ticket data connection. |
-AddStorage |
bool |
No | Configure storage using the zpool. |
-Ashift |
int |
No | Pool sector size exponent. |
-Compression |
string |
No | The compression algorithm to use. Values: on, off, gzip, lz4, lzjb, zle, zstd. |
-Devices |
string |
Yes | The block devices you want to create the zpool on. |
-DraidConfig |
string |
No | |
-Name |
string |
Yes | The storage identifier. |
-Node |
string |
Yes | The cluster node name. |
-Raidlevel |
string |
Yes | The RAID level to use. Values: single, mirror, raid10, raidz, raidz2, raidz3, draid, draid2, draid3. |
Every parameter also binds by property name from the pipeline, so an object with node and vmid properties (the output of Get-PveGuest, for one) fills -Node and -Vmid. Without -PveTicket the cmdlet uses the last connection, see Connection.
Output
Section titled “Output”A PveResponse: the data returned by Proxmox VE is in .Response.data, the outcome in .IsSuccessStatusCode. See Results and Errors.