search for: nov29

...Type: Distribute Volume ID: eccc3a90-212d-4563-ae8d-10a77758738d Status: Started Number of Bricks: 3 Transport-type: tcp Bricks: Brick1: gluster-0-0:/mseas-data-0-0 Brick2: gluster-0-1:/mseas-data-0-1 Brick3: gluster-data:/data [root at mseas-data ~]# ps -ef | grep gluster root 2783 1 0 Nov29 ? 00:01:15 /usr/sbin/glusterd -p /var/run/glusterd.pid root 2899 1 0 Nov29 ? 00:00:00 /usr/sbin/glusterfsd -s localhost --volfile-id gdata.gluster-data.data -p /var/lib/glusterd/vols/gdata/run/gluster-data-data.pid -S /tmp/e3eac7ce95e786a3d909b8fc65ed2059.socket --brick-name...

...Type: Distribute Volume ID: eccc3a90-212d-4563-ae8d-10a77758738d Status: Started Number of Bricks: 3 Transport-type: tcp Bricks: Brick1: gluster-0-0:/mseas-data-0-0 Brick2: gluster-0-1:/mseas-data-0-1 Brick3: gluster-data:/data [root at mseas-data ~]# ps -ef | grep gluster root 2783 1 0 Nov29 ? 00:01:15 /usr/sbin/glusterd -p /var/= run/glusterd.pid root 2899 1 0 Nov29 ? 00:00:00 /usr/sbin/glusterfsd -s loc= alhost --volfile-id gdata.gluster-data.data -p /var/lib/glusterd/vols/gdata= /run/gluster-data-data.pid -S /tmp/e3eac7ce95e786a3d909b8fc65ed2059.socket = --br...

Hi all, I''m currently getting a lot of update failures showing up with no logs in the dashboard. This happens for about half of our 28 nodes, about once an hour. When re-run half an hour later, everything seems fine. Through a combination of server restarts and our Puppet master locking up entirely yesterday, almost all of our nodes are now trying to do their half hourly update at

...ent ahead and made all of these changes, and I reviewed the doxygen section of the Coding Standards document and updated the comments as well. I also fixed the issue mentioned by Ben with braces on their own line. I've posted an updated patch here: http://people.freedesktop.org/~tstellar/llvm/Nov29/ Also in that directory are two patches which show the changes since the previous version of R600.patch. Hopefully this patch looks a little better. Thanks, Tom

...these changes, and I reviewed the doxygen section > of the Coding Standards document and updated the comments as well. > I also fixed the issue mentioned by Ben with braces on their own line. > > I've posted an updated patch here: > http://people.freedesktop.org/~tstellar/llvm/Nov29/ > > Also in that directory are two patches which show the changes since the > previous version of R600.patch. > > Hopefully this patch looks a little better. I'm obviously not an expert on this architecture, but the patch looks basically ok to me. Please commit! -Chris

...I reviewed the doxygen section >> of the Coding Standards document and updated the comments as well. >> I also fixed the issue mentioned by Ben with braces on their own line. >> >> I've posted an updated patch here: >> http://people.freedesktop.org/~tstellar/llvm/Nov29/ >> >> Also in that directory are two patches which show the changes since the >> previous version of R600.patch. >> >> Hopefully this patch looks a little better. > > I'm obviously not an expert on this architecture, but the patch looks basically ok to me...

...iewed the doxygen section > > of the Coding Standards document and updated the comments as well. > > I also fixed the issue mentioned by Ben with braces on their own line. > > > > I've posted an updated patch here: > > http://people.freedesktop.org/~tstellar/llvm/Nov29/ > > > > Also in that directory are two patches which show the changes since the > > previous version of R600.patch. > > > > Hopefully this patch looks a little better. > > I'm obviously not an expert on this architecture, but the patch looks basically ok...

On Tue, Nov 27, 2012 at 12:37 AM, Tom Stellard <tom at stellard.net> wrote: > Assuming I caught all the coding style mistakes you pointed out, what > else needs to be done to be able to commit this code? Hello Tom, There are still a few classes of coding style issues... + /// CreateLiveInRegister - Helper function that adds Reg to the LiveIn list + /// of the DAG's

Greetings, Last night I manually unpresented and deleted a LUN (a SAN snapshot) that was presented to one node in a four node RAC environment running OCFS2 v1.4.1-1. The system then rebooted with the following error: Oct 21 16:45:34 ausracdb03 kernel: (27,1):o2hb_write_timeout:166 ERROR: Heartbeat write timeout to device dm-24 after 120000 milliseconds Oct 21 16:45:34 ausracdb03 kernel:

On Sat, Nov 17, 2012 at 10:56:26PM +0100, Benjamin Kramer wrote: > > On 01.11.2012, at 14:44, Tom Stellard <tom at stellard.net> wrote: > > > Moving this thread to llvmdev. > > > > On Tue, Oct 30, 2012 at 11:09:34PM -0700, Chris Lattner wrote: > >> On Oct 30, 2012, at 11:35 AM, Tom Stellard <tom at stellard.net> wrote: > >>>> Hi