public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Shen Feng <shen@cn.fujitsu.com>
To: Liu Hui <onlyflyer@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: A bug with multiple devices?
Date: Wed, 31 Dec 2008 09:43:13 +0800	[thread overview]
Message-ID: <495ACE31.3050209@cn.fujitsu.com> (raw)
In-Reply-To: <2c3b11250812301717q7d54a8cdt6417d32468ea2eee@mail.gmail.com>



on 12/31/2008 09:17 AM, Liu Hui wrote:
> mkfs.btrfs -m raid1 just means 'meta data' works as raid1
> 
> You should try mkfs.btrfs -d raid1
> 
> This maybe help:
> mkfs.btrfs [-A <offset>] [-b <size>] [-l <size>] [-n <size>] [-l
> <label>] [-s <size>] [-m raid0|raid1|raid10|single] [-d
> raid0|raid1|raid10|single] <device>

Thanks.

The problem still exists with -d option.

[root@localhost ~]# mkfs.btrfs -m raid1 -d raid1 /dev/sdb8 /dev/sdb9 /dev/sdb10 /dev/sdb11
adding device /dev/sdb9 id 2
adding device /dev/sdb10 id 3
adding device /dev/sdb11 id 4
fs created label (null) on /dev/sdb8
	nodesize 4096 leafsize 4096 sectorsize 4096 size 74.50GB
Btrfs v0.16-29-g0d53b21
[root@localhost ~]# btrfsctl -a
Scanning for Btrfs filesystems
[root@localhost ~]#  mount -t btrfs /dev/sdb8 /mnt/btrfs
[root@localhost ~]# df -h /dev/sdb8
Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb8              75G   28K   75G   1% /mnt/btrfs
[root@localhost ~]# dd if=/dev/zero of=/mnt/btrfs/file bs=1024 count=1024
1024+0 records in
1024+0 records out
1048576 bytes (1.0 MB) copied, 0.0199063 s, 52.7 MB/s
[root@localhost ~]# sync
[root@localhost ~]# df -h /dev/sdb8
Filesystem            Size  Used Avail Use% Mounted on
/dev/sdb8              75G  1.1M   75G   1% /mnt/btrfs



> 
> 2008/12/31 Shen Feng <shen@cn.fujitsu.com>:
>>
>> on 12/30/2008 09:44 AM, Shen Feng wrote:
>>> Hi,
>>>
>>> I create a raid-1 btrfs with the following command.
>>>
>>> [root@localhost ~]# fdisk -l /dev/sdb
>>>
>>> Disk /dev/sdb: 320.0 GB, 320072933376 bytes
>>> 255 heads, 63 sectors/track, 38913 cylinders
>>> Units = cylinders of 16065 * 512 = 8225280 bytes
>>> Disk identifier: 0xb44829ea
>>>
>>>    Device Boot      Start         End      Blocks   Id  System
>>> /dev/sdb1               1        4863    39062016   83  Linux
>>> /dev/sdb2            4864        9726    39062047+  83  Linux
>>> /dev/sdb3            9727       38905   234375905+   f  W95 Ext'd (LBA)
>>> /dev/sdb5            9727       14590    39063374   83  Linux
>>> /dev/sdb6           14590       19453    39068690+   7  HPFS/NTFS
>>> /dev/sdb7           19454       29178    78116031   83  Linux
>>> /dev/sdb8           29179       31610    19535008+  83  Linux
>>> /dev/sdb9           31611       34041    19526976   83  Linux
>>> /dev/sdb10          34042       36473    19535008+  83  Linux
>>> /dev/sdb11          36474       38904    19526976   83  Linux
>>>
>>> [root@localhost ~]# mkfs.btrfs -m raid1 /dev/sdb8 /dev/sdb9 /dev/sdb10 /dev/sdb11
>>> adding device /dev/sdb9 id 2
>>> adding device /dev/sdb10 id 3
>>> adding device /dev/sdb11 id 4
>>> fs created label (null) on /dev/sdb8
>>>       nodesize 4096 leafsize 4096 sectorsize 4096 size 74.50GB
>>> Btrfs v0.16-29-g0d53b21
>>>
>>> [root@localhost ~]# mount -t btrfs /dev/sdb8 /mnt/btrfs[root@localhost ~]# df
>>> Filesystem           1K-blocks      Used Available Use% Mounted on
>>> ...
>>> /dev/sdb8             78123968        28  78123940   1% /mnt/btrfs
>>>
>> More test:
>>
>> [root@localhost btrfs]# df -h /dev/sdb8
>> Filesystem            Size  Used Avail Use% Mounted on
>> /dev/sdb8              75G   28K   75G   1% /mnt/btrfs
>> [root@localhost btrfs]# dd if=/dev/zero of=/mnt/btrfs/file bs=1024 count=1024
>> 1024+0 records in
>> 1024+0 records out
>> 1048576 bytes (1.0 MB) copied, 0.0481317 s, 21.8 MB/s
>> [root@localhost btrfs]# sync
>> [root@localhost btrfs]# df -h /dev/sdb8
>> Filesystem            Size  Used Avail Use% Mounted on
>> /dev/sdb8              75G  1.1M   75G   1% /mnt/btrfs
>>
>> With raid-1, the used space may be double (about 2.2M), I think.
>>
>>
>>
>>> I think the partition size is no correct since this is a raid-1 partition.
>>> The size should be half.
>>> Is this a bug?
>>>
>>> -Shen
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>
>>>
>> --
>> Best Regards,
>> --------------------------------------------------
>> Shen Feng
>> Development Dept.I
>> Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
>> 8/F., Civil Defense Building, No.189 Guangzhou Road,
>> Nanjing, 210029, China
>> PHONE: +86-25-86630566-950
>> COINS: 79955-950
>> FAX: +86-25-83317685
>> MAIL: shen@cn.fujitsu.com
>> -------------------------------------------------
>> This communication is for use by the intended recipient(s) only and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not an intended recipient of this communication, you are hereby notified that any dissemination, distribution or copying hereof is strictly prohibited.  If you have received this communication in error, please notify me by reply e-mail, permanently delete this communication from your system, and destroy any hard copies you may have printed.
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
> 
> 
> 

-- 
Best Regards,
--------------------------------------------------
Shen Feng
Development Dept.I
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
8/F., Civil Defense Building, No.189 Guangzhou Road,
Nanjing, 210029, China
PHONE: +86-25-86630566-950
COINS: 79955-950
FAX: +86-25-83317685
MAIL: shen@cn.fujitsu.com
-------------------------------------------------
This communication is for use by the intended recipient(s) only and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not an intended recipient of this communication, you are hereby notified that any dissemination, distribution or copying hereof is strictly prohibited.  If you have received this communication in error, please notify me by reply e-mail, permanently delete this communication from your system, and destroy any hard copies you may have printed.

  reply	other threads:[~2008-12-31  1:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-30  1:44 A bug with multiple devices? Shen Feng
2008-12-30 10:45 ` Chris Samuel
2008-12-30 11:14   ` Chris Samuel
2008-12-30 21:19     ` Chris Mason
2008-12-30 11:35   ` Yan Zheng
2008-12-30 12:03     ` Chris Samuel
2008-12-30 12:19     ` Chris Samuel
2008-12-31  1:11 ` Shen Feng
2008-12-31  1:17   ` Liu Hui
2008-12-31  1:43     ` Shen Feng [this message]
2009-01-01  0:52       ` Chris Samuel
2008-12-31  3:30     ` Shen Feng

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=495ACE31.3050209@cn.fujitsu.com \
    --to=shen@cn.fujitsu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=onlyflyer@gmail.com \
    /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