https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244692
Bug ID: 244692
Summary: gjournal TRIM support
Product: Base System
Version: 12.1-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: b...@freebsd.org
Reporter: s...@spy.zp.ua
# gjournal load
# gjournal label -vh /dev/gpt/testdata /dev/gpt/testlog
# newfs -J -t -g 1M /dev/gpt/testdata.journal
# mount -o "async,atime=off" /dev/gpt/testdata.journal /mnt
# tail -n 3 /var/log/messages
Mar 9 12:22:16 ctl kernel: GEOM_JOURNAL: BIO_FLUSH not supported by
gpt/testlog.
Mar 9 12:22:16 ctl kernel: GEOM_JOURNAL: BIO_FLUSH not supported by
gpt/testdata.
Mar 9 12:25:40 ctl kernel: WARNING: /mnt: TRIM flag on fs but disk does not
confirm that it supports TRIM
# smartctl -a /dev/nvme1 | grep -i utiliz
Namespace 1 Utilization: 50,589,696 [50.5 MB]
# dd if=/dev/random of=/mnt/junk bs=1m count=30000
# smartctl -a /dev/nvme1 | grep -i utiliz
Namespace 1 Utilization: 36,860,428,288 [36.8 GB]
# rm /mnt/junk
… after a couple of time still not free …
# smartctl -a /dev/nvme1 | grep -i utiliz
Namespace 1 Utilization: 36,860,428,288 [36.8 GB]
It seems, gjournal still does not support TRIM in 2020?!.. neither for data
device nor for journal device.
And really, one more fast proof:
# trim -f /dev/gpt/testdata.journal
trim /dev/gpt/testdata.journal offset 0 length 53687090688
trim: /dev/gpt/testdata.journal: TRIM/UNMAP not supported by driver
Without gjournal trim works fine on the same device nvd1.
# gjournal stop /dev/gpt/testdata
# trim -f /dev/nvd1
trim /dev/nvd1 offset 0 length 960197124096
# smartctl -a /dev/nvme1 | grep -i utiliz
Namespace 1 Utilization: 0
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
