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

2016-07-05 Thread Vasco Almeida
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

2016-06-26 Thread Vasco Almeida
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/6694593

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

2016-06-26 Thread Vasco Almeida
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 isn

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

2016-06-25 Thread Vasco Almeida
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 [ 1838.006038] BTRFS info (device dm-9): relocating block group 15799943168

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

2016-06-24 Thread Vasco Almeida
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 20:34:19 UTC 2016 3.18.34 is ancient

Bad hard drive - checksum verify failure forces readonly mount

2016-06-23 Thread Vasco Almeida
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 and