search for: disk3

On Sat, Aug 17, 2013 at 7:08 AM, Tom Browder <tom.browder at gmail.com> wrote: > On Sat, Aug 17, 2013 at 6:15 AM, Tom Browder <tom.browder at gmail.com>wrote: > >> On Fri, Aug 16, 2013 at 2:58 PM, Tom Browder <tom.browder at gmail.com>wrote: >> >>> On Fri, Aug 16, 2013 at 2:55 PM, Tom Browder <tom.browder at gmail.com>wrote: >>>

...Release" -DLLVM_TARGETS_TO_BUILD="X86" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_CXX_COMPILER="/usr/bin/g++" -DCMAKE_C_COMPILER="/usr/bin/gcc" cmake failure output: … … -- Performing Test HAS_MAYBE_UNINITIALIZED -- Performing Test HAS_MAYBE_UNINITIALIZED - Success /mnt/disk3/llvmtruck/llvm/autoconf/config.guess: 6: /mnt/disk3/llvmtruck/llvm/au: not foundig.guess: /mnt/disk3/llvmtruck/llvm/autoconf/config.guess: 8: /mnt/disk3/llvmtruck/llvm/au: not foundig.guess: /mnt/disk3/llvmtruck/llvm/autoconf/config.guess: 28: /mnt/disk3/llvmtruck/llvm/a: not foundfig.guess: /mnt/d...

...eneral framework for plotting these measures, in the hopes that it's of some use to people other than me. One obstacle I encounter is that, when I select one column out of a data.frame, the result is no longer a data.frame. So, say I've got, in data frame 'input' disk1 disk2 disk3 disk4 T0000 0 1 0 4 T0001 0 1 0 5 T0002 0 1 0 5 T0003 0 2 0 4 T0004 0 2 0 3 T0005 0 1 0 3 T0006 0 0 0 3 and somewhere I've noted a list targets <- c('disk2','disk3...

...ms_va_start, __builtin_ms_va_arg, __builtin_ms_va_end, my code will build fail in Ubuntu with below message. Do you suggest I should build it in windows and not in Linux? Or did I miss any build option here? Appreciate if you could let me know the correct build steps. jshi19 at jshi19-Intel:/mnt/disk3$ clang X64.c X64.c:12:2: error: unknown type name '__builtin_ms_va_list'; did you mean '__builtin_va_list'? __builtin_ms_va_list Marker; ^~~~~~~~~~~~~~~~~~~~ __builtin_va_list note: '__builtin_va_list' declared here X64.c:15:2: error: use of u...

...Brick1: pdchyperscale1sds:/ws/disk1/ws_brick Brick2: pdchyperscale2sds:/ws/disk1/ws_brick Brick3: pdchyperscale3sds:/ws/disk1/ws_brick Brick4: pdchyperscale1sds:/ws/disk2/ws_brick Brick5: pdchyperscale2sds:/ws/disk2/ws_brick Brick6: pdchyperscale3sds:/ws/disk2/ws_brick Brick7: pdchyperscale1sds:/ws/disk3/ws_brick Brick8: pdchyperscale2sds:/ws/disk3/ws_brick Brick9: pdchyperscale3sds:/ws/disk3/ws_brick Brick10: pdchyperscale1sds:/ws/disk4/ws_brick Brick11: pdchyperscale2sds:/ws/disk4/ws_brick Brick12: pdchyperscale3sds:/ws/disk4/ws_brick Please suggest how to know which bricks are part of first and...

Hi, I wonder if there will be a 3rd and 4th disk (additional Packages) to 4.8-Release ... or won't there like in 5.0-Release. Thanks! Zheyu -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Bitte l?cheln! Fotogalerie online mit GMX ohne eigene Homepage!

...create test <disk0> mirror <disk1> <disk2> invalid vdev specification use ''-f'' to override the following errors: mismatched replication level: both disk and mirror vdevs are present # zpool create test <disk0> log <disk1> mirror <disk2> <disk3> # echo $? 0 # zpool create test mirror <disk0> <disk1> mirror <disk2> <disk3> <disk4> invalid vdev specification use ''-f'' to override the following errors: mismatched replication level: both 2-way and 3-way mirror vdevs are present # zpoo...

...2: pdchyperscale2sds:/ws/disk1/ws_brick > > Brick3: pdchyperscale3sds:/ws/disk1/ws_brick > > Brick4: pdchyperscale1sds:/ws/disk2/ws_brick > > Brick5: pdchyperscale2sds:/ws/disk2/ws_brick > > Brick6: pdchyperscale3sds:/ws/disk2/ws_brick > > Brick7: pdchyperscale1sds:/ws/disk3/ws_brick > > Brick8: pdchyperscale2sds:/ws/disk3/ws_brick > > Brick9: pdchyperscale3sds:/ws/disk3/ws_brick > > Brick10: pdchyperscale1sds:/ws/disk4/ws_brick > > Brick11: pdchyperscale2sds:/ws/disk4/ws_brick > > Brick12: pdchyperscale3sds:/ws/disk4/ws_brick > > Pl...

