From: "Mike Audia" <mikey_a@gmx.com>
To: linux-btrfs@vger.kernel.org
Subject: Question about blocksize, I want to use 16k
Date: Sat, 10 Aug 2013 11:42:21 -0400 [thread overview]
Message-ID: <20130810154221.206170@gmx.com> (raw)
Wanting to use 16k block for my btrfs, I did so via:
# mkfs.btrfs -l 16k -s 16k -L arch64 -f /dev/sda3
WARNING! - Btrfs v0.20-rc1-253-g7854c8b IS EXPERIMENTAL
WARNING! - see http://btrfs.wiki.kernel.org before using
Detected a SSD, turning off metadata duplication. Mkfs with -m dup if you want to force metadata duplication.
fs created label arch64 on /dev/sda3
nodesize 16384 leafsize 16384 sectorsize 16384 size 119.00GB
Btrfs v0.20-rc1-253-g7854c8b
But when I tried to mount it, dmesg showed these errors aobut sector sizes:
# mount /dev/sda3 /newarch
mount: wrong fs type, bad option, bad superblock on /dev/sda3,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
[ 1463.366701] device label arch64 devid 1 transid 4 /dev/sda3
[ 1463.367186] btrfs: disk space caching is enabled
[ 1463.367189] btrfs flagging fs with big metadata feature
[ 1463.367539] btrfs: Incompatible sector size(16384) found on sda3
[ 1463.419215] btrfs: open_ctree failed
So I made the filesystem like this and all is well... what am I missing?
# mkfs.btrfs -l 16k -L arch64 -f /dev/sda3
WARNING! - Btrfs v0.20-rc1-253-g7854c8b IS EXPERIMENTAL
WARNING! - see http://btrfs.wiki.kernel.org before using
Detected a SSD, turning off metadata duplication. Mkfs with -m dup if you want to force metadata duplication.
fs created label arch64 on /dev/sda3
nodesize 16384 leafsize 16384 sectorsize 4096 size 119.00GB
Btrfs v0.20-rc1-253-g7854c8b
next reply other threads:[~2013-08-10 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-10 15:42 Mike Audia [this message]
2013-08-10 16:17 ` Question about blocksize, I want to use 16k Chris Murphy
2013-08-10 16:19 ` Chris Murphy
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=20130810154221.206170@gmx.com \
--to=mikey_a@gmx.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.