search for: disk10

..._brick Brick23: glusterfs2sds:/ws/disk8/ws_brick Brick24: glusterfs3sds:/ws/disk8/ws_brick Brick25: glusterfs4sds.commvault.com:/ws/disk1/ws_brick Brick26: glusterfs5sds.commvault.com:/ws/disk1/ws_brick Brick27: glusterfs6sds.commvault.com:/ws/disk1/ws_brick Brick28: glusterfs4sds.commvault.com:/ws/disk10/ws_brick Brick29: glusterfs5sds.commvault.com:/ws/disk10/ws_brick Brick30: glusterfs6sds.commvault.com:/ws/disk10/ws_brick Brick31: glusterfs4sds.commvault.com:/ws/disk11/ws_brick Brick32: glusterfs5sds.commvault.com:/ws/disk11/ws_brick Brick33: glusterfs6sds.commvault.com:/ws/disk11/ws_brick Brick...

...gt; > Brick24: glusterfs3sds:/ws/disk8/ws_brick > > Brick25: glusterfs4sds.commvault.com:/ws/disk1/ws_brick > > Brick26: glusterfs5sds.commvault.com:/ws/disk1/ws_brick > > Brick27: glusterfs6sds.commvault.com:/ws/disk1/ws_brick > > Brick28: glusterfs4sds.commvault.com:/ws/disk10/ws_brick > > Brick29: glusterfs5sds.commvault.com:/ws/disk10/ws_brick > > Brick30: glusterfs6sds.commvault.com:/ws/disk10/ws_brick > > Brick31: glusterfs4sds.commvault.com:/ws/disk11/ws_brick > > Brick32: glusterfs5sds.commvault.com:/ws/disk11/ws_brick > > Brick33: glu...

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/disk8/ws_brick >> >> Brick25: glusterfs4sds.commvault.com:/ws/disk1/ws_brick >> >> Brick26: glusterfs5sds.commvault.com:/ws/disk1/ws_brick >> >> Brick27: glusterfs6sds.commvault.com:/ws/disk1/ws_brick >> >> Brick28: glusterfs4sds.commvault.com:/ws/disk10/ws_brick >> >> Brick29: glusterfs5sds.commvault.com:/ws/disk10/ws_brick >> >> Brick30: glusterfs6sds.commvault.com:/ws/disk10/ws_brick >> >> Brick31: glusterfs4sds.commvault.com:/ws/disk11/ws_brick >> >> Brick32: glusterfs5sds.commvault.com:/ws/disk11...

...>>> Brick25: glusterfs4sds.commvault.com:/ws/disk1/ws_brick >>> >>> Brick26: glusterfs5sds.commvault.com:/ws/disk1/ws_brick >>> >>> Brick27: glusterfs6sds.commvault.com:/ws/disk1/ws_brick >>> >>> Brick28: glusterfs4sds.commvault.com:/ws/disk10/ws_brick >>> >>> Brick29: glusterfs5sds.commvault.com:/ws/disk10/ws_brick >>> >>> Brick30: glusterfs6sds.commvault.com:/ws/disk10/ws_brick >>> >>> Brick31: glusterfs4sds.commvault.com:/ws/disk11/ws_brick >>> >>> Brick32: gluste...

...usterfs4sds.commvault.com:/ws/disk1/ws_brick >>>> >>>> Brick26: glusterfs5sds.commvault.com:/ws/disk1/ws_brick >>>> >>>> Brick27: glusterfs6sds.commvault.com:/ws/disk1/ws_brick >>>> >>>> Brick28: glusterfs4sds.commvault.com:/ws/disk10/ws_brick >>>> >>>> Brick29: glusterfs5sds.commvault.com:/ws/disk10/ws_brick >>>> >>>> Brick30: glusterfs6sds.commvault.com:/ws/disk10/ws_brick >>>> >>>> Brick31: glusterfs4sds.commvault.com:/ws/disk11/ws_brick >>>>...

..._brick Brick23: glusterfs2sds:/ws/disk8/ws_brick Brick24: glusterfs3sds:/ws/disk8/ws_brick Brick25: glusterfs4sds.commvault.com:/ws/disk1/ws_brick Brick26: glusterfs5sds.commvault.com:/ws/disk1/ws_brick Brick27: glusterfs6sds.commvault.com:/ws/disk1/ws_brick Brick28: glusterfs4sds.commvault.com:/ws/disk10/ws_brick Brick29: glusterfs5sds.commvault.com:/ws/disk10/ws_brick Brick30: glusterfs6sds.commvault.com:/ws/disk10/ws_brick Brick31: glusterfs4sds.commvault.com:/ws/disk11/ws_brick Brick32: glusterfs5sds.commvault.com:/ws/disk11/ws_brick Brick33: glusterfs6sds.commvault.com:/ws/disk11/ws_brick Brick...

...gt; > Brick24: glusterfs3sds:/ws/disk8/ws_brick > > Brick25: glusterfs4sds.commvault.com:/ws/disk1/ws_brick > > Brick26: glusterfs5sds.commvault.com:/ws/disk1/ws_brick > > Brick27: glusterfs6sds.commvault.com:/ws/disk1/ws_brick > > Brick28: glusterfs4sds.commvault.com:/ws/disk10/ws_brick > > Brick29: glusterfs5sds.commvault.com:/ws/disk10/ws_brick > > Brick30: glusterfs6sds.commvault.com:/ws/disk10/ws_brick > > Brick31: glusterfs4sds.commvault.com:/ws/disk11/ws_brick > > Brick32: glusterfs5sds.commvault.com:/ws/disk11/ws_brick > > Brick33: glu...

...ze bsize bps/cpg] b: 265 0 swap # (Cyl. 0 - 0*) c: 320172993 0 unused 0 0 # (Cyl. 0 - 317631*) e: 320172728 265 vinum # (Cyl. 0*- 317631*) and the vinum objects on this disk: D disk10 State: up Device /dev/ad4s1e Avail: 0/156334 MB (0%) V arch State: up Plexes: 1 Size: 152 GB P arch.p0 S State: up Subdisks: 1 Size: 152 GB S arch.p0.s0 State: up PO: 0 B...

Hi everyone, I'm playing with Gluster3.3b2, and everything is working fine when uploading stuff through swift. However, when I enable quotas on Gluster, I randomly get permission errors. Sometimes I can upload files, most times I can't. I'm mounting the partitions with the acl flag, I've tried wiping out everything and starting from scratch, same result. As soon as I

.../dev/da5a Avail: 3/4094 MB (0%) D disk05 State: up Device /dev/da6a Avail: 3/4094 MB (0%) D disk08 State: up Device /dev/da7a Avail: 3/4094 MB (0%) D disk09 State: up Device /dev/da8a Avail: 3/4094 MB (0%) D disk10 State: up Device /dev/da9a Avail: 3/4094 MB (0%) D disk11 State: up Device /dev/da10a Avail: 3/4094 MB (0%) D disk12 State: up Device /dev/da11a Avail: 3/4094 MB (0%) D disk13 State: up Device /de...

A lot of code runs 'qemu-img create' or 'truncate' to create blank disk images. In the past I resisted adding an API to do this, since it essentially duplicates what you can already do using other tools (ie. qemu-img). However this does simplify calling code quite a lot since qemu-img is somewhat error-prone to use (eg: don't try to create a disk called "foo:bar")