...Brick1: pdchyperscale1sds:/ws/disk1/ws_brick Brick2: pdchyperscale2sds:/ws/disk1/ws_brick Brick3: pdchyperscale3sds:/ws/disk1/ws_brick Brick4: pdchyperscale1sds:/ws/disk2/ws_brick Brick5: pdchyperscale2sds:/ws/disk2/ws_brick Brick6: pdchyperscale3sds:/ws/disk2/ws_brick Brick7: pdchyperscale1sds:/ws/disk3/ws_brick Brick8: pdchyperscale2sds:/ws/disk3/ws_brick Brick9: pdchyperscale3sds:/ws/disk3/ws_brick Brick10: pdchyperscale1sds:/ws/disk4/ws_brick Brick11: pdchyperscale2sds:/ws/disk4/ws_brick Brick12: pdchyperscale3sds:/ws/disk4/ws_brick Please suggest how to know which bricks are part of first and...

...Transport-type: tcp Bricks: Brick1: glusterfs1sds:/ws/disk1/ws_brick Brick2: glusterfs2sds:/ws/disk1/ws_brick Brick3: glusterfs3sds:/ws/disk1/ws_brick Brick4: glusterfs1sds:/ws/disk2/ws_brick Brick5: glusterfs2sds:/ws/disk2/ws_brick Brick6: glusterfs3sds:/ws/disk2/ws_brick Brick7: glusterfs1sds:/ws/disk3/ws_brick Brick8: glusterfs2sds:/ws/disk3/ws_brick Brick9: glusterfs3sds:/ws/disk3/ws_brick Brick10: glusterfs1sds:/ws/disk4/ws_brick Brick11: glusterfs2sds:/ws/disk4/ws_brick Brick12: glusterfs3sds:/ws/disk4/ws_brick Brick13: glusterfs1sds:/ws/disk5/ws_brick Brick14: glusterfs2sds:/ws/disk5/ws_bric...

...te prop-del - delete a user property from the disk state prop-get - read a property from the disk state prop-set - set a property in the disk state : alpha[1]#; vdiskadm create -t vmdk:sparse -s 8g /tank/guests/nevada/disk2 : alpha[1]#; vdiskadm create -t vdi:sparse -s 8g /tank/guests/nevada/disk3 : alpha[1]#; vdiskadm snapshot /tank/guests/nevada/disk3@initial : alpha[1]#; vdiskadm snapshot /tank/guests/nevada/disk3@2 : alpha[1]#; vdiskadm rollback -r /tank/guests/nevada/disk3@initial Snapshot a guest --- : alpha[1]#; virsh console nevada Loading kmdb... v3.1.4-xvm chgset ''Mon O...

...ws_brick > > Brick2: glusterfs2sds:/ws/disk1/ws_brick > > Brick3: glusterfs3sds:/ws/disk1/ws_brick > > Brick4: glusterfs1sds:/ws/disk2/ws_brick > > Brick5: glusterfs2sds:/ws/disk2/ws_brick > > Brick6: glusterfs3sds:/ws/disk2/ws_brick > > Brick7: glusterfs1sds:/ws/disk3/ws_brick > > Brick8: glusterfs2sds:/ws/disk3/ws_brick > > Brick9: glusterfs3sds:/ws/disk3/ws_brick > > Brick10: glusterfs1sds:/ws/disk4/ws_brick > > Brick11: glusterfs2sds:/ws/disk4/ws_brick > > Brick12: glusterfs3sds:/ws/disk4/ws_brick > > Brick13: glusterfs1sds...

...:/ws/disk1/ws_brick > > Brick3: pdchyperscale3sds:/ws/disk1/ws_brick > > Brick4: pdchyperscale1sds:/ws/disk2/ws_brick > > Brick5: pdchyperscale2sds:/ws/disk2/ws_brick > > Brick6: pdchyperscale3sds:/ws/disk2/ws_brick > > Brick7: pdchyperscale1sds:/ws/disk3/ws_brick > > Brick8: pdchyperscale2sds:/ws/disk3/ws_brick > > Brick9: pdchyperscale3sds:/ws/disk3/ws_brick > > Brick10: pdchyperscale1sds:/ws/disk4/ws_brick > > Brick11: pdchyperscale2sds:/ws/disk4/ws_brick > > Brick12: pdchyperscale3sds:/ws/disk4/w...

