search for: disk5

...ill install guest system in paravirtualized mode (mine processor does not support full virtualization). I.Xen DomU installation 1.Install xen kernel kernel-xen-2.6.18-8.el5.i686.rpm kernel-xen-devel-2.6.18-8.el5.i686.rpm 2.When i tried to install xen : rpm -Uvh xen-3.0.3-25.el5.i386.rpm -Disk5 I had following dep missing error: Failed dependencies: bridge-utils is needed by xen-3.0.3-25.el5.i386 libSDL-1.2.so.0 is needed by xen-3.0.3-25.el5.i386 libblktap.so.3.0 is needed by xen-3.0.3-25.el5.i386 libxenctrl.so.3.0 is needed by xen-3.0.3-25.el5.i386...

...al master = no max connections = 100 create mask = 0777 directory mask = 0777 preserve case = yes short preserve case = no dos filetime resolution = yes syslog = 1 syslog only = no #============================ Share Definitions ============================== [V] comment = Kopie disk5 path = /disk5 read only = yes # create mask = 0777 # directory mask = 0777 [Z] comment = Kopie disk5 path = /opt/samba/bin/test read only = no # create mask = 0777 # directory mask = 0777 ############################################################################ ###########...

...3sds:/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_brick Brick15: glusterfs3sds:/ws/disk5/ws_brick Brick16: glusterfs1sds:/ws/disk6/ws_brick Brick17: glusterfs2sds:/ws/disk6/ws_brick Brick18: glusterfs3sds:/ws/disk6/ws_brick Brick19: glusterfs1sds:/ws/disk7/ws_brick Brick20: glusterfs2sds:/ws/disk7/ws_br...

...rick > > 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_brick > > Brick15: glusterfs3sds:/ws/disk5/ws_brick > > Brick16: glusterfs1sds:/ws/disk6/ws_brick > > Brick17: glusterfs2sds:/ws/disk6/ws_brick > > Brick18: glusterfs3sds:/ws/disk6/ws_brick > > Brick19: glusterfs1s...

Hi, rsync was running against filesystems /disk5 and /disk7 to back them onto remote server (172.16.101.4) using the following script: if [ `ps -ef | grep -v grep | grep ::d5 | /usr/bin/wc -l` -eq 0 ] then rm -f /etc/rsync5.log echo " --- Disk5 --- starts `date`" > /etc/rsync5.log /usr/local/bin/rsync -a --recursive --compress /disk...

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

.../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_brick >> >> Brick15: glusterfs3sds:/ws/disk5/ws_brick >> >> Brick16: glusterfs1sds:/ws/disk6/ws_brick >> >> Brick17: glusterfs2sds:/ws/disk6/ws_brick >> >> Brick18: glusterfs3sds:/ws/disk6...

...; 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_brick >>> >>> Brick15: glusterfs3sds:/ws/disk5/ws_brick >>> >>> Brick16: glusterfs1sds:/ws/disk6/ws_brick >>> >>> Brick17: glusterfs2sds:/ws/disk6/ws_brick >>> >&...

...3/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_brick >>>> >>>> Brick15: glusterfs3sds:/ws/disk5/ws_brick >>>> >>>> Brick16: glusterfs1sds:/ws/disk6/ws_brick >>>> >>>> Brick17: glusterfs2sds:/ws/d...

...3sds:/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_brick Brick15: glusterfs3sds:/ws/disk5/ws_brick Brick16: glusterfs1sds:/ws/disk6/ws_brick Brick17: glusterfs2sds:/ws/disk6/ws_brick Brick18: glusterfs3sds:/ws/disk6/ws_brick Brick19: glusterfs1sds:/ws/disk7/ws_brick Brick20: glusterfs2sds:/ws/disk7/ws_br...

...rick > > 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_brick > > Brick15: glusterfs3sds:/ws/disk5/ws_brick > > Brick16: glusterfs1sds:/ws/disk6/ws_brick > > Brick17: glusterfs2sds:/ws/disk6/ws_brick > > Brick18: glusterfs3sds:/ws/disk6/ws_brick > > Brick19: glusterfs1s...

