Hello, I have a 3 1TB drives that I wanted to make a Raid1 system on. I issued the following command "mkfs.btrfs -m raid1 -d raid1 /dev/sdb /dev/sdc /dev/sdd" And it seems to have created the fs, with no issue. When I do an df -h, I see that the available space is 3TB. Seems like with RAID1 I would only see 1TB available, and the other two drives would mirror the first. Am I misunderstanding how the RAID1 works under btrfs? Can you have more than two drives in RAID1 in btrfs, so you can survive multiple drive failures? Is there a better option with only 3 drives? I am not wedded to RAID1 if there is a better way. Here is my uname -a: Linux gemini 2.6.31-19-generic #56-Ubuntu SMP Thu Jan 28 01:26:53 UTC 2010 i686 GNU/Linux And I am using btrfs 0.19. Thank you, -- 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
On Fri, Mar 05, 2010 at 01:28:00PM -0600, Grady Neely wrote:> Hello, > > I have a 3 1TB drives that I wanted to make a Raid1 system on. I issued the following command "mkfs.btrfs -m raid1 -d raid1 /dev/sdb /dev/sdc /dev/sdd" And it seems to have created the fs, with no issue. When I do an df -h, I see that the available space is 3TB. Seems like with RAID1 I would only see 1TB available, and the other two drives would mirror the first. Am I misunderstanding how the RAID1 works under btrfs? Can you have more than two drives in RAID1 in btrfs, so you can survive multiple drive failures? Is there a better option with only 3 drives? I am not wedded to RAID1 if there is a better way. > >DF with btrfs is a loaded question. In the RAID1 case you are going to show 3TB of free space, but everytime you use some space you are going to show 3 times the amount used (I think thats right). There are some patches forthcoming to make the reporting for RAID stuff make more sense, but for the time being just ignore df. Thanks, Josef -- 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
Hi, > DF with btrfs is a loaded question. In the RAID1 case you are > going to show 3TB of free space, but everytime you use some space > you are going to show 3 times the amount used (I think thats > right). There are some patches forthcoming to make the reporting > for RAID stuff make more sense, but for the time being just > ignore df. Added to: http://btrfs.wiki.kernel.org/index.php/FAQ#Why_does_df_show_incorrect_free_space_for_my_RAID_volume.3F since we''re often seeing this question on the list and IRC. - Chris. -- Chris Ball <cjb@laptop.org> One Laptop Per Child -- 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
Thank you! One more question: Since I have three devices in a RAID1 pool, can it survive 2 drive failures? On Mar 5, 2010, at 1:58 PM, Chris Ball wrote:> Hi, > >> DF with btrfs is a loaded question. In the RAID1 case you are >> going to show 3TB of free space, but everytime you use some space >> you are going to show 3 times the amount used (I think thats >> right). There are some patches forthcoming to make the reporting >> for RAID stuff make more sense, but for the time being just >> ignore df. > > Added to: > > http://btrfs.wiki.kernel.org/index.php/FAQ#Why_does_df_show_incorrect_free_space_for_my_RAID_volume.3F > > since we''re often seeing this question on the list and IRC. > > - Chris. > -- > Chris Ball <cjb@laptop.org> > One Laptop Per Child-- 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
On Fri, Mar 05, 2010 at 02:29:56PM -0600, Grady Neely wrote:> Thank you! > > One more question: > > Since I have three devices in a RAID1 pool, can it survive 2 drive failures? >Yes, tho you won''t be able to remove more than 1 at a time (since it wants you to keep at least two disks around). Thanks, Josef -- 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
On Fri, Mar 5, 2010 at 21:31, Josef Bacik <josef@redhat.com> wrote:>> Since I have three devices in a RAID1 pool, can it survive 2 drive failures? > > Yes, tho you won''t be able to remove more than 1 at a time (since it wants you > to keep at least two disks around). Thanks, > > JosefHmm, I would expect the raid1 data mode to keep 2 copies of each file and thus yield 50% effective storage capacity, even with 3 disks. I see no real reason to stick with the full-disk mirroring mentality of previous raid systems since raid implemented in a filesystem works differently. Or would it be difficult to implement btrfs raid1 like this? Maybe it''s worth to consider leaving the burdened raid* terminology behind and name the btrfs redundancy modes more clearly by what they do. For instance "-d double|triple" or "-d 2n|3n". And for raid5/6 "-d single-parity|double-parity" or "-d n+1|n+2". Regards, Bart -- 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
On Fri, Mar 5, 2010 at 1:49 PM, Bart Noordervliet <bart@noordervliet.net> wrote:> On Fri, Mar 5, 2010 at 21:31, Josef Bacik <josef@redhat.com> wrote: >>> Since I have three devices in a RAID1 pool, can it survive 2 drive failures? >> >> Yes, tho you won''t be able to remove more than 1 at a time (since it wants you >> to keep at least two disks around). Thanks, >> >> Josef > > Hmm, I would expect the raid1 data mode to keep 2 copies of each file > and thus yield 50% effective storage capacity, even with 3 disks. I > see no real reason to stick with the full-disk mirroring mentality of > previous raid systems since raid implemented in a filesystem works > differently. Or would it be difficult to implement btrfs raid1 like > this? > > Maybe it''s worth to consider leaving the burdened raid* terminology > behind and name the btrfs redundancy modes more clearly by what they > do. For instance "-d double|triple" or "-d 2n|3n". And for raid5/6 "-d > single-parity|double-parity" or "-d n+1|n+2". >+1 -- 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
On Friday 05 March 2010 23:13:54 Mike Fedyk wrote:> On Fri, Mar 5, 2010 at 1:49 PM, Bart Noordervliet <bart@noordervliet.net>wrote:> > Maybe it''s worth to consider leaving the burdened raid* terminology > > behind and name the btrfs redundancy modes more clearly by what they > > do. For instance "-d double|triple" or "-d 2n|3n". And for raid5/6 "-d > > single-parity|double-parity" or "-d n+1|n+2". > > +1Good idea IMHO. When we will be able to specify the redundancy modes on a file by file basis it will make it much less confusig for the users to talk about double, triple replication or [single|double]-parity. It''s a bit silly to talk about "Arrays of Disks" when we mean groups of blocks. -- Hubert Kario QBS - Quality Business Software ul. Ksawerów 30/85 02-656 Warszawa POLAND tel. +48 (22) 646-61-51, 646-74-24 fax +48 (22) 646-61-50 -- 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
On 03/05/10 15:49, Bart Noordervliet wrote:> On Fri, Mar 5, 2010 at 21:31, Josef Bacik<josef@redhat.com> wrote: >>> Since I have three devices in a RAID1 pool, can it survive 2 drive failures? >> >> Yes, tho you won''t be able to remove more than 1 at a time (since it wants you >> to keep at least two disks around). Thanks, >> >> Josef > > Hmm, I would expect the raid1 data mode to keep 2 copies of each file > and thus yield 50% effective storage capacity, even with 3 disks. I > see no real reason to stick with the full-disk mirroring mentality of > previous raid systems since raid implemented in a filesystem works > differently. Or would it be difficult to implement btrfs raid1 like > this? > > Maybe it''s worth to consider leaving the burdened raid* terminology > behind and name the btrfs redundancy modes more clearly by what they > do. For instance "-d double|triple" or "-d 2n|3n". And for raid5/6 "-d > single-parity|double-parity" or "-d n+1|n+2". > > Regards, > > Bart > -- > 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 >This would be pretty excellent - there''s a real need for a storage system where you can just give it a bunch of disks and a policy, and let the system worry about the details. Current RAID implementations are pretty inflexible, for example when dealing with disks of varying size. --Ravi -- 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