Re: What are the typical usecase of "btrfs check --init-extent-tree"?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jul 27, 2017 at 9:33 AM, Ivan Sizov <sivan606@xxxxxxxxx> wrote:
> I've just noticed a huge number of errors on one of the RAID's disks.
> "btrfs dev stats" gives:
>
> [/dev/sdc1].write_io_errs    0
> [/dev/sdc1].read_io_errs     305
> [/dev/sdc1].flush_io_errs    0
> [/dev/sdc1].corruption_errs  429
> [/dev/sdc1].generation_errs  0
>
> [/dev/sda1].write_io_errs    58331
> [/dev/sda1].read_io_errs     57438
> [/dev/sda1].flush_io_errs    37
> [/dev/sda1].corruption_errs  10110
> [/dev/sda1].generation_errs  0


You'll need to translate the sda device to ata device, and then do a
search for kernel messages. I suspect persistent bad sector on this
drive, and write failures are always disqualifying but Btrfs won't
eject this device.

Read errors are not a big problem. Read errors along with corruptions
aren't necessarily a big problem. Write errors are a big problem.



-- 
Chris Murphy
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux