Bug 102941 - BTRFS OOPSes while deleting files with bad checksums
Summary: BTRFS OOPSes while deleting files with bad checksums
Status: NEW
Alias: None
Product: File System
Classification: Unclassified
Component: btrfs (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Josef Bacik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-15 13:24 UTC by Timothy Miller
Modified: 2016-03-20 10:02 UTC (History)
1 user (show)

See Also:
Kernel Version: 4.1.4
Tree: Mainline
Regression: No

Attachments
dmesg output (31.24 KB, application/octet-stream)
2015-08-15 13:24 UTC, Timothy Miller 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Timothy Miller 2015-08-15 13:24:00 UTC 
Created attachment 185001 [details]
dmesg output

I was constructing a 4-drive RAID1 (adding a new drive, deleting missing), and the delete missing failed because there were some files with bad checksums.  (I'm not sure that's a good reason to abort, though!)  Anyhow, I'm pretty sure I know which files had bad checksums, so I deleted them.  During that delete, BTRFS OOPSed and made the filesystem read-only.  

I think that deleting files unmatched checksums should be a valid way to recover from that condition.  If you don't need the data anymore, who cares about the checksums.

I'm attaching the complete dmesg from this situation.
Note You need to log in before you can comment on or make changes to this bug.