Sysadmin Linux Theory

File System Journaling

Understanding file system journaling for data protection and recovery from unexpected shutdowns and system crashes

Journaling is a file system feature that maintains a log (journal) of changes before they’re written to the main file system. It prevents data corruption during unexpected shutdowns by allowing the system to replay or rollback incomplete operations during recovery.

Key Concepts

  • Journal: Log file that records metadata changes before they occur
  • Write Barrier: Ensures journal entries are written before data
  • Recovery: Process of checking journal after unclean shutdown
  • Transaction: Group of related file system operations
  • Commit: Finalizing changes from journal to main file system

Journal Types

  • Metadata Only: Journals file system structure changes
  • Ordered: Journals metadata, orders data writes
  • Full/Data: Journals both metadata and file data

File Systems with Journaling

ext3/ext4 - Linux standard with journal support XFS - High-performance journaling file system
JFS - IBM’s journaling file system ReiserFS - Legacy journaling file system Btrfs - Modern copy-on-write file system

Practical Examples

Example 1: Check journal status (ext4) 

1
2
3

tune2fs -l /dev/sda1 | grep -i journal
Filesystem features: has_journal ext_attr resize_inode
Journal size: 128M

Shows if journaling is enabled and journal size

Example 2: Mount with journal options 

1

mount -o data=journal /dev/sda1 /mnt

Mounts with full data journaling (slowest, safest)

Example 3: Change journal mode 

1

tune2fs -o journal_data_writeback /dev/sda1

Sets writeback mode (fastest, least safe)

Example 4: View journal info with dumpe2fs 

1
2

dumpe2fs -h /dev/sda1 | grep -i journal
Journal backup: inode blocks

Displays detailed journal information

Journal Modes (ext3/ext4)

data=writeback - No data ordering guarantees data=ordered - Default, orders data before metadata data=journal - Full journaling of data and metadata

Use Cases

  • Server environments: Prevents corruption on power loss
  • Desktop systems: Faster boot after crashes
  • Database servers: Ensures transaction integrity
  • High-availability systems: Minimizes downtime
  • Storage arrays: Protects against controller failures

fsck - File system check and repair utility tune2fs - Adjust file system parameters dumpe2fs - Display file system information mount - Mount file systems with journal options blkid - Display block device attributes

Tips & Troubleshooting

  • Journal uses disk space (typically 32-128MB)
  • Full journaling impacts write performance
  • Corrupted journals may require fsck -f
  • SSD users: consider journal_async_commit option
  • Never disable journaling on production systems
  • Monitor journal size with tune2fs -l
  • Use dmesg to check for journal errors
  • Backup before changing journal modes

Performance Considerations

  • Ordered mode: Good balance of safety/speed
  • Journal mode: Safest but slowest writes
  • Writeback mode: Fastest but less crash protection
  • Journal on separate device can improve performance
  • Larger journals handle burst writes better