Hello, here is the fifth iteration of my patches to improve filesystem freezing. No serious changes since last time. Mostly I rebased patches and merged this series with series moving file_update_tim
Looking at a desktop system, I think it is very typical that there are open-unlinked files present, so I don't know if this is really an acceptable solution. It isn't clear from your comments whether
Unlinked-but-open files are the reason that XFS dirties the log after the freeze process is complete. This ensures that if the system crashes while the filesystem is frozen then log recovery during t
The ext3/4 code has long been able to handle open-unlinked files properly after a crash (they are put into a singly-linked list from the superblock on disk that is processed after journal recovery).
Thanks for looking at this. It is currently a blanket refusal. And I agree it's problematic. There are two problems with open but unlinked files. One is that some old filesystems cannot get in a cons
Let me add my name to the chorus of "we have to handle freezing with open+unlinked, we cannot assume they don't exist." Others have pointed out that we can flag the safe filesystems. I'd even be will
It would also affect current KDE desktops as they tend to use MySQL for Akonadi & Nepomuk, plus anyone using Chromium (and presumably Chrome): samuel@eris:/tmp$ sudo lsof | grep deleted | awk '{print