Created attachment 244961 [details]
kernel log

I have a btrfs formatted nvme device which is being used for a test which does the follwing:
1. Open a file with O_DIRECT|O_SYNC flags (sparse 128MB).
2. Write and overwrite the file in a loop.
3. Induce a kernel panic and check the file for consistency after restart.

The test resulted in the file getting corrupt. Reading the file report "no csum found for inode" for almost the entire file.

It takes a few tries but the test is repeatable. has anyone seen this before? 

[ 1114.035335] BTRFS: detected SSD devices, enabling SSD mode                   
[ 1115.391082] BTRFS info (device nvme0n1): no csum found for inode 260 start 6213632
[ 1115.391088] BTRFS info (device nvme0n1): no csum found for inode 260 start 6217728
[ 1115.391091] BTRFS info (device nvme0n1): no csum found for inode 260 start 6221824
[ 1115.391093] BTRFS info (device nvme0n1): no csum found for inode 260 start 6225920
[ 1115.391095] BTRFS info (device nvme0n1): no csum found for inode 260 start 6230016
[ 1115.391098] BTRFS info (device nvme0n1): no csum found for inode 260 start 6234112
[ 1115.391100] BTRFS info (device nvme0n1): no csum found for inode 260 start 6238208
[ 1115.391102] BTRFS info (device nvme0n1): no csum found for inode 260 start 6242304
[ 1115.391118] BTRFS info (device nvme0n1): no csum found for inode 260 start 6246400
[ 1115.391120] BTRFS info (device nvme0n1): no csum found for inode 260 start 6250496
[ 1115.391122] BTRFS info (device nvme0n1): no csum found for inode 260 start 6254592
....

Distro: CentOS Linux release 7.2.1511 (Core)
Kernel: 3.10.0-327.13.1.el7.x86_64