| Summary: | fstrim on ext4 without journal | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jorge Fábregas <jorge.fabregas> |
| Component: | kernel | Assignee: | Lukáš Czerner <lczerner> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | gansalmon, itamar, jonathan, jorge.fabregas, kernel-maint, kzak, lczerner, madhu.chinakonda, marcelo.barbosa, mluscon, msnitzer, yanwang |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-01-12 15:19:07 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Jorge Fábregas
2013-09-18 15:28:07 UTC
Had some typos: fstrim -v /var/lib/libvirt/images/tempfile should be of course: fstrim -v /var/lib/libvirt/images/ I forgot to mention that all this was without using the "discard" mount option. If I use "discard" everything works as expected. As soon as I delete a file I see that the space is reclaimed in the thin pool (lvs vgthin1). In the email you've mentioned that you're using ext4 without journal. I can not see it in the steps to reproduce, does it mean that you have it defined in the /etc/mke2fs.conf, or you're using journal after all ? Please confirm. In no journal mode there is a bug which prevents fstrim to do anything after the first run. Patch has already been send upstream. -Lukas I wrote the steps on how to redproduce out of my mind (based on what I remembered). I totally forgot that for this logical volume I created it without journal...so to answer your question the steps to reproduce should include: mkfs.ext4 -O ^has_journal /dev/vgthin1/lvol2 ...instead of the plain vanilla mkfs.ext4 *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.12.6-200.fc19. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20. If you experience different issues, please open a new bug report for those. Patch accepted upstream (commit 8f9ff189205a6817aee5a1f996f876541f86e07c) and submitted for stable 3.16.y Thanks! -Lukas (In reply to Lukáš Czerner from comment #6) > Patch accepted upstream (commit 8f9ff189205a6817aee5a1f996f876541f86e07c) > and submitted for stable 3.16.y > > Thanks! > -Lukas Er... I think you mean 3.12.y? If so, it should make the next 3.12.y release, so we'll leave this in POST for right now and pick it up via that. Yeah, of course I meant 3.12.y :) Btw, it's also submitted for 3.10.y. -Lukas 3.12.7 is in updates-testing now. Thanks Josh. I did an update of my Fedora 20 system with: yum update --enablerepo=updates-testing kernel ...and installed 3.12.7. I then removed the discard option for my non-journal-EXT4 filesystem and proceeded with the fstrim tests. It works perfectly fine now. Thank you all & specially to Lukáš Czerner. |