From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-btrfs-owner@vger.kernel.org>
Received: from mail0200.smtp25.com ([174.37.170.200]:42064 "EHLO
	mail0200.smtp25.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750964AbbJJXIT convert rfc822-to-8bit (ORCPT
	<rfc822;linux-btrfs@vger.kernel.org>);
	Sat, 10 Oct 2015 19:08:19 -0400
From: covici@ccs.covici.com
cc: Lionel Bouton <lionel+ceph@bouton.name>,
        =?us-ascii?Q?=3D=3Fus-ascii=3FQ=3F=3D3D=3D3FUTF-8=3D3FQ=3D3FHolger=3D5?=
	 =?us-ascii?Q?FHoffst=3D3Dc3=3D3Da4tte=3D3F=3D3D=3F=3D?=
	<holger.hoffstaette@googlemail.com>,
        linux-btrfs@vger.kernel.org
Subject: Re: btrfs says no errors, but booting gives lots of errors
In-reply-to: <27402.1444518173@ccs.covici.com>
References: <8042.1444481164@ccs.covici.com> <56191CC2.9000505@googlemail.com> <11640.1444488108@ccs.covici.com> <561932EF.2090005@bouton.name> <5619385C.7040103@googlemail.com> <16953.1444496102@ccs.covici.com> <56198B7B.90806@bouton.name> <27402.1444518173@ccs.covici.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Date: Sat, 10 Oct 2015 19:08:16 -0400
Message-ID: <27611.1444518496@ccs.covici.com>
To: unlisted-recipients:; (no To-header on input)
Sender: linux-btrfs-owner@vger.kernel.org
List-ID: <linux-btrfs.vger.kernel.org>

covici@ccs.covici.com wrote:

> Lionel Bouton <lionel+ceph@bouton.name> wrote:
> 
> > Le 10/10/2015 18:55, covici@ccs.covici.com a écrit :
> > > [...]
> > > But do you folks have any idea about my original question, this leads me
> > > to think that btrfs is too new or something.
> > 
> > I've seen a recent report of a problem with btrfs-progs 4.2 confirmed as
> > a bug in mkfs. As you created the filesystem with it, it could be the
> > problem.
> > Note that btrfs-progs 4.2 is marked ~amd64 on Gentoo: when you live on
> > the bleeding edge you shouldn't be surprised to bleed sometimes ;-)
> > 
> > You might have more luck by better describing the errors. Your title
> > mentions lots of errors, but there's only one log extract in a zip file
> > for a filesystem being mounted and it's only a warning about lock
> > contention which from an educated guess seems unlikely to make programs
> > crash.
> > I'm not familiar with the 203 exit codes you mention. This seems a
> > systemd thing with unclear meaning from a quick Google search so it
> > isn't really helpful unless there are kernel oops or panics for these
> > errors too.
> 
> These errors are not kernel panicks, they are just that systemd units
> are not starting and the programs that  are executed in the unit files
> are returning these errors such as the 203 with no other explanation.  I
> tried for instance to run /usr/bin/postgresql-9.4-check-db-dir and it
> said that postgresql.conf was missing, but I could do an ls on that file
> and got the name.  I think I have more like that, but no kernel errors
> and scrub has no errors.  Should I go back to an earlier btrfs progs
> and, if so, which one?

I do have 4.2.2, I could go to, would that be better?