为何ZFS、smartctl与iostat对同一设备命名不一致？

Great question—this boils down to how OmniOS (a Solaris-based distribution) structures its device naming hierarchy, plus the specific purpose each tool serves. Let’s break this down one by one:

zdb: /dev/dsk/c1t0d0s0 #

• /dev/dsk refers to block devices—buffered, block-oriented devices built for file systems and volume managers like ZFS.
• The s0 suffix represents the "whole-disk slice." In OmniOS/Solaris, disks are split into slices (similar to partitions), and s0 is usually configured to cover the entire disk when used with ZFS. zdb reports the exact block device slice that ZFS uses for your pool, hence the full path including s0.

smartctl: /dev/rdsk/c1t0d0s0 #

• /dev/rdsk stands for raw character devices—unbuffered, direct-access devices that bypass the OS’s block cache.
• SMART tools like smartctl need unfiltered, direct access to disk hardware to read diagnostic data. Using the raw device (rdsk) ensures no OS-level buffering interferes with this process. The s0 suffix here targets the entire disk’s raw slice, since smartctl needs to query the full disk hardware.

iostat: c1t0d0 #

• iostat focuses on overall disk performance monitoring, not specific device nodes or slices.
• By default, it aggregates metrics at the physical disk level, so it omits the dsk/rdsk prefixes and s0 slice suffix. c1t0d0 refers to the underlying physical disk’s core identifier: controller (c1), target (t0), and disk (d0)—the hardware’s base name, regardless of how it’s sliced or accessed via block/raw devices.

Quick Recap #

All three names point to the same physical disk—they just represent different ways of interacting with it:

• Block device (dsk/s0) for ZFS storage operations
• Raw device (rdsk/s0) for hardware diagnostic queries
• Base disk identifier for system-wide performance tracking

内容的提问来源于stack exchange，提问作者Bino Oetomo