Protocol: SMBv[1-2] Bytes
These statistics show SMB bytes/second transferred between SMB clients and Oracle ZFS Storage Appliance. Supported SMB versions are SMB and SMB2. Bytes statistics can be broken down by: operation, client, filename, share, and project.
When to Check SMB/SMB2 Bytes
SMB bytes/sec can be used as an indication of SMB load. The best way to improve performance is to eliminate unnecessary work, which can be identified through the client and filename breakdowns, and the filename hierarchy view. Client and especially filename breakdowns can be very expensive in terms of storage and execution overhead. Therefore, it is not recommended to permanently enable these breakdowns on a busy production Oracle ZFS Storage Appliance.
SMB/SMB2 Bytes Breakdowns
Table 5-49 Breakdowns of SMB Bytes
| Breakdown | Description |
|---|---|
|
type of operation |
SMB/SMB2 operation type (read/write/getattr/setattr/lookup/...). |
|
client |
Remote hostname or IP address of the SMB client. |
|
filename |
Filename for the SMB I/O, if known, and cached by Oracle ZFS Storage Appliance. There are some circumstances where the filename is not known, such as after a cluster failover, and when clients continue to operate on SMB file handles without issuing an open request to identify the filename; in these situations the filename reported is <unknown>. |
|
share |
The share for this SMB I/O. |
|
project |
The project for this SMB I/O. |
These breakdowns can be combined to produce powerful statistics. For example, use Protocol: SMB2 bytes per second for client hostname.example.com broken down by filename to view which files a particular client is accessing.
Further Analysis
-
Protocol: SMB Operations for numerous other breakdowns on SMB operations
-
Protocol: SMBv[1-3] Average Latency for average latency per second
-
Cache: ARC Accesses to learn how well an SMB read workload is returning from cache
-
Disk: I/O Operations for the back-end disk I/O caused