From: Kai Krakow <hurikhan77@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Can't create valid btrfs on NVMe
Date: Fri, 2 Sep 2016 03:07:31 +0200 [thread overview]
Message-ID: <20160902030731.1b5cfc07@jupiter.sol.kaishome.de> (raw)
In-Reply-To: 20160818144707.03e54015@digimed.co.uk
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
Am Thu, 18 Aug 2016 14:47:07 +0100
schrieb Neil Bothwick <neil@digimed.co.uk>:
> On Thu, 18 Aug 2016 09:38:03 -0400, Rich Freeman wrote:
>
> > This is almost certainly a bug in btrfs-progs, or maybe the btrfs
> > filesystem driver in the kernel.
>
> The latter, a later kernel appears to have done the trick.
>
> > I'd suggest raising this on the btrfs mailing list, where it is
> > going to get a lot more attention from the people who develop
> > btrfs. There are a few of us who use it around here, but I'd have
> > to spend a day tweaking the btrfs-progs source to have a guess at
> > where this is bailing out. I suspect somebody over there would
> > have an answer almost immediately.
>
> As our resident btrfs expert, I was expecting you to come up with an
> immediate answer ;-)
Have you tried an explicit "btrfs dev scan"? If that helps, problems
maybe arise from the udev rules...
--
Regards,
Kai
Replies to list-only preferred.
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-09-02 1:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 22:26 [gentoo-user] Can't create valid btrfs on NVMe Neil Bothwick
2016-08-18 5:56 ` Adam Carter
2016-08-18 9:06 ` Peter Humphrey
2016-08-18 10:49 ` james
2016-08-18 12:57 ` J. Roeleveld
2016-08-18 13:38 ` Rich Freeman
2016-08-18 13:47 ` Neil Bothwick
2016-09-02 1:07 ` Kai Krakow [this message]
2016-09-02 9:03 ` [gentoo-user] " Neil Bothwick
2016-08-18 13:45 ` [gentoo-user] " Neil Bothwick
2016-08-18 14:15 ` Rich Freeman
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=20160902030731.1b5cfc07@jupiter.sol.kaishome.de \
--to=hurikhan77@gmail.com \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox