Re: corrupt lead, bad key order & no csum found for inode & csum failed ino & input/output error

2015-12-27 Thread Hugo Mills
On Sun, Dec 27, 2015 at 08:03:16PM -0500, james harvey wrote: > Have gotten about 300 (mostly duplicate) BTRFS errors in the last > hours. No signs of disk problem. Non-SSD SATA. Was able to dd the > drive into an image file on another drive without errors. Smartctl > reports no issues. It is

corrupt lead, bad key order & no csum found for inode & csum failed ino & input/output error

2015-12-27 Thread james harvey
Have gotten about 300 (mostly duplicate) BTRFS errors in the last hours. No signs of disk problem. Non-SSD SATA. Was able to dd the drive into an image file on another drive without errors. Smartctl reports no issues. It is a single disk though. Been running btrfs fine since 7/9/15, installin