search for: 67g

Hi Gluster experts, I'm new to glusterfs and I have encountered a problem about list directory of glusters 3.3. I have a volume configuration of 3(distribute) * 2(replica). When write file on the glusterfs client mount directory some of the files can't be listed through ls command but the file exists. Some times the ls command hangs. Any one know what's the problem is? Thank you

...reason for the discrepancy). qemu-img info reports: file format: qcow2 virtual size: 100G (107374182400 bytes) disk size: 70G cluster_size: 65536 Format specific information: compat: 0.10 I used Windows Server 2012r2 "Optimize" (defrag) and then reduced the C: partition to about 67G in Disk Administrator leaving the remaining 33G as unallocated. Afterward I tried a web reference technique and used Sysinternals SDelete to zero the free space then used 'qemu-img convert -O qcow2 <original.qcow2> <new.qcow2>' to produce a physical image size of 29G. qemu-im...

...0 2070 >> >> uname -a >> Linux nas1 2.6.14.2-smp #2 SMP Thu Nov 17 15:31:40 GMT 2005 x86_64 >> x86_64 >> x86_64 GNU/Linux >> >> df -h >> Filesystem Size Used Avail Use% Mounted on >> /dev/sda1 73G 6.0G 67G 9% / >> tmpfs 2.0G 0 2.0G 0% /dev/shm >> /dev/sdb 6.9T 263G 6.6T 4% /storage >> >> lsscsi >> [0:0:0:0] disk ATA HTS541080G9SA00 MB4O /dev/sda >> [4:0:1:0] tape CERTANCE ULTRIUM 2 1775 /dev/st0 &...

...d 5e8325ec7f66b5189c65c7a8710fe8cb) depends: ocfs2_nodemanager,ocfs2_dlm,jbd,debugfs vermagic: 2.6.9-89.0.26.ELsmp SMP gcc-3.4 # When I run df -h to show available disk space It shows as follows # df -h cfs Filesystem Size Used Avail Use% Mounted on /dev/emcpowera1 67G 42G 26G 62% /d00/cfs But actual usage is much less :- # du -sh /d00/cfs 18G cfs I have the output of stat_sysdir.sh if needed, but it is over 11,000 lines long. I think this might be to do with inodes or something not being freed up - but am not 100% sure? Given I am stuck on Red Hat...

When I run df -h to show available disk space It shows as follows ? # df -h . Filesystem??????????? Size? Used Avail Use% Mounted on /dev/emcpowera1??????? 67G?? 42G?? 26G? 62% /d00/cfs ? But actual usage is much less :- ? # du -sh /d00/cfs 18G???? cfs ? I have the output of stat_sysdir.sh if needed, but it is very long. ? I think this might be to do with inodes or something not being freed up - but am not 100% sure? ? I am running OCFS2 1.2.9 on RHEL 4 K...

...2.9G 67% /lib/libc.so.1 fd 0K 0K 0K 0% /dev/fd swap 2.2G 40K 2.2G 1% /tmp swap 2.2G 40K 2.2G 1% /var/run /dev/dsk/c1t0d0s7 57G 3.6G 53G 7% /export/home ZPOOL 67G 18K 60G 1% /ZPOOL hs-usca-05.sfbay:/export/home1/14/ht156504 246G 226G 20G 92% /home/ht156504 # zpool destroy ZPOOL -- Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- Yo...

...:25 lost+found 47427620 -rwxr-xr-x 1 root root 107374182400 Mar 14 13:36 sa.raw 47410284 -rwxr-xr-x 1 root root 107374182400 Mar 14 11:37 sa.raw.snap ha-idg-1:/cluster/guests/servers_alive # df -h Filesystem Size Used Avail Use% Mounted on ... /dev/dm-9 115G 49G 67G 42% /cluster/guests/servers_alive You see that just 49GB are allocated, because the source has not grown to the maximum, and the reflink occupies no space in the beginning. Maximum size is 100GB. I would now expect a rsync from the snap would transfer just some megay bytes to the file from the...

Hello, i am creating my XEN VM with virt-install (see below). When I create new images i do first an "df -h" to see if there is still enough space left on the drive. Are the XEN images pre allocated or does XEN only use that space that really is used by the VM inside the image? I know have the Problem that an "du -h" inside my /VM folder gives me nearly a higher number that

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking