Re: "decompress failed" in 1-2 files always causes kernel oops, check/scrub pass

(Conversation order changed to put program output at bottom) On Sat, May 12, 2018 at 10:09 PM, Chris Murphy wrote: > On Sat, May 12, 2018 at 6:10 PM, james harvey > wrote: >> Does this mean that although I've never had a corrupted disk bit >>

Re: "decompress failed" in 1-2 files always causes kernel oops, check/scrub pass

On Sat, May 12, 2018 at 6:10 PM, james harvey wrote: > On Sat, May 12, 2018 at 3:51 AM, Martin Steigerwald > wrote: >> Hey James. >> >> james harvey - 12.05.18, 07:08: >>> 100% reproducible, booting from disk, or even Arch installation ISO. >>>

Re: Btrfs installation advices

Thanks you two very much for your answers. So if I sum up correctly, I could: 1- use Self-Encrypting Drive (SED), since my drive is a Samsung NVMe 960 EVO, which is supposed to support SED according to http://www.samsung.com/semiconductor/minisite/ssd/support/faqs-nvmessd: "*Do Samsung NVMe

Re: "decompress failed" in 1-2 files always causes kernel oops, check/scrub pass

On Sat, May 12, 2018 at 3:51 AM, Martin Steigerwald wrote: > Hey James. > > james harvey - 12.05.18, 07:08: >> 100% reproducible, booting from disk, or even Arch installation ISO. >> Kernel 4.16.7. btrfs-progs v4.16. >> >> Reading one of two journalctl files causes a kernel

Re: replace drive with write_io_errs?

Adam Bahe wrote: Hello all, 'All' includes me as well, but keep in mind I am not a BTRFS dev. I have a drive that has been in my btrfs array for about 6 months now. It was purchased new. Its an IBM-ESXS SAS drive rebranded from an HGST HUH721010AL4200. Here is the following stats, it passed

replace drive with write_io_errs?

Hello all, I have a drive that has been in my btrfs array for about 6 months now. It was purchased new. Its an IBM-ESXS SAS drive rebranded from an HGST HUH721010AL4200. Here is the following stats, it passed a long smartctl test. But I'm not sure what to make of it. [/dev/sdi].write_io_errs

Re: "decompress failed" in 1-2 files always causes kernel oops, check/scrub pass

Hey James. james harvey - 12.05.18, 07:08: > 100% reproducible, booting from disk, or even Arch installation ISO. > Kernel 4.16.7. btrfs-progs v4.16. > > Reading one of two journalctl files causes a kernel oops. Initially > ran into it from "journalctl --list-boots", but cat'ing the file does