Dear developers,
I've been using f2fs for my root fs since the 4.9 kernel. The partition is encrypted with dm-crypt (LUKS). A few weeks back, after upgrading to kernel 4.14.2, I began to experience corruption of many files, revealed by boot-time fsck. Most of the corrupted files were temporary, but not all. I never got to successfully restore them, since fsck.f2fs attempts to restore files to /.lost_found (instead of lost+found, as it'd normally be expected), and the folder did not exist in my system. After isolating the problem to the kernel version, and after it affected some important system files, I simply reverted to 4.13.9 and stood by it for a while. Two days ago I wanted to give it another try. Even though nothing from the changelogs seemed to give me hope, I upgraded from 4.13.9 to 4.14.7 and rebooted. And rebooted again. No apparent issue, at that moment. But then, after a few hours of work, my applications started to malfunction. First qemu/libvirt (not sure which); I restarted my VM but it crashed again after a couple minutes. Then the music player crashed, followed by my text editor, with a delay of about 5-10 minutes in between. This is where I noticed something was seriously wrong. I attempted to close my browser (Firefox) in order to restart the computer, but it was impossible. Firefox would not close due to some missing persistent state file(s) that should be stored in $HOME/.mozilla, but was missing. I proceeded to shutdown the system nevertheless, but my DE (Cinnamon) was not accepting commands due to missing or invalid system libraries. Hard reset. On power on, fsck once again "recovered" many lost files - only it actually did not recover a thing, for I still hadn't created lost_found. After struggling for a while to get my system to a usable state, I had to reinstall 1146 packages from the package manager. It seems I'm alright by now. I'm sure this is a kernel issue. Could be device mapper, I suppose, but... I use encryption, in the same fashion, on two other volumes formatted with ext4. I also have ext2 and ntfs filesystems without encryption. My hardware is alright. The problem is gone by downgrading to kernel 4.13.x. For these reasons I'm quite sure this is an f2fs issue. Let me know if I can provide something more useful to help in sorting this out. Regards Marc ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Linux-f2fs-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
