Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>,
	linux-btrfs@vger.kernel.org
Subject: Re: mkfs.btrfs doesn't detect SSD
Date: Mon, 9 Nov 2015 08:39:56 -0500	[thread overview]
Message-ID: <5640A22C.2030604@gmail.com> (raw)
In-Reply-To: <1446910202.7774.5.camel@scientia.net>

[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]

On 2015-11-07 10:30, Christoph Anton Mitterer wrote:
> Hmm in fact it seems to be the kernel who wrongly, detects the type:
> /sys/block/sdb/queue/rotational = 1
> or more like the USB/SATA bridge simply reports it wrong.
>
> Anyway, is there a way to override? Or will setting
> /sys/block/sdb/queue/rotational = 0 give the expected behaviour?
This is a common issue with many USB/SATA bridges (and also 
device-mapper and MD devices), which don't properly query the attached 
device and modify the properties they report to the host system.  If you 
have some way to reliably identify this particular device, you could add 
a udev rule to automatically set it as non-rotational.  You could also 
do like you suggested and set it to non-rotational manually, although 
for mkfs at least, it's quicker to just manually specify '-m single'  on 
the command-line (that's the only difference in mkfs behavior for a 
SSD).  Like Chris said in his reply though, everything other than using 
single profile for metadata is done at mount time (if queue/rotational 
is 0, then -o ssd does get added to the mount options automatically, but 
it's a lot clearer to just specify the option yourself).


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]

      reply	other threads:[~2015-11-09 13:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-07 15:05 mkfs.btrfs doesn't detect SSD Christoph Anton Mitterer
2015-11-07 15:28 ` Chris Murphy
2015-11-07 15:30 ` Christoph Anton Mitterer
2015-11-09 13:39   ` Austin S Hemmelgarn [this message]

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=5640A22C.2030604@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=calestyo@scientia.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox