similar to: issues after botched update

Hi all, I still experience vm crashes with glusterfs. The VM I had problems (kept on crashing) was moved away from gluster and have had no problems since. Now another VM is doing the same. It just shutsdown. gluster is 3.8.13 I know now you are on 3.10 and 3.12, but I had troubles upgrading another cluster to 3.10 (although the processes were off and no files where in use gluster had to heal

Hi @all, I've created a Distributed-Replicated Volume consisting of 4 bricks on 2 servers. # gluster volume create glusterfs replica 2 transport tcp \ gluster0{0..1}:/srv/gluster/exp0 gluster0{0..1}:/srv/gluster/exp1 Now I have the following very nice replication schema: +-------------+ +-------------+ | gluster00 | | gluster01 | +-------------+ +-------------+ | exp0 | exp1 |

Hi, A client had some issues with their glusterfs cluster and botched an update. Currently they have loads of broken symlinks in their bricks .glusterfs folder Like the second one below lrwxrwxrwx 1 root root 55 Jul 14 2017 591c33db-e88b-4544-9372-bea4ec362360 -> ../../83/4a/834a8af8-95a4-4f8a-9810-4e4d829e87f9/394947 lrwxrwxrwx 1 root root 74 Jul 17 2017

Hi, A client had some issues with their glusterfs cluster and botched an update. Currently they have loads of broken symlinks in their bricks .glusterfs subfolders Like the second symlink one below lrwxrwxrwx 1 root root 55 Jul 14 2017 591c33db-e88b-4544-9372-bea4ec362360 -> ../../83/4a/834a8af8-95a4-4f8a-9810-4e4d829e87f9/394947 lrwxrwxrwx 1 root root 74 Jul 17 2017

https://bugzilla.mindrot.org/show_bug.cgi?id=1414 Summary: Botched getpwuid usage on Mac OS X Classification: Unclassified Product: Portable OpenSSH Version: 4.7p1 Platform: Other OS/Version: Mac OS X Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: bitbucket at mindrot.org

Sorry, I botched a commit and broke the build. I've just committed a fix. So expect to see some buildbot churning. -Dave

David Greene <dag at cray.com> writes: > Sorry, I botched a commit and broke the build. I've just committed a fix. > > So expect to see some buildbot churning. Don't hurry. A buildbot already decided that I am the only culprit of the breakage. :-/ And some people pretend to use computer technology to pinpoint terrorists...

On Monday 15 February 2010 11:54:25 Óscar Fuentes wrote: > David Greene <dag at cray.com> writes: > > Sorry, I botched a commit and broke the build. I've just committed a > > fix. > > > > So expect to see some buildbot churning. > > Don't hurry. A buildbot already decided that I am the only culprit of > the breakage. :-/ Hmm...given that

On Feb 15, 2010, at 10:00 AM, David Greene wrote: > On Monday 15 February 2010 11:54:25 Óscar Fuentes wrote: >> David Greene <dag at cray.com> writes: >>> Sorry, I botched a commit and broke the build. I've just committed a >>> fix. >>> >>> So expect to see some buildbot churning. >> >> Don't hurry. A buildbot already

On Monday 15 February 2010 14:59:19 Chris Lattner wrote: > On Feb 15, 2010, at 12:53 PM, Chris Lattner wrote: > > On Feb 15, 2010, at 10:00 AM, David Greene wrote: > >> On Monday 15 February 2010 11:54:25 Óscar Fuentes wrote: > >>> David Greene <dag at cray.com> writes: > >>>> Sorry, I botched a commit and broke the build. I've just committed

Unless others find this objectionable, it would be nice to see the grammar for metadata instruction attachment in the http://llvm.org/docs/LangRef.html#metadata section. The grammar you gave earlier seems to work. Garrison On Feb 15, 2010, at 16:17, David Greene wrote: > On Monday 15 February 2010 15:08:22 Chris Lattner wrote: >> On Feb 15, 2010, at 1:04 PM, David Greene wrote:

I think I botched syslinux-6.04-pre3. There are two fundamental problems with the build: a) The selection of what pieces of the library gets included in the core is done manually whereas it really should be automatic; b) The build doesn't fail if there are unresolved dependencies between the libraries and the core. I will fix these. (b) is IMO fundamental to avoid this error in the

On Mon, 2019-02-11 at 12:15 -0800, H. Peter Anvin via Syslinux wrote: > > > I think I botched syslinux-6.04-pre3. There are two fundamental > problems with the build: > > a) The selection of what pieces of the library gets included in the core > is done manually whereas it really should be automatic; > > b) The build doesn't fail if there are unresolved

On February 11, 2019 12:29:41 PM PST, Joakim Tjernlund <Joakim.Tjernlund at infinera.com> wrote: >On Mon, 2019-02-11 at 12:15 -0800, H. Peter Anvin via Syslinux wrote: >> >> >> I think I botched syslinux-6.04-pre3. There are two fundamental >> problems with the build: >> >> a) The selection of what pieces of the library gets included in the >core

I have a 6.5 box that failed to boot after a kernel update. The reason is the first arg on the kernel line: title CentOS (2.6.32-431.11.2.el6.x86_64) root (hd0,0) kernel /tboot.gz ro root=/dev/mapper/vol0-lvol1 intel_iommu=on rd_NO_LUKS LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_NO_DM KEYBOARDTYPE=pc KEYTABLE=us rd_LVM_LV=vol0/lv ol3

On Feb 15, 2010, at 12:53 PM, Chris Lattner wrote: > > On Feb 15, 2010, at 10:00 AM, David Greene wrote: > >> On Monday 15 February 2010 11:54:25 Óscar Fuentes wrote: >>> David Greene <dag at cray.com> writes: >>>> Sorry, I botched a commit and broke the build. I've just committed a >>>> fix. >>>> >>>> So expect

On Monday 15 February 2010 15:08:22 Chris Lattner wrote: > On Feb 15, 2010, at 1:04 PM, David Greene wrote: > >> FWIW, this is because you broke the encoding of an instruction in your > >> patch. This is incorrect: > >> > >> +def MOVNTDQ_64mr : PSI<0xE7, MRMDestMem, (outs), (ins f128mem:$dst, > >> VR128:$src), +

On Monday 15 February 2010 15:27:34 Chris Lattner wrote: > On Feb 15, 2010, at 1:17 PM, David Greene wrote: > > On Monday 15 February 2010 15:08:22 Chris Lattner wrote: > >> On Feb 15, 2010, at 1:04 PM, David Greene wrote: > >>>> FWIW, this is because you broke the encoding of an instruction in your > >>>> patch. This is incorrect: >

Hi; The following message appears to have been sent, but in fact never does reach their destination: [root qmail-send]# tail current @400000004b87b3d3392cbddc new msg 97881462 @400000004b87b3d3392cc5ac info msg 97881462: bytes 531 from < suzieprogrammer at gmail.com> qp 23629 uid 508 @400000004b87b3d33b7f700c starting delivery 4: msg 97881462 to remote suzieprogrammer at gmail.com

On Feb 15, 2010, at 1:04 PM, David Greene wrote: >> FWIW, this is because you broke the encoding of an instruction in your >> patch. This is incorrect: >> >> +def MOVNTDQ_64mr : PSI<0xE7, MRMDestMem, (outs), (ins f128mem:$dst, >> VR128:$src), + "movntdq\t{$src, $dst|$dst, $src}", >> + [(alignednontemporalstore