From: Lionel Bouton <lionel+ceph@bouton.name>
To: covici@ccs.covici.com,
"Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs says no errors, but booting gives lots of errors
Date: Sun, 11 Oct 2015 00:04:43 +0200 [thread overview]
Message-ID: <56198B7B.90806@bouton.name> (raw)
In-Reply-To: <16953.1444496102@ccs.covici.com>
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.
Lionel
next prev parent reply other threads:[~2015-10-10 22:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-10 12:46 btrfs says no errors, but booting gives lots of errors covici
2015-10-10 14:12 ` Holger Hoffstätte
2015-10-10 14:41 ` covici
2015-10-10 15:46 ` Lionel Bouton
2015-10-10 16:10 ` Holger Hoffstätte
2015-10-10 16:55 ` covici
2015-10-10 22:04 ` Lionel Bouton [this message]
2015-10-10 23:02 ` covici
2015-10-10 23:08 ` covici
2015-10-11 12:13 ` Duncan
2015-10-11 12:29 ` covici
2015-10-15 2:10 ` Duncan
2015-10-10 23:21 ` Lionel Bouton
2015-10-10 23:32 ` covici
2015-10-10 23:58 ` Lionel Bouton
2015-10-11 0:28 ` covici
2015-10-10 16:45 ` covici
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56198B7B.90806@bouton.name \
--to=lionel+ceph@bouton.name \
--cc=covici@ccs.covici.com \
--cc=holger.hoffstaette@googlemail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.