Date: Mon, 09 Mar 2020 10:47:33 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 244692] gjournal TRIM support Message-ID: <bug-244692-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D244692 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: bugs@FreeBSD.org Reporter: spy@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=3Doff" /dev/gpt/testdata.journal /mnt=20 # 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=3D/dev/random of=3D/mnt/junk bs=3D1m count=3D30000 # smartctl -a /dev/nvme1 | grep -i utiliz Namespace 1 Utilization: 36,860,428,288 [36.8 GB] # rm /mnt/junk =E2=80=A6 after a couple of time still not free =E2=80=A6 # 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 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-244692-227>