Re: Bad hard drive - checksum verify failure forces readonly mount

Bug reported https://bugzilla.kernel.org/show_bug.cgi?id=121491 Thank you for helping. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Bad hard drive - checksum verify failure forces readonly mount

On Mon, Jun 27, 2016 at 12:30 AM, Vasco Almeida wrote: > File system image available at (choose one link) > https://mega.nz/#!AkAEgKyB!RUa7G5xHIygWm0ALx5ZxQjjXNdFYa7lDRHJ_sW0bWLs > https://www.sendspace.com/file/i70cft > Should I file a bug report with that image dump

Re: Bad hard drive - checksum verify failure forces readonly mount

A Dom, 26-06-2016 às 13:54 -0600, Chris Murphy escreveu: > On Sun, Jun 26, 2016 at 7:05 AM, Vasco Almeida > wrote: > > I have tried "btrfs check --repair /device" but that seems do not > > do > > any good. > > http://paste.fedoraproject.org/384960/66945936/ > > It did fix

Re: Bad hard drive - checksum verify failure forces readonly mount

On Sun, Jun 26, 2016 at 7:05 AM, Vasco Almeida wrote: > A Sáb, 25-06-2016 às 14:54 -0600, Chris Murphy escreveu: >> On Sat, Jun 25, 2016 at 2:10 PM, Vasco Almeida > > wrote: >> > Citando Chris Murphy : >> > > 3. btrfs-image

Re: Bad hard drive - checksum verify failure forces readonly mount

A Sáb, 25-06-2016 às 14:54 -0600, Chris Murphy escreveu: > On Sat, Jun 25, 2016 at 2:10 PM, Vasco Almeida > wrote: > > Citando Chris Murphy : > > > 3. btrfs-image so that devs can see what's causing the problem > > > that > > > the current code

Re: Bad hard drive - checksum verify failure forces readonly mount

On Sat, Jun 25, 2016 at 2:10 PM, Vasco Almeida wrote: > Citando Chris Murphy : >> >> I would do a couple things in order: >> 1. Mount ro and copy off what you want in case the whole thing gets >> worse and can't ever be mounted again. >> 2. Mount

Re: Bad hard drive - checksum verify failure forces readonly mount

Citando Chris Murphy : On Fri, Jun 24, 2016 at 6:06 PM, Vasco Almeida wrote: Citando Chris Murphy : dmesg http://paste.fedoraproject.org/384352/80842814/ [ 1837.386732] BTRFS info (device dm-9): continuing balance [

Re: Bad hard drive - checksum verify failure forces readonly mount

On Fri, Jun 24, 2016 at 6:06 PM, Vasco Almeida wrote: > Citando Chris Murphy : >> A lot of changes have happened since 4.1.2 I would still use something >> newer and try to repair it. > > > By repair do you mean issue "btrfs check --repair /device"

Re: Bad hard drive - checksum verify failure forces readonly mount

Citando Chris Murphy : On Fri, Jun 24, 2016 at 9:52 AM, Vasco Almeida wrote: From the pasted kernel messages: > Linux version 3.18.34-std473-amd64 (root@rl-sysrcd-p11) (gcc version 4.8.5 > (Gentoo 4.8.5 p1.3, pie-0.6.2) ) #2 SMP Tue May 24

Re: Bad hard drive - checksum verify failure forces readonly mount

On Fri, Jun 24, 2016 at 9:52 AM, Vasco Almeida wrote: >> >> From the pasted kernel messages: >> > Linux version 3.18.34-std473-amd64 (root@rl-sysrcd-p11) (gcc version 4.8.5 >> > (Gentoo 4.8.5 p1.3, pie-0.6.2) ) #2 SMP Tue May 24 20:34:19 UTC 2016 >> 3.18.34 is ancient.

Re: Bad hard drive - checksum verify failure forces readonly mount

On Thu, Jun 23, 2016 at 10:56 PM, Duncan <1i5t5.dun...@cox.net> wrote: > Chris Murphy posted on Thu, 23 Jun 2016 18:54:28 -0600 as excerpted: > >> From the pasted kernel messages: >> >>> Linux version 3.18.34-std473-amd64 (root@rl-sysrcd-p11) (gcc version >>> 4.8.5 (Gentoo 4.8.5 p1.3, pie-0.6.2) )

Re: Bad hard drive - checksum verify failure forces readonly mount

Chris Murphy posted on Thu, 23 Jun 2016 18:54:28 -0600 as excerpted: > From the pasted kernel messages: > >> Linux version 3.18.34-std473-amd64 (root@rl-sysrcd-p11) (gcc version >> 4.8.5 (Gentoo 4.8.5 p1.3, pie-0.6.2) ) #2 SMP Tue May 24 20:34:19 UTC >> 2016 > > > 3.18.34 is ancient. Find

Re: Bad hard drive - checksum verify failure forces readonly mount

On Thu, Jun 23, 2016 at 2:30 PM, Vasco Almeida wrote: > I was running OpenSuse Leap 42.1 with btrfs and > LVM (Logical Volume Management). > Last time I've checked smartd log, I noticed there were > 30 sector pending reallocation and 1 unrecoverable bad > sector on hard

Bad hard drive - checksum verify failure forces readonly mount

I was running OpenSuse Leap 42.1 with btrfs and LVM (Logical Volume Management). Last time I've checked smartd log, I noticed there were 30 sector pending reallocation and 1 unrecoverable bad sector on hard drive. I think my hard drive got some sector corrupted and now btrfs fails some checksum