From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.domeneshop.no ([194.63.252.55]:42765 "EHLO smtp.domeneshop.no" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750930AbbCaTSa (ORCPT ); Tue, 31 Mar 2015 15:18:30 -0400 Message-ID: <551AF2FF.6020708@skagestad.org> Date: Tue, 31 Mar 2015 21:18:23 +0200 From: =?UTF-8?B?VG9yYmrDuHJu?= MIME-Version: 1.0 To: Chris Mason CC: fdmanana@gmail.com, linux-btrfs Subject: Re: Linux 4.0.0-rc5 - [ 1851.858652] BTRFS: error (device sda1) in cleanup_transaction:1686: errno=-17 Object already exists References: <550FEC73.9010507@skagestad.org> <55100CE5.5020602@itpas.no> <1427118454.5707.5@mail.thefacebook.com> <55101A35.6020406@skagestad.org> <55103155.3040202@skagestad.org> <55198AF9.7090403@skagestad.org> <1427825525.24929.0@mail.thefacebook.com> In-Reply-To: <1427825525.24929.0@mail.thefacebook.com> Content-Type: text/plain; charset=utf-8; format=flowed Sender: linux-btrfs-owner@vger.kernel.org List-ID: On 03/31/2015 08:12 PM, Chris Mason wrote: > > > On Mon, Mar 30, 2015 at 1:42 PM, Torbjørn wrote: >> Hi, >> >> Just a follow up on this report. >> >> The file system in question is a raid1 across 2x320G old Western >> Digital WD3200KS. >> I janked them out of the server to run a fsck on another computer >> (after a proper shutdown). >> >> One of the disks did not get properly detected on the secondary >> computer. >> Hopefully the fsck of the single disk is still of some value to you. >> >> As you can see, there are several issues with the fs. >> The system has occasionally had hard reboots. >> >> The fs does not have any real value for me. Everything worth anything >> is backed up. >> I'll keep the drive around in case it's of any value for some devs. >> >> As noted before: this (corrupted) fs only get errors when booting >> into 4.0-rc5. With 4.0-rc4 or earlier it works as if nothing is wrong. > > This is really strange because we also have reports from v3.19 stable > kernels, but none of the btrfs patches between rc4 and rc5 were tagged > for stable. > > Can I convince you to hammer a bit more on rc4? I'd like to make sure > it really was a regression introdcued in rc5. > > -chris > > > > Perhaps I was a bit unclear. The error is triggered when booting into rc5. If I reset and try to start up rc4 or earlier, it is still there. After zero-log I can boot into rc4. I already did a fresh reinstall to alternative drives. I did not want to have the corrupted fs as root. I'm not sure I can get the second disk in the raid1 to work. It was head crashing when trying to attach it for fsck. If I somehow get it back online I can do some more testing. Anything in particular? -- Torbjørn