Block Devices vs Character Devices in Linux

In Linux, hardware components are exposed to user space as special files located inside the /dev directory. This article provides a clear comparison between the two primary categories of device nodes: block devices and character devices. You will learn how each type handles data transmission, how the kernel buffers and accesses them, common real-world examples of both, and how to identify them using standard Linux commands.

The Role of the /dev Directory

Linux follows the Unix philosophy that "everything is a file." To allow programs to communicate with physical hardware or virtual resources, the kernel exposes these components as special files called device nodes or device files inside the /dev directory.

Instead of containing readable text or binary application data, a device file acts as an interface or endpoint to a device driver within the Linux kernel. Device files are categorized mainly into character devices and block devices based on how the operating system handles data transfers to and from them.

What Is a Character Device?

A character device (often called a "char device") communicates by sending or receiving data sequentially as a stream of individual bytes or characters.

Key attributes of character devices include:

• Sequential Access: Data must be read or written in a continuous stream. You generally cannot seek back and forth to arbitrary positions within the data stream.
• Unbuffered Transfer: Data moves directly between the user space application and the driver without going through the kernel's file system page cache.
• Real-time Handling: Because bytes are processed as they arrive, this model is ideal for interactive devices and streaming hardware.

Common Examples of Character Devices

• /dev/tty and /dev/pts/*: Standard terminals and pseudo-terminals.
• /dev/null, /dev/zero: Virtual devices that discard output or produce null bytes.
• /dev/random, /dev/urandom: Kernel entropy and random number generators.
• Sound cards, serial ports, and human interface devices like mice and keyboards.

What Is a Block Device?

A block device transfers data in fixed-size chunks known as blocks (typically 512 bytes to 4096 bytes).

Key attributes of block devices include:

• Random Access: The operating system can read or write data to any specific block address on the device at any time, allowing for seeking and non-sequential access.
• Kernel Buffering: Block devices rely heavily on the kernel's buffer cache. When an application writes data, the kernel stores it in RAM and flushes it to the physical medium asynchronously, optimizing performance.
• Filesystem Hosting: Because block devices allow random access and structured addressing, they are the only device types that can host mountable filesystems.

Common Examples of Block Devices

• /dev/sda, /dev/sdb: SATA or SCSI hard drives and SSDs.
• /dev/nvme0n1: NVMe solid-state storage.
• /dev/sda1: Specific disk partitions.
• /dev/loop0: Loopback devices used to mount disk image files as filesystems.

Key Differences at a Glance

How to Identify Device Types in Linux

You can check whether a device is a block or character device using the ls -l command on any file in /dev. Look at the very first character of the file permissions string:

• c indicates a character device.
• b indicates a block device.

Example: Inspecting a Character Device

$ ls -l /dev/null
crw-rw-rw- 1 root root 1, 3 Oct 24 10:00 /dev/null

The leading c signifies that /dev/null is a character device. The numbers 1, 3 are the major and minor numbers used by the kernel to identify the corresponding driver.

Example: Inspecting a Block Device

$ ls -l /dev/sda
brw-rw---- 1 root disk 8, 0 Oct 24 10:00 /dev/sda

The leading b indicates that /dev/sda is a block device, managed by the storage driver identified by major number 8.