Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster-dev, 2014-07-03

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

All times shown according to UTC.

Time Nick Message
00:27 shyam joined #gluster-dev
01:25 purpleidea can someone confirm what the C in RHS-C means?
02:21 hagarth purpleidea: console
02:24 [o__o] joined #gluster-dev
02:25 vpshastry joined #gluster-dev
03:20 kshlm joined #gluster-dev
03:34 purpleidea hagarth: thanks!
03:43 itisravi joined #gluster-dev
03:50 shubhendu joined #gluster-dev
04:12 ndarshan joined #gluster-dev
04:19 kanagaraj joined #gluster-dev
04:26 skoduri joined #gluster-dev
04:29 skoduri joined #gluster-dev
04:42 ppai joined #gluster-dev
04:45 hagarth joined #gluster-dev
04:46 kdhananjay joined #gluster-dev
04:56 spandit joined #gluster-dev
05:02 vimal joined #gluster-dev
05:09 lalatenduM joined #gluster-dev
05:09 vpshastry joined #gluster-dev
05:15 nishanth joined #gluster-dev
05:35 skoduri joined #gluster-dev
05:47 hagarth joined #gluster-dev
05:47 lalatenduM ndevos, regarding http://review.gluster.org/#/c/8213/3, man 2 write has following text
05:47 glusterbot Title: Gerrit Code Review (at review.gluster.org)
05:47 lalatenduM POSIX requires that a read(2) which can be proved to occur after a write() has returned returns the new data
05:48 lalatenduM ndevos, does it mean we dont have to do a lseek for read after write
05:56 JustinClift ndevos: On the + side :/ I have a better understanding of how the status return codes for Jenkins work now.
05:56 * JustinClift was swearing a lot last night
06:16 raghu joined #gluster-dev
06:48 nishanth joined #gluster-dev
07:29 vpshastry joined #gluster-dev
07:29 [o__o] joined #gluster-dev
08:34 aravindavk joined #gluster-dev
08:38 nishanth joined #gluster-dev
08:39 ppai joined #gluster-dev
08:50 shubhendu joined #gluster-dev
08:54 ndarshan joined #gluster-dev
08:58 xavih lalatenduM: what POSIX tries to say there (at least this is how I understand it) is that whatever operation done on a file after a write has completed should never return information as if the write hadn't completed yet
08:59 xavih lalatenduM: this means that if check file size, modification time... you will always receive the information with write results incorporated
08:59 xavih lalatenduM: this also means that if you read the *same* portion of the file, it will contain the written data
09:00 xavih lalatenduM: however you have to move the file pointer back since you are using the same fd and the write operation would have incremented the pointer
09:00 lalatenduM xavih, yeah, wrote a small prog to verify that and you are right about it
09:01 lalatenduM xavih, , thanks
09:01 lalatenduM @xavih++
09:01 glusterbot lalatenduM: xavih's karma is now 1
09:01 xavih lalatenduM: yw :)
09:01 lalatenduM :)
09:21 aravindavk joined #gluster-dev
09:29 deepakcs joined #gluster-dev
09:32 ndarshan joined #gluster-dev
09:39 bala1 joined #gluster-dev
09:41 [o__o] joined #gluster-dev
09:50 hagarth joined #gluster-dev
10:14 kkeithley1 joined #gluster-dev
10:25 shyam1 joined #gluster-dev
10:33 ndarshan joined #gluster-dev
10:39 ndevos JustinClift, hchiramm__: http://build.gluster.org/job/rackspace​-regression-2GB-triggered/105/console seems to be hanging for 10+ hours, what can be done about it?
10:39 glusterbot Title: rackspace-regression-2GB-triggered #105 Console [Jenkins] (at build.gluster.org)
10:40 hagarth ndevos: killed it
10:41 ndevos hagarth: ok
10:43 foster joined #gluster-dev
10:45 hagarth ndevos: please feel free to kill such erroneous jobs and send a note to pranith/Justin
10:45 ndevos hagarth: kill through Jenkins, or an other way? And, would I need to capture some details for debugging?
10:46 hagarth ndevos: kill through Jenkins .. I try to remember the name of the test that was hung (that is usually sufficient for further analysis)
10:55 skoduri joined #gluster-dev
11:00 ndevos hagarth: ok, thanks
11:01 shubhendu joined #gluster-dev
11:35 skoduri joined #gluster-dev
11:49 lalatenduM joined #gluster-dev
11:49 vpshastry joined #gluster-dev
12:05 kshlm joined #gluster-dev
12:14 kanagaraj joined #gluster-dev
12:21 hagarth joined #gluster-dev
12:35 edward1 joined #gluster-dev
12:44 hchiramm__ joined #gluster-dev
13:02 shyam joined #gluster-dev
13:45 hchiramm__ joined #gluster-dev
14:13 JustinClift ndevos hagarth: Yeah, noticed that hanging job a few hours ago, but left it running in case kkeithley_ wanted to log in and see what was going on (eg strace, etc).
14:13 JustinClift Emailed kkeithley_ about it.
14:14 JustinClift Since it's killed, the node should probably be rebooted, just to be sure it's complete ok now.
14:14 wushudoin joined #gluster-dev
14:16 kkeithley_ mail?
14:16 JustinClift kkeithley_: Not in your inbox?
14:16 JustinClift Hmm
14:16 * JustinClift double checks
14:17 kkeithley_ don't see anything
14:17 kkeithley_ last email from you was "Homebfew on the Westford lab mac min"
14:17 JustinClift That's weird.  It's not in my Sent box either.
14:18 JustinClift Guess I didn't hit send, or got distracted or something
14:18 JustinClift Damn.
14:18 * JustinClift is not on the all recently :(
14:18 JustinClift s/all/ball/  <-- example right there
14:19 kkeithley_ pft. If I went by that criteria then I should be dead and buried
14:19 JustinClift Heh
14:19 JustinClift Well, I've just yum updated and rebooted the node
14:19 JustinClift It's back online now
14:22 bala1 joined #gluster-dev
14:59 deepakcs joined #gluster-dev
15:08 jobewan joined #gluster-dev
15:11 _Bryan_ joined #gluster-dev
15:42 bala joined #gluster-dev
15:57 vpshastry joined #gluster-dev
16:15 lpabon_test joined #gluster-dev
16:25 vpshastry joined #gluster-dev
17:22 vpshastry joined #gluster-dev
18:00 vpshastry joined #gluster-dev
19:30 MacWinner joined #gluster-dev
20:11 MacWinner joined #gluster-dev
20:24 wushudoin joined #gluster-dev
21:06 wushudoin joined #gluster-dev
22:28 shyam joined #gluster-dev
23:15 MacWinner joined #gluster-dev
23:15 purpleidea joined #gluster-dev
23:22 wushudoin joined #gluster-dev

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