Ok, I'll check it out.
I think I'v tracked down all the files with bad "atime" and cleared
all the BTRFS errors by cp -r , deleting the originals and moving the
copies in .
thanks a bunch .
Charles Wright
On Tue, Sep 24, 2019 at 12:08 AM Chris Murphy <li...@colorremedies.com> wrote:
>
> On Mon, Sep 23, 2019 at 6:35 PM Charles Wright
> <charles.v.wri...@gmail.com> wrote:
> >
> > if I boot the 5.0.0-30 kernel and enter the "dwhelper" directory and
> > do "dmesg" their is this
> >
> > [ 199.522886] ata2.00: exception Emask 0x10 SAct 0x8000 SErr 0x2d0100
> > action 0x6 frozen
> > [ 199.522891] ata2.00: irq_stat 0x08000000, interface fatal error
> > [ 199.522893] ata2: SError: { UnrecovData PHYRdyChg CommWake 10B8B BadCRC }
> > [ 199.522897] ata2.00: failed command: READ FPDMA QUEUED
> > [ 199.522902] ata2.00: cmd 60/08:78:a8:57:f3/00:00:12:00:00/40 tag 15
> > ncq dma 4096 in
> > res 50/00:08:a8:57:f3/00:00:12:00:00/40 Emask
> > 0x10 (ATA bus error)
> > [ 199.522904] ata2.00: status: { DRDY }
> > [ 199.522908] ata2: hard resetting link
> > [ 199.837384] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
> > [ 199.840579] ata2.00: configured for UDMA/133
> > [ 199.840771] ata2: EH complete
>
> This is a hardware problem. I suggest swapping out the cable between
> the drive and controller.
>
> "interface fatal error"
> "BadCRC"
>
> >
> > but all works as in I can access the files as normal
>
> It's not normal to having the ATA link hard reset due to CRC errors.
> That blows away the entire command queue on SATA drives. There's
> nothing any file system can do about this.
>
>
>
> --
> Chris Murphy
