Bug 1253595
Summary: | lazytime mount option doesn't work on root partition | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | srakitnican <samuel.rakitnican> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 22 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, samuel.rakitnican |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-08-19 14:53:24 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: | |
Embargoed: |
Description
srakitnican
2015-08-14 08:20:18 UTC
(In reply to semiRocket from comment #0) > Description of problem: By adding lazytime mount option to fstab and > rebooting, mount command shows lazytime applied only to /home partition, not > on /. > Moreover changing mount options on mounted partitions described in > following mail using mount -o remount command does not work at all. http://article.gmane.org/gmane.comp.file-systems.ext4/48663 suggests that the remount issue is a regression in util-linux. You should probably file a separate bug against that component to get it fixed. > > http://www.spinics.net/lists/linux-fsdevel/msg86233.html > > Version-Release number of selected component (if applicable): > util-linux-2.26.2-1.fc22.x86_64 > kernel-4.1.3-201.fc22.x86_64 > > > How reproducible: Always > > > Steps to Reproduce: > 1. Add lazytime option to /etc/fstab > 2. Reboot Did you specify rootflags=lazytime on the kernel command line or did you rebuild your initramfs after updating /etc/fstab? (In reply to Josh Boyer from comment #1) > (In reply to semiRocket from comment #0) > > Description of problem: By adding lazytime mount option to fstab and > > rebooting, mount command shows lazytime applied only to /home partition, not > > on /. > > > Moreover changing mount options on mounted partitions described in > > following mail using mount -o remount command does not work at all. > > http://article.gmane.org/gmane.comp.file-systems.ext4/48663 > > suggests that the remount issue is a regression in util-linux. You should > probably file a separate bug against that component to get it fixed. Did that: https://bugzilla.redhat.com/show_bug.cgi?id=1254833 > Did you specify rootflags=lazytime on the kernel command line or did you > rebuild your initramfs after updating /etc/fstab? I did not do any of that because I thought that will work as is. With rootflags=lazytime at boot time works, did not try to rebuild initramfs. (In reply to semiRocket from comment #2) > (In reply to Josh Boyer from comment #1) > > (In reply to semiRocket from comment #0) > > > Description of problem: By adding lazytime mount option to fstab and > > > rebooting, mount command shows lazytime applied only to /home partition, not > > > on /. > > > > > Moreover changing mount options on mounted partitions described in > > > following mail using mount -o remount command does not work at all. > > > > http://article.gmane.org/gmane.comp.file-systems.ext4/48663 > > > > suggests that the remount issue is a regression in util-linux. You should > > probably file a separate bug against that component to get it fixed. > > Did that: https://bugzilla.redhat.com/show_bug.cgi?id=1254833 > > > Did you specify rootflags=lazytime on the kernel command line or did you > > rebuild your initramfs after updating /etc/fstab? > > I did not do any of that because I thought that will work as is. With > rootflags=lazytime at boot time works, did not try to rebuild initramfs. The initramfs mounts the root filesystem, so if the fstab containted within does not have the flag set it will not mount the rootfs with it unless rootflags= is specified. I believe on future kernel updates, dracut will read /etc/fstab and pick up the options for the corresponding initramfs. |