command-line-murders/i-02706fb8ea9a8cc1e
by SadServersMore by SadServers
udev 217M 0 217M 0% /dev tmpfs 46M 368K 46M 1% /run /dev/nvme0n1p1 7.7G 6.1G 1.2G 84% / tmpfs 228M 12K 228M 1% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock /dev/nvme0n1p15 124M 5.9M 118M 5% /boot/efi admin@i-0a305a3ca8eeb45e2:~$ df -h Filesystem Size Used Avail Use% Mounted on udev 217M 0 217M 0% /dev tmpfs 46M 368K 46M 1% /run /dev/nvme0n1p1 7.7G 6.1G 1.2G 84% / tmpfs 228M 12K 228M 1% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock /dev/nvme0n1p15 124M 5.9M 118M 5% /boot/efi admin@i-0a305a3ca8eeb45e2:~$ df
kihei/i-0a305a3ca8eeb45e2 01:18
by SadServersculated as: metadata area start (page size), plus the specified --metadat With metadata starting at 4 KiB, --metadatasize 2048k, and --dataalign pe_start of 2176 KiB is the nearest even multiple of 128 KiB that provide sulting alignment and metadata size when using these options. To shift an aligned pe_start value, use the --dataaligmentoffset option. then the value specified with --dataaligmentoffset is added to produce th USAGE pvcreate PV ... [ -f|--force ] [ -M|--metadatatype lvm2 ] [ -u|--uuid String ] [ -Z|--zero y|n ] Manual page pvcreate(8) line 32 (press h for help or q to quit)
kihei/i-0712eec9ea1e11d0e 08:23
by SadServersDisk /dev/nvme1n1: 1 GiB, 1073741824 bytes, 2097152 sectors Disk model: Amazon Elastic Block Store Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/nvme2n1: 1 GiB, 1073741824 bytes, 2097152 sectors Disk model: Amazon Elastic Block Store Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes admin@i-0e7c2b35017230040:~$ mount /dev/nvme1 nvme1 nvme1n1 admin@i-0e7c2b35017230040:~$ mount /dev/nvme1