...the logical volume groups are visible on all servers. On the backup server I have the following running: # guestmount --version guestmount 1.40.2 # guestmount --ro -a /dev/lvm1-vol/sr8-disk1a -a /dev/lvm1-vol/sr8-disk2 -a /dev/lvm1-vol/sr8-disk3 -a /dev/lvm1-vol/sr8-disk4 -a /dev/lvm1-vol/sr8-disk5 -a /dev/lvm1-vol/sr8-disk6 -m /dev/sdb2 /mnt/sr8-sdb2 # rsync --archive --delete --partial --progress --recursive --no-links --no-devices --quiet /mnt/sr8-sdb2/ /srv/storage/backups/libvirt-filesystems/sr8-sdb2 This used to go fine for many years (we helped with the development of deduplicati...

...tem we created one VM and passed through 3x2TB disks into it. In guests vms on top of this disks we made XFS and fired up glusterfs with distributed replicated volumes for our mailstorage. so it looks like this: vm1??? replicate???? vm2 disk1 ------------> disk4 disk2 ------------> disk5 disk3 ------------> disk6 in each vm we mounted glusterfs and pointed dovecot to that dir for mail creation (as ltmp) and imap4 user access. also we use exim as smtp. So, with glusterfs as mailstorage we can go for LVS to load balancing for exim and dovecot. so wherenever one of host...

...*.img file:*.img guestfish <<EOF disk-create disk1.img raw 256K + disk-create disk2.img raw 256K preallocation:off disk-create disk2.img raw 256K preallocation:sparse disk-create disk3.img raw 256K preallocation:full disk-create disk4.img qcow2 256K disk-create disk5.img qcow2 256K preallocation:off + disk-create disk5.img qcow2 256K preallocation:sparse disk-create disk6.img qcow2 256K preallocation:metadata + disk-create disk6.img qcow2 256K preallocation:full disk-create disk7.img qcow2 256K compat:1.1 disk-create disk8.img qcow2 256K cluste...

Hi, I installed a zpool containing of zpool __mirror ____disk1 500gb ____disk2 500gb __raidz ____disk3 1tb ____disk4 1tb ____disk5 1tb It works fine, but it displays the wrong size (terminal -> zpool list). It should be 500gb (mirrored) + 2TB (3TB raidz) = 2,5 TB, right? But it displays it has 3,17TB diskspace available. I first created the mirror and then added the raidz to it (zpool add -f poolname raidz disk 3 disk4 di...

.../disco2/vms2 gluster2:/disco3/vms3 force And mounted into /vms like this: gluster1:VMS /vms glusterfs defaults,_netdev,x-systemd.automount,backupvolfile-server=gluster2 0 0 Later on, I add more 3 HDD, like: mkfs.xfs /dev/sdf mkfs.xfs /dev/sdg mkfs.xfs /dev/sdh mount /dev/sdf /disk4 mount /dev/sdg /disk5 mount /dev/sdh /disk6 And than, I add the bricks: gluster vol add-brick VMS replica 2 gluster1:/disco4/vms4 gluster1:/disco4/vms5 gluster1:/disco5/vms5 gluster2:/disco4/vms4 gluster2:/disco4/vms5 gluster2:/disco5/vms5 force The /vms mounted grow up normally. So my question: is there anything dange...

...syntax however I don't know the right way to detect disk change. In my patch I try to read first sector than I read again informations and fat however if file have same name (initrd.img on first disk and initrd.img on second) how to detect disk change? Use disk labels or add a empty file (like disk5.id or disk.5 or whatever) ?? freddy77

On Fri, 11 Jul 1997, Hermann Lauer wrote: > The bad news: One of my Users complains that the Visual C 5.0 Compiler stops > working with mysterious error messages (On a NT 4.0SP3 Workstation). > The compiler seems not to find required dlls, exes and so on - despite the > fact, > that it is installed locally and only the files it works on comes via samba. I have found that the M$ VC

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

Dear list, I try to update the prabclus package. R CMD check works nicely, no warnings, good results in all tests. However, building the package fails: ginkgo:/disk5/home/chrish/RAusw/libsrc R CMD build prabclus * checking for file 'prabclus/DESCRIPTION' ... OK * preparing 'prabclus': * checking whether 'INDEX' is up-to-date ... OK * removing junk files * building 'prabclus_2.0-1.tar.gz' tar: prabclus/man/.#prabinit.Rd: Cannot st...