# Linux Disk Space and Logs for Makers

Learn how bytes, inodes, logs, and deleted-open files can each make a project machine look full.

## Outcome
Identify whether a disk-full problem is bytes, inodes, journal logs, Docker, or deleted-open files.

## Safe first step
df -h and df -i separate byte pressure from inode pressure.

## Ladder steps
### 1. Check bytes
Byte pressure means the filesystem has little storage space left.

Check: df -h shows Use% and available space.

### 2. Check inodes
Inode pressure means too many files exist even if bytes look available.

Check: df -i shows IUse%.

### 3. Check logs and journals
Logs can grow until they dominate a filesystem.

Check: journalctl --disk-usage gives the journal size.

### 4. Check deleted-open files
A deleted file can still consume space until the process closes it.

Check: lsof +L1 lists open deleted files.

## Examples
### Check filesystem byte usage
```sh
df -h
```
Expected signal: Use% and Available columns

### Check inode usage
```sh
df -i
```
Expected signal: IUse% column

### Find deleted-open files
```sh
sudo lsof +L1
```
Expected signal: Open files with link count below one

Caution: May expose process paths; inspect before sharing output.

## Common traps
- Deleting random files before proving the owner.
- Ignoring inode pressure.
- Deleting journal directories manually.

## Practice task
Write a five-command disk-full triage checklist and explain what each command proves.

## Next steps
- Use the LinuxOneLiners disk-full hub.
- Learn log search.
- Learn Docker disk usage.

## Related
- [Linux disk full repair path](https://linuxoneliners.com/problems/linux-disk-full/)