search for: 28tb

Hello again, Been an interesting day. I'm attempting to use parted to create a partition on a 28TB volume which consists of 16x2TB drives configuired in a Raid 5 + spare, so total unformatted size is 28TB to the OS.. However upon entering parted, and making a gpt label, print reports back as follows; Model: Areca ARC-1680-VOL#000 (scsi) Disk /dev/sdc: 2199GB Sector Size (logical/physical...

...g to setup Gluster for our project/scratch storage HPC machine using a replicated mode with 2 nodes, 2 bricks each (14tb each). Our goal is to be able to have a replicated system between node 1 and 2 (A bricks) and add an additional 2 bricks (B bricks) from the 2 nodes. so we can have a total of 28tb replicated mode. Node 1 [ (Brick A) (Brick B) ] Node 2 [ (Brick A) (Brick B) ] -------------------------------------------- 14Tb + 14Tb = 28Tb At this I was able to create the replica nodes between node 1 and 2 (brick A) but I?ve not been able to add to the replica together, Gluster switches...

I think I have the same problems as: http://gluster.org/pipermail/gluster-users/2011-June/007980.html and http://gluster.org/pipermail/gluster-users/2011-May/007697.html Recently I installed Glusterfs 3.2.0 on four workstations which share a total of 28TB of disk-space between them for batch processing of FMRI and DTI data. Had the same setup between three workstations and 9TB with Glusterfs 3.0.4 for over a year, but the hard-disk pool was to small. The three "old" workstations from the old cluster and two more will also access the 28TB p...

...our project/scratch storage HPC machine > using a replicated mode with 2 nodes, 2 bricks each (14tb each). > > Our goal is to be able to have a replicated system between node 1 and 2 (A > bricks) and add an additional 2 bricks (B bricks) from the 2 nodes. so we > can have a total of 28tb replicated mode. > > Node 1 [ (Brick A) (Brick B) ] > Node 2 [ (Brick A) (Brick B) ] > -------------------------------------------- > 14Tb + 14Tb = 28Tb > > At this I was able to create the replica nodes between node 1 and 2 > (brick A) but I?ve not been able to add to the...

...Gluster for our project/scratch storage HPC machine using a replicated mode with 2 nodes, 2 bricks each (14tb each). > > Our goal is to be able to have a replicated system between node 1 and 2 (A bricks) and add an additional 2 bricks (B bricks) from the 2 nodes. so we can have a total of 28tb replicated mode. > > Node 1 [ (Brick A) (Brick B) ] > Node 2 [ (Brick A) (Brick B) ] > -------------------------------------------- > 14Tb + 14Tb = 28Tb > > At this I was able to create the replica nodes between node 1 and 2 (brick A) but I?ve not been able to add to the...

...istributed-Replicate indicates the volume is both distributed (as in files will only be created on one of the replicated sets) and replicated. So in the above example, a file will exist on either Brick1 and Brick2 or Brick3 and Brick4. After the add brick, the volume will have a total capacity of 28TB and store 2 copies of every file. Let me know if that is not what you are looking for. Regards, Nithya On 10 January 2018 at 20:40, Jose Sanchez <josesanc at carc.unm.edu> wrote: > > > Hi Nithya > > This is what i have so far, I have peer both cluster nodes together as &gt...

...ate indicates the volume is both distributed (as in files will only be created on one of the replicated sets) and replicated. So in the above example, a file will exist on either Brick1 and Brick2 or Brick3 and Brick4. > > > After the add brick, the volume will have a total capacity of 28TB and store 2 copies of every file. Let me know if that is not what you are looking for. > > > Regards, > Nithya > > > On 10 January 2018 at 20:40, Jose Sanchez <josesanc at carc.unm.edu <mailto:josesanc at carc.unm.edu>> wrote: > > > Hi Nithya > &g...

...es the volume is both > distributed (as in files will only be created on one of the replicated > sets) and replicated. So in the above example, a file will exist on either > Brick1 and Brick2 or Brick3 and Brick4. > > > After the add brick, the volume will have a total capacity of 28TB and > store 2 copies of every file. Let me know if that is not what you are > looking for. > > > Regards, > Nithya > > > On 10 January 2018 at 20:40, Jose Sanchez <josesanc at carc.unm.edu> wrote: > >> >> >> Hi Nithya >> >> This is w...

...istributed-Replicate indicates the volume is both distributed (as in files will only be created on one of the replicated sets) and replicated. So in the above example, a file will exist on either Brick1 and Brick2 or Brick3 and Brick4. After the add brick, the volume will have a total capacity of 28TB and store 2 copies of every file. Let me know if that is not what you are looking for. Regards, Nithya On 10 January 2018 at 20:40, Jose Sanchez <josesanc at carc.unm.edu> wrote: > > > Hi Nithya > > This is what i have so far, I have peer both cluster nodes together as &gt...

...ain distribute. Then simply adding the bricks without specifying any "#" will expand the volume as a plain distribute volue. > > Im planning on moving with this changes in few days. At this point each > brick has 14tb and adding bricks 1 from node A and B, i have a total of > 28tb, After doing all the process, (removing and adding bricks) I should be > able to see a total of 56Tb right ? > Yes after all these you will have 56TB in total. After adding the bricks, do volume rebalance, so that the data which were present previously, will be moved to the correct bricks. H...

...volume plain distribute. Then simply adding the bricks without specifying any "#" will expand the volume as a plain distribute volue. > > Im planning on moving with this changes in few days. At this point each brick has 14tb and adding bricks 1 from node A and B, i have a total of 28tb, After doing all the process, (removing and adding bricks) I should be able to see a total of 56Tb right ? > Yes after all these you will have 56TB in total. > After adding the bricks, do volume rebalance, so that the data which were present previously, will be moved to the correct bricks. &g...

...plain distribute. Then simply adding the bricks without specifying any "#" will expand the volume as a plain distribute volue. >> >> Im planning on moving with this changes in few days. At this point each brick has 14tb and adding bricks 1 from node A and B, i have a total of 28tb, After doing all the process, (removing and adding bricks) I should be able to see a total of 56Tb right ? >> Yes after all these you will have 56TB in total. >> After adding the bricks, do volume rebalance, so that the data which were present previously, will be moved to the correct br...

...dding the bricks without specifying any "#" > will expand the volume as a plain distribute volue. >> >> >> Im planning on moving with this changes in few days. At this point each >> brick has 14tb and adding bricks 1 from node A and B, i have a total of >> 28tb, After doing all the process, (removing and adding bricks) I should be >> able to see a total of 56Tb right ? > > Yes after all these you will have 56TB in total. > After adding the bricks, do volume rebalance, so that the data which were > present previously, will be moved to the...

...pecifying any "#" >> will expand the volume as a plain distribute volue. >>> >>> >>> Im planning on moving with this changes in few days. At this point each >>> brick has 14tb and adding bricks 1 from node A and B, i have a total of >>> 28tb, After doing all the process, (removing and adding bricks) I should be >>> able to see a total of 56Tb right ? >> >> Yes after all these you will have 56TB in total. >> After adding the bricks, do volume rebalance, so that the data which were >> present previously,...

.... Then simply adding the bricks without specifying any "#" > will expand the volume as a plain distribute volue. > > > > Im planning on moving with this changes in few days. At this point each > brick has 14tb and adding bricks 1 from node A and B, i have a total of > 28tb, After doing all the process, (removing and adding bricks) I should be > able to see a total of 56Tb right ? > > > Yes after all these you will have 56TB in total. > After adding the bricks, do volume rebalance, so that the data which were > present previously, will be moved to th...