...- data block P<x> - parity block N<x> - new parity block U - unused * - if offset in I/O request is less that this marker we use four disks only, if greater - we use five disks After adding ''NewDisk'' to RAIDZ vdev, we have something like this: Disk0 Disk1 Disk2 Disk3 NewDisk <<P00 D00 D01 D02 U P01 D03 D04 D05 U P02 D06>> <<P03 D07>> U <<P04 D08>> <<P05 D09 U P06 D10 D11 D12>> U <<P07 D13 D14 D15>> U Then we start moving data, but we need to beg...

On Fri, Jul 7, 2017 at 9:25 PM, Ankireddypalle Reddy <areddy at commvault.com> wrote: > 3.7.19 > These are the only callers for removexattr and only _posix_remove_xattr has the potential to do removexattr as posix_removexattr already makes sure that it is not gfid/volume-id. And surprise surprise _posix_remove_xattr happens only from healing code of afr/ec. And this can only happen

...:/ws/disk1/ws_brick >> >> Brick3: glusterfs3sds:/ws/disk1/ws_brick >> >> Brick4: glusterfs1sds:/ws/disk2/ws_brick >> >> Brick5: glusterfs2sds:/ws/disk2/ws_brick >> >> Brick6: glusterfs3sds:/ws/disk2/ws_brick >> >> Brick7: glusterfs1sds:/ws/disk3/ws_brick >> >> Brick8: glusterfs2sds:/ws/disk3/ws_brick >> >> Brick9: glusterfs3sds:/ws/disk3/ws_brick >> >> Brick10: glusterfs1sds:/ws/disk4/ws_brick >> >> Brick11: glusterfs2sds:/ws/disk4/ws_brick >> >> Brick12: glusterfs3sds:/ws/disk4/w...

...;> Brick3: glusterfs3sds:/ws/disk1/ws_brick >>> >>> Brick4: glusterfs1sds:/ws/disk2/ws_brick >>> >>> Brick5: glusterfs2sds:/ws/disk2/ws_brick >>> >>> Brick6: glusterfs3sds:/ws/disk2/ws_brick >>> >>> Brick7: glusterfs1sds:/ws/disk3/ws_brick >>> >>> Brick8: glusterfs2sds:/ws/disk3/ws_brick >>> >>> Brick9: glusterfs3sds:/ws/disk3/ws_brick >>> >>> Brick10: glusterfs1sds:/ws/disk4/ws_brick >>> >>> Brick11: glusterfs2sds:/ws/disk4/ws_brick >>> >&gt...

We have a Mirror setup in ZFS that''s 73GB (two internal disks on a sun fire v440). We currently are going to attach this system to an Equallogic Box, and will attach an ISCSCI LUN from the Equallogic box to the v440 of about 200gb. The Equallogic Box is configured as a Hardware Raid 50 (two hot spares for redundancy). My question is what''s the best approach to moving the ZFS

...disk1/ws_brick >>>> >>>> Brick4: glusterfs1sds:/ws/disk2/ws_brick >>>> >>>> Brick5: glusterfs2sds:/ws/disk2/ws_brick >>>> >>>> Brick6: glusterfs3sds:/ws/disk2/ws_brick >>>> >>>> Brick7: glusterfs1sds:/ws/disk3/ws_brick >>>> >>>> Brick8: glusterfs2sds:/ws/disk3/ws_brick >>>> >>>> Brick9: glusterfs3sds:/ws/disk3/ws_brick >>>> >>>> Brick10: glusterfs1sds:/ws/disk4/ws_brick >>>> >>>> Brick11: glusterfs2sds:/ws/dis...

...Transport-type: tcp Bricks: Brick1: glusterfs1sds:/ws/disk1/ws_brick Brick2: glusterfs2sds:/ws/disk1/ws_brick Brick3: glusterfs3sds:/ws/disk1/ws_brick Brick4: glusterfs1sds:/ws/disk2/ws_brick Brick5: glusterfs2sds:/ws/disk2/ws_brick Brick6: glusterfs3sds:/ws/disk2/ws_brick Brick7: glusterfs1sds:/ws/disk3/ws_brick Brick8: glusterfs2sds:/ws/disk3/ws_brick Brick9: glusterfs3sds:/ws/disk3/ws_brick Brick10: glusterfs1sds:/ws/disk4/ws_brick Brick11: glusterfs2sds:/ws/disk4/ws_brick Brick12: glusterfs3sds:/ws/disk4/ws_brick Brick13: glusterfs1sds:/ws/disk5/ws_brick Brick14: glusterfs2sds:/ws/disk5/ws_bric...