From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 4D5F113832E for ; Thu, 18 Aug 2016 05:57:03 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DCDABE09FC; Thu, 18 Aug 2016 05:56:53 +0000 (UTC) Received: from mail-wm0-f67.google.com (mail-wm0-f67.google.com [74.125.82.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id BC27BE09B2 for ; Thu, 18 Aug 2016 05:56:52 +0000 (UTC) Received: by mail-wm0-f67.google.com with SMTP id q128so3082847wma.1 for ; Wed, 17 Aug 2016 22:56:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=0MvRT8CFsVclU1cx088zjwpihJUNPEoTxzI6saRAFZ4=; b=rVAj5BRdN8zM6dAElk+p2ntEShSpGp7m1f/5wQ/yMlxuRhEJ5SXGS7UL3KEFzLrXeS HzNYBVxXGE113xvQRLpGs0HOOZeUcg/y8xk0QIU/cy7xUmalt6xdf8Joxo6pWTB6RG/Q +eDw1UcSD9irpRBCHzvPqNq4d5zMs/RxPL+EIP3ZQ7ED4MpH2V9D0dBk410Mb8uiVrbH 5GeCx60apuZRDCPYoCXHMs1s1a9ZkmscxF71AlwdO9Nif1aFkw/3DpS/eYT4nNZqxxuj XIBSmbpQPVCCO1TzlsOQmY1flqm8pfkbqkFZqxEqNPj8iGsz3H/PFdn0wONycoysPx7g Moug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=0MvRT8CFsVclU1cx088zjwpihJUNPEoTxzI6saRAFZ4=; b=AgaGeCYzGYDrXgIRIc+EnCLlNmPI3Btxwitu3iNKrjQnNIoALBJnR0T7Qj6DZknhFL kvqFjQQOYTXqCH7JlB7ZGCnc1Z/qy0Hl426+e/qtBQHXuTY3bLfki5ARb4jYLTnU3jI+ mDzjZvFqA+Pl30SSdRp7KMzwcHJ0DVDknpdbPga8B8orY9VRP6r5qUImho/4ZH/StB81 5XO0ZTEgZFqK1uBJmTIsD4/gOztp6+KpI7tdN9u5LsVoC0U06nAzMULNEPPs6sKSJ0wJ j7/U3QfhCWeqnPP6AM8t35ZeHbp5ZvW9EFmPyBupHS042fGVVxx2sDVnJNlaxzh+Gq4q fOOg== X-Gm-Message-State: AEkoouv4ayY0ahVKy353dT+4J/ng0ctJKdYslh2U7VxAEcqXQ1akhHE+eutKeIFkf0iHYWtTO33w6yMsYb0FqA== X-Received: by 10.28.39.134 with SMTP id n128mr28347761wmn.60.1471499811069; Wed, 17 Aug 2016 22:56:51 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.194.178.167 with HTTP; Wed, 17 Aug 2016 22:56:50 -0700 (PDT) In-Reply-To: <20160817232613.47d780b3@digimed.co.uk> References: <20160817232613.47d780b3@digimed.co.uk> From: Adam Carter Date: Thu, 18 Aug 2016 15:56:50 +1000 Message-ID: Subject: Re: [gentoo-user] Can't create valid btrfs on NVMe To: "gentoo-user@lists.gentoo.org" Content-Type: multipart/alternative; boundary=001a114e212686a34a053a523f3c X-Archives-Salt: 432af2be-7f3b-4c53-9a7f-4d3a3fa86921 X-Archives-Hash: 70563b72210e5c0bff2f312c57b0c1d8 --001a114e212686a34a053a523f3c Content-Type: text/plain; charset=UTF-8 On Thu, Aug 18, 2016 at 8:26 AM, 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'm assuming tools are expecting SATA (or SCSI) and need an update or alternative for nvm; # hdparm -i /dev/nvme0n1 /dev/nvme0n1: HDIO_DRIVE_CMD(identify) failed: Inappropriate ioctl for device HDIO_GET_IDENTITY failed: Inappropriate ioctl for device Maybe SCSI emulation could work around it? CONFIG_BLK_DEV_NVME_SCSI --001a114e212686a34a053a523f3c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= hu, Aug 18, 2016 at 8:26 AM, Neil Bothwick <neil@digimed.co.uk> wrote:
I'm pu= tting 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'm assuming tools are expecting SATA (or SCSI) and need an updat= e or alternative for nvm;

# hdparm -i /dev/nvme0n1

/dev/nvme0= n1:
=C2=A0HDIO_DRIVE_CMD(identify) failed: Inappropriate ioctl for devic= e
=C2=A0HDIO_GET_IDENTITY failed: Inappropriate ioctl for device
=C2= =A0
Maybe SCSI emulation could work around it?
CONFIG_BLK_= DEV_NVME_SCSI
--001a114e212686a34a053a523f3c--