search for: ab8b

Displaying 8 results from an estimated 8 matches for "ab8b".

Did you mean: ab8a
2018 Jan 10
2
Creating cluster replica on 2 nodes 2 bricks each.
...Y 2626 Task Status of Volume scratch ------------------------------------------------------------------------------ There are no active volume tasks [root at gluster01 ~]# [root at gluster01 ~]# gluster volume info Volume Name: scratch Type: Replicate Volume ID: a6e20f7d-13ed-4293-ab8b-d783d1748246 Status: Started Snapshot Count: 0 Number of Bricks: 1 x 2 = 2 Transport-type: tcp,rdma Bricks: Brick1: gluster01ib:/gdata/brick1/scratch Brick2: gluster02ib:/gdata/brick1/scratch Options Reconfigured: performance.readdir-ahead: on nfs.disable: on [root at gluster01 ~]# --------------...
2018 Jan 10
0
Creating cluster replica on 2 nodes 2 bricks each.
Hi, Please let us know what commands you ran so far and the output of the *gluster volume info* command. Thanks, Nithya On 9 January 2018 at 23:06, Jose Sanchez <josesanc at carc.unm.edu> wrote: > Hello > > We are trying 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
2018 Jan 11
0
Creating cluster replica on 2 nodes 2 bricks each.
...---------------------------------------------------- > ------------------ > There are no active volume tasks > > > [root at gluster01 ~]# > > [root at gluster01 ~]# gluster volume info > > > Volume Name: scratch > Type: *Replicate* > Volume ID: a6e20f7d-13ed-4293-ab8b-d783d1748246 > Status: Started > Snapshot Count: 0 > Number of Bricks: 1 x 2 = 2 > Transport-type: tcp,rdma > Bricks: > Brick1: gluster01ib:/gdata/brick1/scratch > Brick2: gluster02ib:/gdata/brick1/scratch > Options Reconfigured: > performance.readdir-ahead: on > nfs.d...
2018 Jan 09
2
Creating cluster replica on 2 nodes 2 bricks each.
Hello We are trying 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
2018 Jan 11
3
Creating cluster replica on 2 nodes 2 bricks each.
...> ------------------------------------------------------------------------------ > There are no active volume tasks > > [root at gluster01 ~]# > > [root at gluster01 ~]# gluster volume info > > Volume Name: scratch > Type: Replicate > Volume ID: a6e20f7d-13ed-4293-ab8b-d783d1748246 > Status: Started > Snapshot Count: 0 > Number of Bricks: 1 x 2 = 2 > Transport-type: tcp,rdma > Bricks: > Brick1: gluster01ib:/gdata/brick1/scratch > Brick2: gluster02ib:/gdata/brick1/scratch > Options Reconfigured: > performance.readdir-ahead: on > nfs.d...
2018 Jan 15
1
Creating cluster replica on 2 nodes 2 bricks each.
...-------------------------------------------------- >> There are no active volume tasks >> >> [root at gluster01 ~]# >> >> [root at gluster01 ~]# gluster volume info >> >> Volume Name: scratch >> Type: *Replicate* >> Volume ID: a6e20f7d-13ed-4293-ab8b-d783d1748246 >> Status: Started >> Snapshot Count: 0 >> Number of Bricks: 1 x 2 = 2 >> Transport-type: tcp,rdma >> Bricks: >> Brick1: gluster01ib:/gdata/brick1/scratch >> Brick2: gluster02ib:/gdata/brick1/scratch >> Options Reconfigured: >> perf...
2018 Jan 12
0
Creating cluster replica on 2 nodes 2 bricks each.
...; ------------------------------------------------------------ > ------------------ > There are no active volume tasks > > [root at gluster01 ~]# > > [root at gluster01 ~]# gluster volume info > > Volume Name: scratch > Type: *Replicate* > Volume ID: a6e20f7d-13ed-4293-ab8b-d783d1748246 > Status: Started > Snapshot Count: 0 > Number of Bricks: 1 x 2 = 2 > Transport-type: tcp,rdma > Bricks: > Brick1: gluster01ib:/gdata/brick1/scratch > Brick2: gluster02ib:/gdata/brick1/scratch > Options Reconfigured: > performance.readdir-ahead: on > nfs.d...
2008 Jun 30
4
Rebuild of kernel 2.6.9-67.0.20.EL failure
Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking