Created attachment 850193 [details] dmesg log Description of problem: kernel-3.12.7-300.fc20.x86_64 breaks ext4 on bcache device WARNING: CPU: 3 PID: 2245 at fs/inode.c:281 drop_nlink+0x3e/0x50() Version-Release number of selected component (if applicable): kernel-3.12.7-300.fc20.x86_64 How reproducible: always Steps to Reproduce: update to new kernel reboot use computer for a while Actual results: kernel oops, system instability (broken desktop...) Expected results: stable system Additional info: see dmesg.log
Not sure if this one should go to block or fs, but we'll start with the obvious for now.
You mention 3.12.7 specifically here. If you boot into 3.12.6 or older do you still have these issues? There were a number of changes in 3.12.7 to ext4, but nothing to bcache that I can see.
I don't have this issue in 3.12.6. Note: I can boot on 3.12.6 with fs error and use my system. When I run fsck.ext4 I got a lot of different (metadata) corruptions. Still running fsck.ext4, I'm in "Clone multiply-claimed blocks?" phase. It tries to fix files, which has been modified during 3.12.7 run. (Desktop configuration files, Firefox cache...). This operation is very slow and seems to be CPU-bound, filling separate bug.
I forgot to mention I also use LVM thin provisioning. My setup is: SSD/LUKS/LVM thinp/bcache caching device HDD/LUKS/bcache backing device bcache/ext4
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug has been in a needinfo state for several weeks and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 20, please feel free to reopen the bug and provide the additional information requested.