On Fri, May 19, 2017 at 06:27:53PM -0600, Chris Murphy wrote: > On Fri, May 19, 2017 at 3:00 PM, Darrick J. Wong > <darrick.wong@xxxxxxxxxx> wrote: > > Frankly, all you have to do is tweak the grub config file writer to > > "fsfreeze -f /boot && fsfreeze -u /boot" after it writes the grub.cfg and > > before it exits. That's both grubby and grub-mkconfig. > > I am willing to bet that their assumption has been, since ancient > times, that PID 1 umounts the file system before reboot, thereby > writing log contents to the file system. And it's not just these two > programs, there's probably bunches of kernel updates that are done by > myriad scripts that likewise assume on umount happening before reboot. This is not relevant to the discussion, because sync(1) is sufficient for those updates to be accessible after reboot because the filesystem replays the log at mount time and the changes are not accessed until the filesystem is mounted. IOWs, the problem is purely a bootloader issue due to the fact it is the only software on the system that directly accesses the filesystem metadata prior to log recovery being performed at boot time. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
