From: "Matthew Patton" <pattonme@yahoo.com>
To: linux-bcache@vger.kernel.org, Jakub Witkowski <skylynx@wp.pl>
Subject: Re: register_bcache() error opening /dev/md2: bad block/bucket size
Date: Sun, 15 Dec 2013 20:02:38 -0500 [thread overview]
Message-ID: <op.w75uiojsf3gqgg@desktop.patton.net> (raw)
In-Reply-To: <52AE4BD1.3080001@wp.pl>
On Sun, 15 Dec 2013 19:39:45 -0500, Jakub Witkowski <skylynx@wp.pl> wrote:
> to use larger block but bcache I think I use this. The another problem
> is that SSD's manufacturers don't release information about some basic
> info about SSD like page size or nand erase block size
Sometimes they post it in technical papers or will supply on request.
Regardless, optimization at this stage is a total waste of time, IMO.
Provision 25-30% spare area on your drive and let it do it's thing. Unless
you're in the habit of buying el-cheapo, cr*p drives (stay away from
low-priced consumer) the firmware is smart enough to do the right thing.
If you want consistent speed and reliable drives you MUST spend money and
get the professional or high-end gear.
prev parent reply other threads:[~2013-12-16 1:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-30 3:37 register_bcache() error opening /dev/md2: bad block/bucket size Paul B. Henson
2013-12-02 23:26 ` Paul B. Henson
2013-12-16 0:39 ` Jakub Witkowski
2013-12-16 1:02 ` Matthew Patton [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=op.w75uiojsf3gqgg@desktop.patton.net \
--to=pattonme@yahoo.com \
--cc=linux-bcache@vger.kernel.org \
--cc=skylynx@wp.pl \
/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