driveripper disk monitor agent deployed
All checks were successful
Podman DDNS Image / build-and-push-ddns (push) Successful in 1m16s
All checks were successful
Podman DDNS Image / build-and-push-ddns (push) Successful in 1m16s
This commit is contained in:
@@ -13,6 +13,7 @@
|
||||
- [Monitoring Disk Health](#monitoring-disk-health)
|
||||
- [Defragmenting and Compressing](#defragmenting-and-compressing)
|
||||
- [Converting ext4 to btrfs](#converting-ext4-to-btrfs)
|
||||
- [Error Kata](#error-kata)
|
||||
|
||||
Oracle [has decent docs here](https://docs.oracle.com/en/operating-systems/oracle-linux/8/btrfs/btrfs-ResizingaBtrfsFileSystem.html)
|
||||
|
||||
@@ -209,4 +210,27 @@ btrfs filesystem defragment -c zstd:20 /btrfs/pool0
|
||||
# Unmount and then run btrfs-convert
|
||||
umount /path/to/mount
|
||||
btrfs-convert /dev/sdX1
|
||||
```
|
||||
```
|
||||
|
||||
## Error Kata
|
||||
|
||||
After unplanned shutdowns, power loss, physically moving the server, or whenever
|
||||
you feel like it, it's generally a good idea to scrub your btrfs pools for
|
||||
errors and check your device stats.
|
||||
|
||||
```bash
|
||||
export POOL=pool1
|
||||
# Find any device stat with a number > 0
|
||||
# This means there's an error
|
||||
btrfs device stats /btrfs/${POOL} | grep -vE ' 0$'
|
||||
|
||||
# If you find an error, grab the smartctl details to check for disk error
|
||||
# Scrub the btrfs pool to check for other hidden errors
|
||||
lsblk -fs
|
||||
smartctl -a /dev/<dev>
|
||||
btrfs scrub start -Bd /btrfs/pool0
|
||||
btrfs scrub status /btrfs/${POOL}
|
||||
|
||||
# Check the filesystem status after a scrub
|
||||
btrfs filesystem show /btrfs/${POOL}
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user