Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster, 2016-03-13

| Channels | #gluster index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:01 haomaiwa_ joined #gluster
00:04 Merlin_ joined #gluster
00:23 Merlin_ joined #gluster
00:31 plarsen joined #gluster
00:39 Merlin_ joined #gluster
00:42 RameshN joined #gluster
00:46 Merlin__ joined #gluster
00:55 beeradb_ joined #gluster
01:01 haomaiwa_ joined #gluster
01:15 Wizek joined #gluster
01:15 Wizek_ joined #gluster
01:20 Merlin_ joined #gluster
01:30 Merlin_ joined #gluster
01:44 Wizek joined #gluster
01:54 ovaistariq joined #gluster
01:56 DV joined #gluster
02:01 haomaiwa_ joined #gluster
02:02 baojg joined #gluster
02:07 Merlin__ joined #gluster
02:18 Merlin_ joined #gluster
02:38 johnmilton joined #gluster
02:41 Merlin_ joined #gluster
02:56 dlambrig_ joined #gluster
03:01 haomaiwang joined #gluster
03:02 Merlin_ joined #gluster
03:05 LessSeen_ joined #gluster
03:13 beeradb_ joined #gluster
03:19 ovaistariq joined #gluster
03:31 Merlin_ joined #gluster
03:54 dlambrig_ joined #gluster
04:01 haomaiwa_ joined #gluster
04:13 DV joined #gluster
04:17 Merlin_ joined #gluster
04:20 ovaistariq joined #gluster
04:30 ference joined #gluster
04:36 Merlin_ joined #gluster
04:44 Merlin__ joined #gluster
04:45 ference hi there, I'm running an old setup, gluster 3.4 on two outdated nodes that are running out of space. Type: Replicate, Number of Bricks: 1 x 2 = 2. I set up two new nodes with more storage and gluster 3.6 and added these as peers to the trusted pool. Next I wanted to replace the old nodes with the new nodes, and for the first node ran: `gluster volume replace-brick <volume> oldnode1:/data/glusterfs/brick newnode1:/data/glusterfs/brick commit forc
04:55 armyriad joined #gluster
05:01 haomaiwa_ joined #gluster
05:07 Merlin_ joined #gluster
05:13 baojg joined #gluster
05:20 ovaistariq joined #gluster
05:26 gem joined #gluster
05:29 Merlin_ joined #gluster
05:40 Merlin_ joined #gluster
05:45 Lee1092 joined #gluster
05:51 hchiramm joined #gluster
05:59 Merlin_ joined #gluster
06:01 haomaiwa_ joined #gluster
06:11 Merlin_ joined #gluster
06:15 aravindavk joined #gluster
06:23 beeradb_ joined #gluster
06:23 coredump|br joined #gluster
06:27 armyriad joined #gluster
06:34 Merlin_ joined #gluster
06:41 baojg_ joined #gluster
06:52 baojg joined #gluster
06:59 RameshN_ joined #gluster
07:01 haomaiwa_ joined #gluster
07:19 sonicrose joined #gluster
07:21 ovaistariq joined #gluster
07:24 sonicrose morning all… can anyone tell me if there is a way to make gluster FS ignore a client’s O_DIRECT flag and make it force the use of VFS cache?   I’m trying to do Gluster and XenServer.  XenServer opens files over NFS and uses O_DIRECT.   its fine on my server that has a hard-raid card with DDR cache onboard, but i’m on a different server now without the DDR cache, and performance is horrible basically theres no cache!  Ideally I
07:24 sonicrose wouldn’t change XenServer, let it open with o_direct because we dont want the data going into it’s VFS cache… we want the data in the VFS cache of the gluster servers… hoping i can just do something to disable O_DIRECT on the gluster side?
07:24 Merlin_ joined #gluster
07:25 rafi joined #gluster
07:40 Merlin_ joined #gluster
07:50 Merlin_ joined #gluster
08:01 haomaiwa_ joined #gluster
08:03 Merlin_ joined #gluster
08:03 armyriad joined #gluster
08:06 mhulsman joined #gluster
08:06 dlambrig_ joined #gluster
08:13 pur joined #gluster
08:20 Merlin_ joined #gluster
08:23 Merlin_ joined #gluster
08:27 Merlin_ joined #gluster
08:33 baojg joined #gluster
08:35 mhulsman1 joined #gluster
08:36 sonicrose joined #gluster
08:39 DV joined #gluster
08:41 steveeJ joined #gluster
08:50 Merlin__ joined #gluster
08:58 Merlin_ joined #gluster
09:01 haomaiwa_ joined #gluster
09:02 ahino joined #gluster
09:13 karnan joined #gluster
09:22 ovaistariq joined #gluster
09:38 Wizek joined #gluster
09:39 Wizek_ joined #gluster
09:45 ference joined #gluster
09:48 semiautomatic joined #gluster
09:53 semiautomatic1 joined #gluster
10:01 haomaiwa_ joined #gluster
10:06 semiautomatic joined #gluster
10:08 Wizek_ joined #gluster
10:09 semiautomatic1 joined #gluster
10:10 RameshN joined #gluster
10:12 mhulsman joined #gluster
10:23 ovaistariq joined #gluster
10:39 semiautomatic joined #gluster
10:42 hackman joined #gluster
11:01 ference joined #gluster
11:01 haomaiwa_ joined #gluster
11:04 skoduri joined #gluster
11:09 hackman joined #gluster
11:31 pur joined #gluster
12:01 77CAAFUAR joined #gluster
12:07 Gnomethrower joined #gluster
12:13 rafi joined #gluster
12:16 karnan joined #gluster
12:17 gem joined #gluster
12:21 mhulsman joined #gluster
12:23 ovaistariq joined #gluster
12:25 mhulsman1 joined #gluster
13:01 haomaiwa_ joined #gluster
13:10 ahino joined #gluster
13:11 mhulsman joined #gluster
13:13 gem joined #gluster
13:48 Gnomethrower joined #gluster
13:53 RameshN joined #gluster
13:57 mhulsman joined #gluster
14:00 karnan joined #gluster
14:00 csterling joined #gluster
14:01 haomaiwa_ joined #gluster
14:24 ovaistariq joined #gluster
14:28 sonicrose joined #gluster
14:28 sonicrose morning all… can anyone tell me if there is a way to make gluster FS ignore a client’s O_DIRECT flag and make it force the use of VFS cache?  I’m trying to do Gluster and XenServer.  XenServer opens files over NFS and uses O_DIRECT.  its fine on my server that has a hard-raid card with DDR cache onboard, but i’m on a different server now without the DDR cache, and performance is horrible basically theres no cache!  Ideally I
14:28 sonicrose wouldn’t change XenServer, let it open with o_direct because we dont want the data going into it’s VFS cache… we want the data in the VFS cache of the gluster servers… hoping i can just do something to disable O_DIRECT on the gluster side?
14:29 ahino joined #gluster
14:31 karnan joined #gluster
14:33 jiffin joined #gluster
14:46 dlambrig_ joined #gluster
15:01 haomaiwa_ joined #gluster
15:13 sonicrose joined #gluster
15:14 RameshN joined #gluster
15:15 baojg joined #gluster
15:18 sonicrose joined #gluster
15:24 robb_nl joined #gluster
15:30 EinstCrazy joined #gluster
15:30 sonicrose joined #gluster
15:41 baoboa joined #gluster
15:56 Merlin_ joined #gluster
16:01 haomaiwa_ joined #gluster
16:04 EinstCrazy joined #gluster
16:12 johnmilton joined #gluster
16:22 jwd joined #gluster
16:40 plarsen joined #gluster
16:40 Merlin_ joined #gluster
16:44 Merlin_ joined #gluster
16:51 d0nn1e joined #gluster
17:00 Merlin_ joined #gluster
17:01 haomaiwa_ joined #gluster
17:04 sonicrose joined #gluster
17:07 shaunm joined #gluster
17:24 Merlin_ joined #gluster
17:27 johnmilton joined #gluster
17:27 Merlin_ joined #gluster
17:34 pur joined #gluster
17:37 Merlin_ joined #gluster
17:41 ovaistariq joined #gluster
17:45 EinstCrazy joined #gluster
17:52 arcolife joined #gluster
18:03 Merlin_ joined #gluster
18:06 plarsen joined #gluster
18:10 ference joined #gluster
18:12 rafi joined #gluster
18:14 Merlin_ joined #gluster
18:22 ahino joined #gluster
18:40 Merlin_ joined #gluster
18:41 ovaistariq joined #gluster
18:57 7GHAAIRKN joined #gluster
19:03 Merlin_ joined #gluster
19:14 plarsen joined #gluster
19:27 jwaibel joined #gluster
19:32 jwd joined #gluster
19:47 robb_nl joined #gluster
20:11 DV joined #gluster
20:14 TvL2386 joined #gluster
20:34 ovaistariq joined #gluster
20:56 haomaiwa_ joined #gluster
21:05 Merlin_ joined #gluster
21:07 hackman joined #gluster
21:57 haomaiwa_ joined #gluster
22:18 hackman joined #gluster
22:38 sonicrose joined #gluster
23:02 ovaistariq joined #gluster
23:37 sonicrose joined #gluster
23:42 sonicrose does anyone know if it’s possible to ignore O_DIRECT on XFS?
23:50 haomaiwang joined #gluster
23:53 ference ok, this place is not exactly chatty... Maybe you could point me to some good documentation on troubleshooting brick replacement / addition / removal operations? The official docs only cover the surface afaik. It would be much appreciated.

| Channels | #gluster index | Today | | Search | Google Search | Plain-Text | summary