public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Can't create valid btrfs on NVMe
Date: Thu, 18 Aug 2016 09:38:03 -0400	[thread overview]
Message-ID: <CAGfcS_mxTj_bfDvZQmqP01WNHXWrJXjgPK6HCxtwQk862a-dAA@mail.gmail.com> (raw)
In-Reply-To: <2035119.Y6fIYWEQZY@andromeda>

On Thu, Aug 18, 2016 at 8:57 AM, J. Roeleveld <joost@antarean.org> wrote:
> On Wednesday, August 17, 2016 11:26:13 PM Neil Bothwick wrote:
>> I'm putting together a new desktop using a Samsung SM951 NVMe drive. I
>> booted sysrescd, partitioned the drive and ran
>>
>> mkfs.btrfs /dev/nvme0n1p3
>> mount /dev/nvme0n1p3 /mnt/custom
>>
>> df -T, mount and findmnt all show this is mounted as a btrfs filesystem,
>> e.g.
>>
>> /dev/nvme0n1p3 on /mnt/custom type btrfs (rw,relatime,ssd,space_cache)
>>
>> I can create files in here but cannot do anything btrfs-y
>>
>> % btrfs filesystem show /mnt/custom
>> ERROR: not a valid btrfs filesystem: /mnt/custom
>>
>> % btrfs subvolume create /mnt/custom/test
>> Create subvolume '/mnt/custom/test'
>> ERROR: cannot create subvolume: Inappropriate ioctl for device
>>
>> Google has been no help at all.
>
> I've got a similar drive in my desktop and it actually works.
> Difference: I am using Ext4.
>
> Can you try Ext4 and see if it works?
> Next test: Does it work with a non-NVMe drive?
>
> Also, which kernel version?

I think you guys are going down the wrong road.  The kernel drivers
are almost certainly working for the drive, otherwise the filesystem
wouldn't work at all, and I'm sure a million ext4 users would have
noticed a problem by now.

This is almost certainly a bug in btrfs-progs, or maybe the btrfs
filesystem driver in the kernel.

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.

-- 
Rich


  reply	other threads:[~2016-08-18 13:38 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 [this message]
2016-08-18 13:47     ` Neil Bothwick
2016-09-02  1:07       ` [gentoo-user] " Kai Krakow
2016-09-02  9:03         ` 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=CAGfcS_mxTj_bfDvZQmqP01WNHXWrJXjgPK6HCxtwQk862a-dAA@mail.gmail.com \
    --to=rich0@gentoo.org \
    --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