All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kyle Bentley <kwbent@uab.edu>
To: <linux-btrfs@vger.kernel.org>
Subject: Btrfs shows incorrect disk size after running a replace command
Date: Tue, 21 Jan 2014 07:35:19 -0600	[thread overview]
Message-ID: <52DE7797.30400@uab.edu> (raw)

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


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have just recently replaced two 750 GB disks with two 1 TB disks.  I
used the replace command to do so, aka "btrfs replace start /dev/sdX
/dev/sdY /mountpoint".  Each replacement went smoothly, with no errors
reporting.  I'm positive that the source and destination drives were
identified correctly.  However, when I run "btrfs filesystem show", the
output is

Label: none  uuid: b2dbc0e4-94fc-4089-9221-d79d7919f8cb
    Total devices 2 FS bytes used 494.23GB
    devid    2 size 698.64GB used 495.03GB path /dev/sda
    devid    1 size 698.64GB used 495.03GB path /dev/sdb

Btrfs v0.20-rc1

The disks show up as the 750 GB, when they are in fact 1 TB.  smartctl
for each drive shows

root@Lore:/home/kyle# smartctl -i /dev/sda |grep "User Capacity"
User Capacity:    1,000,204,886,016 bytes [1.00 TB]

root@Lore:/home/kyle# smartctl -i /dev/sdb |grep "User Capacity"
User Capacity:    1,000,204,886,016 bytes [1.00 TB]

Is there any harm in this?  If it is simply a superficial bug I will not
worry.  Would running a balance help?  As for the specifics, I'm using

Debian testing x64
Vanilla kernel 3.13.0
AMD hardware

Thanks,

Kyle Bentley

- ---------------------------------------
kwbent@uab.edu
UAB Dept of Physics
1300 University Blvd
CH 310
Birmingham, AL
- ---------------------------------------



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQEcBAEBAgAGBQJS3neNAAoJEKZ75usGhR84secH/iIbH/FcU3pTsg7+V9vwqMgB
VuQeZpU13RH/2fwupuFJtu4wK021xWLrSuN7nUGG0WzrWSmt8nHvQqIV1TBY+2PO
QqttgbBK5yDEIY6QB3lUn2fQDWohlrbG4/3CTjILoTdHWsihTBzXIug6D6aEpM1o
1b3smiBPM6mg6sy3d+JSr47TGi8Wko1QnOh2ory5FlkJMTZLDNWBqG2ja00B7W9H
UKnwgaU3KZr9UcbiVlvM1BLgDBxRZlhsjWMMo+diX92PHgaBovhEOzCrHI/nyXv7
vY3YKcwU1zH3f0olHXfp9lFjo06C/4/+EggCrQ3BEe0hxm5r3bHc44zrTCnH/Wg=
=a/VY
-----END PGP SIGNATURE-----


[-- Attachment #2: 0x06851F38.asc --]
[-- Type: application/pgp-keys, Size: 1714 bytes --]

             reply	other threads:[~2014-01-21 13:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-21 13:35 Kyle Bentley [this message]
2014-01-21 13:57 ` Btrfs shows incorrect disk size after running a replace command Andreas Fischer

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=52DE7797.30400@uab.edu \
    --to=kwbent@uab.edu \
    --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.