for: change block size from 1m to 4m (on ""addit vmfs part 11 G"))
..
USB Flash (current)
Name | Size | Allocation Unit | Write Size Unit | Page Size | FAT Location | # open AUs linear | # open AUs random | Algorithm | USB ID | Name |
Sandisk Cruzer Fit | 15,633,408 KB | 4 MB | 64 KB | 16 KB | -- | 27 * 1.33MB | 0 | linear SLC (22 MB/s), Linar MLC (5 MB/s) | 0781:5571 | SanDiskCruzer Fit 1.26 PQ: |
post before prev created ADDIT PARTITION WAS:
[root@localhost:~] ls -l /vmfs/volumes/
total 1792
drwxr-xr-x 1 root root 8 Jan 1 1970 0b6c70ea-d8b9d184-1d7f- 176591fde77e
drwxr-xr-x 1 root root 8 Jan 1 1970 42d466e4-b369e7f8-dc81- 643a620e5406
drwxr-xr-x 1 root root 8 Jan 1 1970 5695083f-631345ec-de5c- 101f744c0550
drwxr-xr-t 1 root root 1680 Jan 23 20:10 56a3bdf4-65a64697-f032- 101f744c0550
lrwxr-xr-x 1 root root 35 Jan 25 11:09 NewDatastore -> 56a3bdf 4-65a64697-f032-101f744c0550
[root@localhost:~] ls -l /vmfs/volumes/
total 1792
drwxr-xr-x 1 root root 8 Jan 1 1970 0b6c70ea-d8b9d184-1d7f-176591fde77e
drwxr-xr-x 1 root root 8 Jan 1 1970 42d466e4-b369e7f8-dc81-643a620e5406
drwxr-xr-x 1 root root 8 Jan 1 1970 5695083f-631345ec-de5c-101f744c0550
drwxr-xr-t 1 root root 1680 Jan 23 20:10 56a3bdf4-65a64697-f032-101f744c0550
lrwxr-xr-x 1 root root 35 Jan 25 11:09 NewDatastore -> 56a3bdf4-65a64697-f032-101f744c0550
[root@localhost:~] vmkfstools -P /vmfs/volumes/56a3bdf4-65a64697-f032-101f744c0550
VMFS-5.61 file system spanning 1 partitions.
File system label (if any): NewDatastore
Mode: public
Capacity 12348030976 (11776 file blocks * 1048576), 2641362944 (2519 blocks) avail, max supported file size 69201586814976
UUID: 56a3bdf4-65a64697-f032-101f744c0550
Partitions spanned (on "lvm"):
mpx.vmhba32:C0:T0:L0:10
Is Native Snapshot Capable: YES
[root@localhost:~] vmkfstools -Ph -v10 /vmfs/volumes/56a3bdf4-65a64697-f032-101f744c0550
VMFS-5.61 file system spanning 1 partitions.
File system label (if any): NewDatastore
Mode: public
Capacity 11.5 GB, 2.5 GB available, file block size 1 MB, max supported file size 62.9 TB
Volume Creation Time: Sat Jan 23 17:52:52 2016
Files (max/free): 87052/86983
Ptr Blocks (max/free): 64512/64488
Sub Blocks (max/free): 32000/31982
Secondary Ptr Blocks (max/free): 256/256
File Blocks (overcommit/used/overcommit %): 0/9257/0
Ptr Blocks (overcommit/used/overcommit %): 0/24/0
Sub Blocks (overcommit/used/overcommit %): 0/18/0
Volume Metadata size: 715481088
UUID: 56a3bdf4-65a64697-f032-101f744c0550
Logical device: 56a3bded-b45b4fdb-fba7-101f744c0550
Partitions spanned (on "lvm"):
mpx.vmhba32:C0:T0:L0:10
Is Native Snapshot Capable: YES
OBJLIB-LIB: ObjLib cleanup done.
WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0
[root@localhost:~]
============================
but "
http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1003565
The limits that apply to VMFS-5 datastores are:
In VMFS-5, very small files (that is, files smaller than 1 KB) will be stored in the file descriptor location in the metadata rather than using file blocks. Once the file size increases beyond 1 KB, sub-blocks are used. After one 8 KB sub-block is used, 1 MB file blocks are used. As VMFS-5 uses sub-blocks of 8 KB rather than 64 KB (as in VMFS-3), this reduces the amount of disk space being used by small files. For more information on VMFS-5, see vSphere 5 FAQ: VMFS-5 (2003813).
http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1003565
VMFS-5 Size Limitations
With VMFS-5, we use a unified 1 MB block size which is no longer configurable, but we can address larger files than a VMFS-3 1 MB block size can due to enhancements to the VMFS file system. Therefore a 1 MB VMFS-3 block size is not the same as a 1 MB VMFS-5 block size regarding file sizes.The limits that apply to VMFS-5 datastores are:
- The maximum virtual disk (VMDK) size is 2 TB minus 512 B for ESXi 5.0 and 5.1. In ESXi 5.5, the size is increased to 62TB.
- The maximum virtual-mode RDM (vRDM) size is 2 TB minus 512 B for ESXi 5.0 and 5.1. In ESXi 5.5, the size is increased to 62TB.
- Physical-mode RDMs are supported up to 64 TB.
In VMFS-5, very small files (that is, files smaller than 1 KB) will be stored in the file descriptor location in the metadata rather than using file blocks. Once the file size increases beyond 1 KB, sub-blocks are used. After one 8 KB sub-block is used, 1 MB file blocks are used. As VMFS-5 uses sub-blocks of 8 KB rather than 64 KB (as in VMFS-3), this reduces the amount of disk space being used by small files. For more information on VMFS-5, see vSphere 5 FAQ: VMFS-5 (2003813).
=============
TARGET: BLOCK SIZE 4m
======
AGAIN:
reinstall esxi ))) (created in prev post)
TARGET: BLOCK SIZE 4m
======
AGAIN:
reinstall esxi ))) (created in prev post)
AND:
Using username "root".
Using keyboard-interactive authentication.
Password:
The time and date of this login have been sent to the system logs.
VMware offers supported, powerful system administration tools. Please
see www.vmware.com/go/sysadmintools for details.
The ESXi Shell can be disabled by an administrative user. See the
vSphere Security documentation for more information.
[root@esxi:~] esxcli storage core device list
mpx.vmhba32:C0:T0:L0
Display Name: Local USB Direct-Access (mpx.vmhba32:C0:T0:L0)
Has Settable Display Name: false
Size: 15267
Device Type: Direct-Access
Multipath Plugin: NMP
Devfs Path: /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0
Vendor: SanDisk
Model: Cruzer Fit
Revision: 1.27
SCSI Level: 2
Is Pseudo: false
Status: on
Is RDM Capable: false
Is Local: true
Is Removable: true
Is SSD: false
Is VVOL PE: false
Is Offline: false
Is Perennially Reserved: false
Queue Full Sample Size: 0
Queue Full Threshold: 0
Thin Provisioning Status: unknown
Attached Filters:
VAAI Status: unsupported
Other UIDs: vml.0000000000766d68626133323a303a30
Is Shared Clusterwide: false
Is Local SAS Device: false
Is SAS: false
Is USB: true
Is Boot USB Device: true
Is Boot Device: true
Device Max Queue Depth: 1
No of outstanding IOs with competing worlds: 32
Drive Type: unknown
RAID Level: unknown
Number of Physical Drives: unknown
Protection Enabled: false
PI Activated: false
PI Type: 0
PI Protection Mask: NO PROTECTION
Supported Guard Types: NO GUARD SUPPORT
DIX Enabled: false
DIX Guard Type: NO GUARD SUPPORT
Emulated DIX/DIF Enabled: false
[root@esxi:~] partedUtil getptbl "/vmfs/devices/disks/mpx.vmhba32:C0:T0:L0"
gpt
1946 255 63 31266816
1 64 8191 C12A7328F81F11D2BA4B00A0C93EC93B systemPartition 128
5 8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
6 520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
7 1032224 1257471 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0
8 1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
9 1843200 7086079 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0
[root@esxi:~] partedUtil setptbl "/vmfs/devices/disks/mpx.vmhba32:C0:T0:L0" gpt "1 64 8191 C12A7328F81F11D2BA4B00A0C93EC93B 128" "
5 8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 0" "6 520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 0" "7 1032224 1257471 9D27538
040AD11DBBF97000C2911D1B8 0" "8 1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 0" "9 1843200 7086079 9D27538040AD11DBBF97000C291
1D1B8 0" "10 7086080 31264767 AA31E02A400F11DB9590000C2911D1B8 0"
gpt
0 0 0 0
1 64 8191 C12A7328F81F11D2BA4B00A0C93EC93B 128
5 8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 0
6 520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 0
7 1032224 1257471 9D27538040AD11DBBF97000C2911D1B8 0
8 1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 0
9 1843200 7086079 9D27538040AD11DBBF97000C2911D1B8 0
10 7086080 31264767 AA31E02A400F11DB9590000C2911D1B8 0
[root@esxi:~] partedUtil getptbl "/vmfs/devices/disks/mpx.vmhba32:C0:T0:L0"
gpt
1946 255 63 31266816
1 64 8191 C12A7328F81F11D2BA4B00A0C93EC93B systemPartition 128
5 8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
6 520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
7 1032224 1257471 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0
8 1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
9 1843200 7086079 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0
10 7086080 31264767 AA31E02A400F11DB9590000C2911D1B8 vmfs 0
[root@esxi:~] vmkfstools -C vmfs5 -b 4m -S Datastore4m
Invalid destination specification:
vmkfstools: Argument missing
[root@esxi:~] vmkfstools -C vmfs5 -b 4m -S Datastore4m /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0:10
create fs deviceName:'/vmfs/devices/disks/mpx.vmhba32:C0:T0:L0:10', fsShortName:'vmfs5', fsName:'Datastore4m'
deviceFullPath:/dev/disks/mpx.vmhba32:C0:T0:L0:10 deviceFile:mpx.vmhba32:C0:T0:L0:10
Invalid fileBlockSize 4194304. VMFS 5 doesn't support file blocks greater than 1MB
Usage: vmkfstools -C [vmfs5|vfat] /vmfs/devices/disks/vml... or,
vmkfstools -C [vmfs5|vfat] /vmfs/devices/disks/naa... or,
vmkfstools -C [vmfs5|vfat] /vmfs/devices/disks/mpx.vmhbaA:T:L:P
Error: Invalid argument
[root@esxi:~] ls -l /vmfs/volumes/
total 768
drwxr-xr-x 1 root root 8 Jan 1 1970 1e7934e3-47d70b38-1615-5dbf5e04c594
drwxr-xr-x 1 root root 8 Jan 1 1970 56a610da-cc6be0e4-7bfa-101f744c0550
drwxr-xr-x 1 root root 8 Jan 1 1970 f3716ce3-2e47c11d-b1ff-40e92ad34166
[root@esxi:~] df
Filesystem Bytes Used Available Use% Mounted on
vfat 261853184 169873408 91979776 65% /vmfs/volumes/1e7934e3-47d70b38-1615-5dbf5e04c594
vfat 261853184 8192 261844992 0% /vmfs/volumes/f3716ce3-2e47c11d-b1ff-40e92ad34166
vfat 299712512 211386368 88326144 71% /vmfs/volumes/56a610da-cc6be0e4-7bfa-101f744c0550
[root@esxi:~] vmkfstools -Ph -v10 /vmfs/volumes/1e7934e3-47d70b38-1615-5dbf5e04c594
Could not retrieve max file size: Inappropriate ioctl for device
vfat-0.04 file system spanning 1 partitions.
File system label (if any):
Mode: private
Capacity 249.7 MB, 87.7 MB available, file block size 4 KB, max supported file size 0 bytes
UUID: 1e7934e3-47d70b38-1615-5dbf5e04c594
Logical device: mpx.vmhba32:C0:T0:L0:5
Partitions spanned (on "disks"):
mpx.vmhba32:C0:T0:L0:5
Is Native Snapshot Capable: NO
OBJLIB-LIB: ObjLib cleanup done.
WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0
[root@esxi:~] vmkfstools -Ph -v10 /vmfs/volumes/56a610da-cc6be0e4-7bfa-101f744c0550
Could not retrieve max file size: Inappropriate ioctl for device
vfat-0.04 file system spanning 1 partitions.
File system label (if any):
Mode: private
Capacity 285.8 MB, 84.2 MB available, file block size 8 KB, max supported file size 0 bytes
UUID: 56a610da-cc6be0e4-7bfa-101f744c0550
Logical device: mpx.vmhba32:C0:T0:L0:8
Partitions spanned (on "disks"):
mpx.vmhba32:C0:T0:L0:8
Is Native Snapshot Capable: NO
OBJLIB-LIB: ObjLib cleanup done.
WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0
[root@esxi:~] vmkfstools -Ph -v10 /vmfs/volumes/f3716ce3-2e47c11d-b1ff-40e92ad34166
Could not retrieve max file size: Inappropriate ioctl for device
vfat-0.04 file system spanning 1 partitions.
File system label (if any):
Mode: private
Capacity 249.7 MB, 249.7 MB available, file block size 4 KB, max supported file size 0 bytes
UUID: f3716ce3-2e47c11d-b1ff-40e92ad34166
Logical device: mpx.vmhba32:C0:T0:L0:6
Partitions spanned (on "disks"):
mpx.vmhba32:C0:T0:L0:6
Is Native Snapshot Capable: NO
OBJLIB-LIB: ObjLib cleanup done.
WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0
[root@esxi:~] esxcfg-scsidevs -m
[root@esxi:~] vmkfstools -C vmfs3 -b 4m -S Datastore4m /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0:10
create fs deviceName:'/vmfs/devices/disks/mpx.vmhba32:C0:T0:L0:10', fsShortName:'vmfs3', fsName:'Datastore4m'
Creation of VMFS-3 is not supported.
Usage: vmkfstools -C [vmfs5|vfat] /vmfs/devices/disks/vml... or,
vmkfstools -C [vmfs5|vfat] /vmfs/devices/disks/naa... or,
vmkfstools -C [vmfs5|vfat] /vmfs/devices/disks/mpx.vmhbaA:T:L:P
Error: vmkfstools failed: vmkernel is not loaded or call not implemented.
[root@esxi:~] vmkfstools -h
No valid command specified
OPTIONS FOR FILE SYSTEMS:
vmkfstools -C --createfs [vmfs5|vfat]
-S --setfsname fsName
-Z --spanfs span-partition
-G --growfs grown-partition
deviceName
-P --queryfs -h --humanreadable
-T --upgradevmfs
vmfsPath
-y --reclaimBlocks vmfsPath [--reclaimBlocksUnit #blocks]
OPTIONS FOR VIRTUAL DISKS:
vmkfstools -c --createvirtualdisk #[bBsSkKmMgGtT]
-d --diskformat [zeroedthick
|thin
|eagerzeroedthick
]
-a --adaptertype [deprecated]
-W --objecttype [file|vsan|vvol]
--policyFile <fileName>
-w --writezeros
-j --inflatedisk
-k --eagerzero
-K --punchzero
-U --deletevirtualdisk
-E --renamevirtualdisk srcDisk
-i --clonevirtualdisk srcDisk
-d --diskformat [zeroedthick
|thin
|eagerzeroedthick
|rdm:<device>|rdmp:<device>
|2gbsparse]
-W --object [file|vsan|vvol]
--policyFile <fileName>
-N --avoidnativeclone
-X --extendvirtualdisk #[bBsSkKmMgGtT]
[-d --diskformat eagerzeroedthick]
-M --migratevirtualdisk
-r --createrdm /vmfs/devices/disks/...
-q --queryrdm
-z --createrdmpassthru /vmfs/devices/disks/...
-v --verbose #
-g --geometry
-x --fix [check|repair]
-e --chainConsistent
-Q --objecttype name/value pair
--uniqueblocks childDisk
vmfsPath
OPTIONS FOR DEVICES:
-L --lock [reserve|release|lunreset|targetreset|busreset|readkeys|readresv
] /vmfs/devices/disks/...
-B --breaklock /vmfs/devices/disks/...
vmkfstools -H --help
[root@esxi:~] vmkfstools -v -C vmfs5 -S DatastoreDefvmfs5 /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0:10
Extra arguments at the end of the command line.
OPTIONS FOR FILE SYSTEMS:
vmkfstools -C --createfs [vmfs5|vfat]
-S --setfsname fsName
-Z --spanfs span-partition
-G --growfs grown-partition
deviceName
-P --queryfs -h --humanreadable
-T --upgradevmfs
vmfsPath
-y --reclaimBlocks vmfsPath [--reclaimBlocksUnit #blocks]
OPTIONS FOR VIRTUAL DISKS:
vmkfstools -c --createvirtualdisk #[bBsSkKmMgGtT]
-d --diskformat [zeroedthick
|thin
|eagerzeroedthick
]
-a --adaptertype [deprecated]
-W --objecttype [file|vsan|vvol]
--policyFile <fileName>
-w --writezeros
-j --inflatedisk
-k --eagerzero
-K --punchzero
-U --deletevirtualdisk
-E --renamevirtualdisk srcDisk
-i --clonevirtualdisk srcDisk
-d --diskformat [zeroedthick
|thin
|eagerzeroedthick
|rdm:<device>|rdmp:<device>
|2gbsparse]
-W --object [file|vsan|vvol]
--policyFile <fileName>
-N --avoidnativeclone
-X --extendvirtualdisk #[bBsSkKmMgGtT]
[-d --diskformat eagerzeroedthick]
-M --migratevirtualdisk
-r --createrdm /vmfs/devices/disks/...
-q --queryrdm
-z --createrdmpassthru /vmfs/devices/disks/...
-v --verbose #
-g --geometry
-x --fix [check|repair]
-e --chainConsistent
-Q --objecttype name/value pair
--uniqueblocks childDisk
vmfsPath
OPTIONS FOR DEVICES:
-L --lock [reserve|release|lunreset|targetreset|busreset|readkeys|readresv
] /vmfs/devices/disks/...
-B --breaklock /vmfs/devices/disks/...
vmkfstools -H --help
[root@esxi:~] vmkfstools -C vmfs5 -S DatastoreDefvmfs5 /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0:10
create fs deviceName:'/vmfs/devices/disks/mpx.vmhba32:C0:T0:L0:10', fsShortName:'vmfs5', fsName:'DatastoreDefvmfs5'
deviceFullPath:/dev/disks/mpx.vmhba32:C0:T0:L0:10 deviceFile:mpx.vmhba32:C0:T0:L0:10
ATS on device /dev/disks/mpx.vmhba32:C0:T0:L0:10: not supported
.
Checking if remote hosts are using this device as a valid file system. This may take a few seconds...
Creating vmfs5 file system on "mpx.vmhba32:C0:T0:L0:10" with blockSize 1048576 and volume label "DatastoreDefvmfs5".
Successfully created new volume: 56a64f12-82285a62-4f3f-101f744c0550
[root@esxi:~] vmkfstools -V
[root@esxi:~] ls -la /vmfs/volumes/
total 1796
drwxr-xr-x 1 root root 512 Jan 25 16:39 .
drwxr-xr-x 1 root root 512 Jan 25 15:07 ..
drwxr-xr-x 1 root root 8 Jan 1 1970 1e7934e3-47d70b38-1615-5dbf5e04c594
drwxr-xr-x 1 root root 8 Jan 1 1970 56a610da-cc6be0e4-7bfa-101f744c0550
drwxr-xr-t 1 root root 1260 Jan 25 16:36 56a64f12-82285a62-4f3f-101f744c0550
lrwxr-xr-x 1 root root 35 Jan 25 16:39 DatastoreDefvmfs5 -> 56a64f12-82285a62-4f3f-101f744c0550
drwxr-xr-x 1 root root 8 Jan 1 1970 f3716ce3-2e47c11d-b1ff-40e92ad34166
[root@esxi:~] vmkfstools -Ph -v10 /vmfs/volumes/56a64f12-82285a62-4f3f-101f744c0550
VMFS-5.61 file system spanning 1 partitions.
File system label (if any): DatastoreDefvmfs5
Mode: public
Capacity 11.5 GB, 10.6 GB available, file block size 1 MB, max supported file size 62.9 TB
Volume Creation Time: Mon Jan 25 16:36:34 2016
Files (max/free): 87052/87044
Ptr Blocks (max/free): 64512/64496
Sub Blocks (max/free): 32000/32000
Secondary Ptr Blocks (max/free): 256/256
File Blocks (overcommit/used/overcommit %): 0/888/0
Ptr Blocks (overcommit/used/overcommit %): 0/16/0
Sub Blocks (overcommit/used/overcommit %): 0/0/0
Volume Metadata size: 715481088
UUID: 56a64f12-82285a62-4f3f-101f744c0550
Logical device: 56a64f0b-cd78de55-808f-101f744c0550
Partitions spanned (on "lvm"):
mpx.vmhba32:C0:T0:L0:10
Is Native Snapshot Capable: YES
OBJLIB-LIB: ObjLib cleanup done.
WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0
[root@esxi:~]
[root@esxi:~] df
Filesystem Bytes Used Available Use% Mounted on
VMFS-5 12348030976 931135488 11416895488 8% /vmfs/volumes/DatastoreDefvmfs5
vfat 261853184 169873408 91979776 65% /vmfs/volumes/1e7934e3-47d70b38-1615-5dbf5e04c594
vfat 261853184 8192 261844992 0% /vmfs/volumes/f3716ce3-2e47c11d-b1ff-40e92ad34166
vfat 299712512 211386368 88326144 71% /vmfs/volumes/56a610da-cc6be0e4-7bfa-101f744c0550
[root@esxi:~] df -h
Filesystem Size Used Available Use% Mounted on
VMFS-5 11.5G 888.0M 10.6G 8% /vmfs/volumes/DatastoreDefvmfs5
vfat 249.7M 162.0M 87.7M 65% /vmfs/volumes/1e7934e3-47d70b38-1615-5dbf5e04c594
vfat 249.7M 8.0K 249.7M 0% /vmfs/volumes/f3716ce3-2e47c11d-b1ff-40e92ad34166
vfat 285.8M 201.6M 84.2M 71% /vmfs/volumes/56a610da-cc6be0e4-7bfa-101f744c0550
[root@esxi:~] fdisk -h
***
*** The fdisk command is deprecated: fdisk does not handle GPT partitions. Please use partedUtil
***
/usr/lib/vmware/misc/bin/fdisk: invalid option -- 'h'
BusyBox v1.20.2 (2014-08-27 12:48:18 PDT) multi-call binary.
Usage: fdisk [-ul] [-C CYLINDERS] [-H HEADS] [-S SECTORS] [-b SSZ] DISK
Change partition table
-u Start and End are in sectors (instead of cylinders)
-l Show partition table for each DISK, then exit
-b 2048 (for certain MO disks) use 2048-byte sectors
-C CYLINDERS Set number of cylinders/heads/sectors
-H HEADS
-S SECTORS
[root@esxi:~] fdisk -l /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0
***
*** The fdisk command is deprecated: fdisk does not handle GPT partitions. Please use partedUtil
***
Found valid GPT with protective MBR; using GPT
Disk /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0: 31266816 sectors, 29.8M
Logical sector size: 512
Disk identifier (GUID): 29d21951-dae2-476f-8c15-b6e2891fd70c
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 31266782
Number Start (sector) End (sector) Size Code Name
1 64 8191 8128 0700
5 8224 520191 499K 0700
6 520224 1032191 499K 0700
7 1032224 1257471 219K 0700
8 1257504 1843199 571K 0700
9 1843200 7086079 5120K 0700
10 7086080 31264767 23.0M 0700
[root@esxi:~]
Using username "root".
Using keyboard-interactive authentication.
Password:
The time and date of this login have been sent to the system logs.
VMware offers supported, powerful system administration tools. Please
see www.vmware.com/go/sysadmintools for details.
The ESXi Shell can be disabled by an administrative user. See the
vSphere Security documentation for more information.
[root@esxi:~] esxcli storage core device list
mpx.vmhba32:C0:T0:L0
Display Name: Local USB Direct-Access (mpx.vmhba32:C0:T0:L0)
Has Settable Display Name: false
Size: 15267
Device Type: Direct-Access
Multipath Plugin: NMP
Devfs Path: /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0
Vendor: SanDisk
Model: Cruzer Fit
Revision: 1.27
SCSI Level: 2
Is Pseudo: false
Status: on
Is RDM Capable: false
Is Local: true
Is Removable: true
Is SSD: false
Is VVOL PE: false
Is Offline: false
Is Perennially Reserved: false
Queue Full Sample Size: 0
Queue Full Threshold: 0
Thin Provisioning Status: unknown
Attached Filters:
VAAI Status: unsupported
Other UIDs: vml.0000000000766d68626133323a303a30
Is Shared Clusterwide: false
Is Local SAS Device: false
Is SAS: false
Is USB: true
Is Boot USB Device: true
Is Boot Device: true
Device Max Queue Depth: 1
No of outstanding IOs with competing worlds: 32
Drive Type: unknown
RAID Level: unknown
Number of Physical Drives: unknown
Protection Enabled: false
PI Activated: false
PI Type: 0
PI Protection Mask: NO PROTECTION
Supported Guard Types: NO GUARD SUPPORT
DIX Enabled: false
DIX Guard Type: NO GUARD SUPPORT
Emulated DIX/DIF Enabled: false
[root@esxi:~] partedUtil getptbl "/vmfs/devices/disks/mpx.vmhba32:C0:T0:L0"
gpt
1946 255 63 31266816
1 64 8191 C12A7328F81F11D2BA4B00A0C93EC93B systemPartition 128
5 8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
6 520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
7 1032224 1257471 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0
8 1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
9 1843200 7086079 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0
[root@esxi:~] partedUtil setptbl "/vmfs/devices/disks/mpx.vmhba32:C0:T0:L0" gpt "1 64 8191 C12A7328F81F11D2BA4B00A0C93EC93B 128" "
5 8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 0" "6 520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 0" "7 1032224 1257471 9D27538
040AD11DBBF97000C2911D1B8 0" "8 1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 0" "9 1843200 7086079 9D27538040AD11DBBF97000C291
1D1B8 0" "10 7086080 31264767 AA31E02A400F11DB9590000C2911D1B8 0"
gpt
0 0 0 0
1 64 8191 C12A7328F81F11D2BA4B00A0C93EC93B 128
5 8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 0
6 520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 0
7 1032224 1257471 9D27538040AD11DBBF97000C2911D1B8 0
8 1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 0
9 1843200 7086079 9D27538040AD11DBBF97000C2911D1B8 0
10 7086080 31264767 AA31E02A400F11DB9590000C2911D1B8 0
[root@esxi:~] partedUtil getptbl "/vmfs/devices/disks/mpx.vmhba32:C0:T0:L0"
gpt
1946 255 63 31266816
1 64 8191 C12A7328F81F11D2BA4B00A0C93EC93B systemPartition 128
5 8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
6 520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
7 1032224 1257471 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0
8 1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
9 1843200 7086079 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0
10 7086080 31264767 AA31E02A400F11DB9590000C2911D1B8 vmfs 0
[root@esxi:~] vmkfstools -C vmfs5 -b 4m -S Datastore4m
Invalid destination specification:
vmkfstools: Argument missing
[root@esxi:~] vmkfstools -C vmfs5 -b 4m -S Datastore4m /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0:10
create fs deviceName:'/vmfs/devices/disks/mpx.vmhba32:C0:T0:L0:10', fsShortName:'vmfs5', fsName:'Datastore4m'
deviceFullPath:/dev/disks/mpx.vmhba32:C0:T0:L0:10 deviceFile:mpx.vmhba32:C0:T0:L0:10
Invalid fileBlockSize 4194304. VMFS 5 doesn't support file blocks greater than 1MB
Usage: vmkfstools -C [vmfs5|vfat] /vmfs/devices/disks/vml... or,
vmkfstools -C [vmfs5|vfat] /vmfs/devices/disks/naa... or,
vmkfstools -C [vmfs5|vfat] /vmfs/devices/disks/mpx.vmhbaA:T:L:P
Error: Invalid argument
[root@esxi:~] ls -l /vmfs/volumes/
total 768
drwxr-xr-x 1 root root 8 Jan 1 1970 1e7934e3-47d70b38-1615-5dbf5e04c594
drwxr-xr-x 1 root root 8 Jan 1 1970 56a610da-cc6be0e4-7bfa-101f744c0550
drwxr-xr-x 1 root root 8 Jan 1 1970 f3716ce3-2e47c11d-b1ff-40e92ad34166
[root@esxi:~] df
Filesystem Bytes Used Available Use% Mounted on
vfat 261853184 169873408 91979776 65% /vmfs/volumes/1e7934e3-47d70b38-1615-5dbf5e04c594
vfat 261853184 8192 261844992 0% /vmfs/volumes/f3716ce3-2e47c11d-b1ff-40e92ad34166
vfat 299712512 211386368 88326144 71% /vmfs/volumes/56a610da-cc6be0e4-7bfa-101f744c0550
[root@esxi:~] vmkfstools -Ph -v10 /vmfs/volumes/1e7934e3-47d70b38-1615-5dbf5e04c594
Could not retrieve max file size: Inappropriate ioctl for device
vfat-0.04 file system spanning 1 partitions.
File system label (if any):
Mode: private
Capacity 249.7 MB, 87.7 MB available, file block size 4 KB, max supported file size 0 bytes
UUID: 1e7934e3-47d70b38-1615-5dbf5e04c594
Logical device: mpx.vmhba32:C0:T0:L0:5
Partitions spanned (on "disks"):
mpx.vmhba32:C0:T0:L0:5
Is Native Snapshot Capable: NO
OBJLIB-LIB: ObjLib cleanup done.
WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0
[root@esxi:~] vmkfstools -Ph -v10 /vmfs/volumes/56a610da-cc6be0e4-7bfa-101f744c0550
Could not retrieve max file size: Inappropriate ioctl for device
vfat-0.04 file system spanning 1 partitions.
File system label (if any):
Mode: private
Capacity 285.8 MB, 84.2 MB available, file block size 8 KB, max supported file size 0 bytes
UUID: 56a610da-cc6be0e4-7bfa-101f744c0550
Logical device: mpx.vmhba32:C0:T0:L0:8
Partitions spanned (on "disks"):
mpx.vmhba32:C0:T0:L0:8
Is Native Snapshot Capable: NO
OBJLIB-LIB: ObjLib cleanup done.
WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0
[root@esxi:~] vmkfstools -Ph -v10 /vmfs/volumes/f3716ce3-2e47c11d-b1ff-40e92ad34166
Could not retrieve max file size: Inappropriate ioctl for device
vfat-0.04 file system spanning 1 partitions.
File system label (if any):
Mode: private
Capacity 249.7 MB, 249.7 MB available, file block size 4 KB, max supported file size 0 bytes
UUID: f3716ce3-2e47c11d-b1ff-40e92ad34166
Logical device: mpx.vmhba32:C0:T0:L0:6
Partitions spanned (on "disks"):
mpx.vmhba32:C0:T0:L0:6
Is Native Snapshot Capable: NO
OBJLIB-LIB: ObjLib cleanup done.
WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0
[root@esxi:~] esxcfg-scsidevs -m
[root@esxi:~] vmkfstools -C vmfs3 -b 4m -S Datastore4m /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0:10
create fs deviceName:'/vmfs/devices/disks/mpx.vmhba32:C0:T0:L0:10', fsShortName:'vmfs3', fsName:'Datastore4m'
Creation of VMFS-3 is not supported.
Usage: vmkfstools -C [vmfs5|vfat] /vmfs/devices/disks/vml... or,
vmkfstools -C [vmfs5|vfat] /vmfs/devices/disks/naa... or,
vmkfstools -C [vmfs5|vfat] /vmfs/devices/disks/mpx.vmhbaA:T:L:P
Error: vmkfstools failed: vmkernel is not loaded or call not implemented.
[root@esxi:~] vmkfstools -h
No valid command specified
OPTIONS FOR FILE SYSTEMS:
vmkfstools -C --createfs [vmfs5|vfat]
-S --setfsname fsName
-Z --spanfs span-partition
-G --growfs grown-partition
deviceName
-P --queryfs -h --humanreadable
-T --upgradevmfs
vmfsPath
-y --reclaimBlocks vmfsPath [--reclaimBlocksUnit #blocks]
OPTIONS FOR VIRTUAL DISKS:
vmkfstools -c --createvirtualdisk #[bBsSkKmMgGtT]
-d --diskformat [zeroedthick
|thin
|eagerzeroedthick
]
-a --adaptertype [deprecated]
-W --objecttype [file|vsan|vvol]
--policyFile <fileName>
-w --writezeros
-j --inflatedisk
-k --eagerzero
-K --punchzero
-U --deletevirtualdisk
-E --renamevirtualdisk srcDisk
-i --clonevirtualdisk srcDisk
-d --diskformat [zeroedthick
|thin
|eagerzeroedthick
|rdm:<device>|rdmp:<device>
|2gbsparse]
-W --object [file|vsan|vvol]
--policyFile <fileName>
-N --avoidnativeclone
-X --extendvirtualdisk #[bBsSkKmMgGtT]
[-d --diskformat eagerzeroedthick]
-M --migratevirtualdisk
-r --createrdm /vmfs/devices/disks/...
-q --queryrdm
-z --createrdmpassthru /vmfs/devices/disks/...
-v --verbose #
-g --geometry
-x --fix [check|repair]
-e --chainConsistent
-Q --objecttype name/value pair
--uniqueblocks childDisk
vmfsPath
OPTIONS FOR DEVICES:
-L --lock [reserve|release|lunreset|targetreset|busreset|readkeys|readresv
] /vmfs/devices/disks/...
-B --breaklock /vmfs/devices/disks/...
vmkfstools -H --help
[root@esxi:~] vmkfstools -v -C vmfs5 -S DatastoreDefvmfs5 /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0:10
Extra arguments at the end of the command line.
OPTIONS FOR FILE SYSTEMS:
vmkfstools -C --createfs [vmfs5|vfat]
-S --setfsname fsName
-Z --spanfs span-partition
-G --growfs grown-partition
deviceName
-P --queryfs -h --humanreadable
-T --upgradevmfs
vmfsPath
-y --reclaimBlocks vmfsPath [--reclaimBlocksUnit #blocks]
OPTIONS FOR VIRTUAL DISKS:
vmkfstools -c --createvirtualdisk #[bBsSkKmMgGtT]
-d --diskformat [zeroedthick
|thin
|eagerzeroedthick
]
-a --adaptertype [deprecated]
-W --objecttype [file|vsan|vvol]
--policyFile <fileName>
-w --writezeros
-j --inflatedisk
-k --eagerzero
-K --punchzero
-U --deletevirtualdisk
-E --renamevirtualdisk srcDisk
-i --clonevirtualdisk srcDisk
-d --diskformat [zeroedthick
|thin
|eagerzeroedthick
|rdm:<device>|rdmp:<device>
|2gbsparse]
-W --object [file|vsan|vvol]
--policyFile <fileName>
-N --avoidnativeclone
-X --extendvirtualdisk #[bBsSkKmMgGtT]
[-d --diskformat eagerzeroedthick]
-M --migratevirtualdisk
-r --createrdm /vmfs/devices/disks/...
-q --queryrdm
-z --createrdmpassthru /vmfs/devices/disks/...
-v --verbose #
-g --geometry
-x --fix [check|repair]
-e --chainConsistent
-Q --objecttype name/value pair
--uniqueblocks childDisk
vmfsPath
OPTIONS FOR DEVICES:
-L --lock [reserve|release|lunreset|targetreset|busreset|readkeys|readresv
] /vmfs/devices/disks/...
-B --breaklock /vmfs/devices/disks/...
vmkfstools -H --help
[root@esxi:~] vmkfstools -C vmfs5 -S DatastoreDefvmfs5 /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0:10
create fs deviceName:'/vmfs/devices/disks/mpx.vmhba32:C0:T0:L0:10', fsShortName:'vmfs5', fsName:'DatastoreDefvmfs5'
deviceFullPath:/dev/disks/mpx.vmhba32:C0:T0:L0:10 deviceFile:mpx.vmhba32:C0:T0:L0:10
ATS on device /dev/disks/mpx.vmhba32:C0:T0:L0:10: not supported
.
Checking if remote hosts are using this device as a valid file system. This may take a few seconds...
Creating vmfs5 file system on "mpx.vmhba32:C0:T0:L0:10" with blockSize 1048576 and volume label "DatastoreDefvmfs5".
Successfully created new volume: 56a64f12-82285a62-4f3f-101f744c0550
[root@esxi:~] vmkfstools -V
[root@esxi:~] ls -la /vmfs/volumes/
total 1796
drwxr-xr-x 1 root root 512 Jan 25 16:39 .
drwxr-xr-x 1 root root 512 Jan 25 15:07 ..
drwxr-xr-x 1 root root 8 Jan 1 1970 1e7934e3-47d70b38-1615-5dbf5e04c594
drwxr-xr-x 1 root root 8 Jan 1 1970 56a610da-cc6be0e4-7bfa-101f744c0550
drwxr-xr-t 1 root root 1260 Jan 25 16:36 56a64f12-82285a62-4f3f-101f744c0550
lrwxr-xr-x 1 root root 35 Jan 25 16:39 DatastoreDefvmfs5 -> 56a64f12-82285a62-4f3f-101f744c0550
drwxr-xr-x 1 root root 8 Jan 1 1970 f3716ce3-2e47c11d-b1ff-40e92ad34166
[root@esxi:~] vmkfstools -Ph -v10 /vmfs/volumes/56a64f12-82285a62-4f3f-101f744c0550
VMFS-5.61 file system spanning 1 partitions.
File system label (if any): DatastoreDefvmfs5
Mode: public
Capacity 11.5 GB, 10.6 GB available, file block size 1 MB, max supported file size 62.9 TB
Volume Creation Time: Mon Jan 25 16:36:34 2016
Files (max/free): 87052/87044
Ptr Blocks (max/free): 64512/64496
Sub Blocks (max/free): 32000/32000
Secondary Ptr Blocks (max/free): 256/256
File Blocks (overcommit/used/overcommit %): 0/888/0
Ptr Blocks (overcommit/used/overcommit %): 0/16/0
Sub Blocks (overcommit/used/overcommit %): 0/0/0
Volume Metadata size: 715481088
UUID: 56a64f12-82285a62-4f3f-101f744c0550
Logical device: 56a64f0b-cd78de55-808f-101f744c0550
Partitions spanned (on "lvm"):
mpx.vmhba32:C0:T0:L0:10
Is Native Snapshot Capable: YES
OBJLIB-LIB: ObjLib cleanup done.
WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0
[root@esxi:~]
[root@esxi:~] df
Filesystem Bytes Used Available Use% Mounted on
VMFS-5 12348030976 931135488 11416895488 8% /vmfs/volumes/DatastoreDefvmfs5
vfat 261853184 169873408 91979776 65% /vmfs/volumes/1e7934e3-47d70b38-1615-5dbf5e04c594
vfat 261853184 8192 261844992 0% /vmfs/volumes/f3716ce3-2e47c11d-b1ff-40e92ad34166
vfat 299712512 211386368 88326144 71% /vmfs/volumes/56a610da-cc6be0e4-7bfa-101f744c0550
[root@esxi:~] df -h
Filesystem Size Used Available Use% Mounted on
VMFS-5 11.5G 888.0M 10.6G 8% /vmfs/volumes/DatastoreDefvmfs5
vfat 249.7M 162.0M 87.7M 65% /vmfs/volumes/1e7934e3-47d70b38-1615-5dbf5e04c594
vfat 249.7M 8.0K 249.7M 0% /vmfs/volumes/f3716ce3-2e47c11d-b1ff-40e92ad34166
vfat 285.8M 201.6M 84.2M 71% /vmfs/volumes/56a610da-cc6be0e4-7bfa-101f744c0550
[root@esxi:~] fdisk -h
***
*** The fdisk command is deprecated: fdisk does not handle GPT partitions. Please use partedUtil
***
/usr/lib/vmware/misc/bin/fdisk: invalid option -- 'h'
BusyBox v1.20.2 (2014-08-27 12:48:18 PDT) multi-call binary.
Usage: fdisk [-ul] [-C CYLINDERS] [-H HEADS] [-S SECTORS] [-b SSZ] DISK
Change partition table
-u Start and End are in sectors (instead of cylinders)
-l Show partition table for each DISK, then exit
-b 2048 (for certain MO disks) use 2048-byte sectors
-C CYLINDERS Set number of cylinders/heads/sectors
-H HEADS
-S SECTORS
[root@esxi:~] fdisk -l /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0
***
*** The fdisk command is deprecated: fdisk does not handle GPT partitions. Please use partedUtil
***
Found valid GPT with protective MBR; using GPT
Disk /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0: 31266816 sectors, 29.8M
Logical sector size: 512
Disk identifier (GUID): 29d21951-dae2-476f-8c15-b6e2891fd70c
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 31266782
Number Start (sector) End (sector) Size Code Name
1 64 8191 8128 0700
5 8224 520191 499K 0700
6 520224 1032191 499K 0700
7 1032224 1257471 219K 0700
8 1257504 1843199 571K 0700
9 1843200 7086079 5120K 0700
10 7086080 31264767 23.0M 0700
[root@esxi:~]
======
SO:
TARGET UNREACHABLE :( :)
====
refs:
=======
Partition Alignment and block size VMware 5
October 26, 2013
http://blog.jgriffiths.org/?p=592
Using vmkfstools
https://pubs.vmware.com/vsphere-50/index.jsp#com.vmware.vsphere.storage.doc_50/GUID-A5D85C33-A510-4A3E-8FC7-93E6BA0A048F.html?resultof=%2522%2576%256d%256b%2566%2573%2574%256f%256f%256c%2573%2522%2520%2522%2576%256d%256b%2566%2573%2574%256f%256f%256c%2522%2520http://blog.jgriffiths.org/?p=592
Block size limitations of a VMFS datastore (1003565)
Managing the Virtual Machine File System with vmkfstools
https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vcli.examples.doc_50%2Fcli_manage_files.5.3.htmlUsing vmkfstools
=======
Reformatting the local VMFS partition's block size in ESX 4.x (post-installation)(1013210)
Frequently Asked Questions on VMware vSphere 5.x for VMFS-5 (2003813)
Performing a rescan of the storage on an ESX/ESXi host (1003988)
to search for new VMFS datastores, run this command:
vmkfstools -V
Note: This command does not generate any output.
If a new datastore has been detected, it is mounted in /vmfs/volumes/ using its friendly name (if it has one) or its UUID.
[root@esxi:~] power
ВідповістиВидалитиpowerOffVms poweroff
[root@esxi:~] poweroff -h
poweroff: invalid option -- 'h'
BusyBox v1.20.2 (2014-08-27 12:48:18 PDT) multi-call binary.
Usage: poweroff [-d DELAY] [-n] [-f]
Halt and shut off power
-d SEC Delay interval
-n Do not sync
-f Force (don't go through init)
[root@esxi:~] poweroff -d 5
[root@esxi:~]