Current situation
I have a couple dozen or so Flatcar systems in my home lab and have spent quite a lot of time creating a drop-in system for generating the configs. Mostly are running the latest stable release, with a handful using the beta channel. All works very well in general and I'm very happy with it so big kudos to the devs.
I noticed the other day (though it's probably been happening for a while, if not forever) that if I create manual snapshots under vSphere or automatically via my backup solution that the file system is never quiesced, even though that option is selected in the options. There are no errors and everything seems to proceed correctly but the resulting snapshot has not has the f/s quiesced. Snapshots taken on Ubuntu VMs are however quiesced with a more or less identical version of open-vmtools.
Impact
I am unable to make application consistent backups. Backup software continually reports warning and failures with Flatcar systems.
Ideal future situation
The filesystem should quiesce when requested. Or, if it can't, a valid reason or error should be emitted.
Additional information
I don't know if there is a rationale that Flatcar has adopted or inherited for this behaviour. Possibly it's working exactly as intended in which case it would be useful to know the reasoning behind it and make that information more readily available.
Current situation
I have a couple dozen or so Flatcar systems in my home lab and have spent quite a lot of time creating a drop-in system for generating the configs. Mostly are running the latest stable release, with a handful using the beta channel. All works very well in general and I'm very happy with it so big kudos to the devs.
I noticed the other day (though it's probably been happening for a while, if not forever) that if I create manual snapshots under vSphere or automatically via my backup solution that the file system is never quiesced, even though that option is selected in the options. There are no errors and everything seems to proceed correctly but the resulting snapshot has not has the f/s quiesced. Snapshots taken on Ubuntu VMs are however quiesced with a more or less identical version of open-vmtools.
Impact
I am unable to make application consistent backups. Backup software continually reports warning and failures with Flatcar systems.
Ideal future situation
The filesystem should quiesce when requested. Or, if it can't, a valid reason or error should be emitted.
Additional information
I don't know if there is a rationale that Flatcar has adopted or inherited for this behaviour. Possibly it's working exactly as intended in which case it would be useful to know the reasoning behind it and make that information more readily available.