search for: 21t

...ror message [root at nas-0-1 mseas-data-0-1]# touch dum touch: cannot touch `dum': No space left on device However, if I check the available space, there seems to be plenty [root at nas-0-1 mseas-data-0-1]# df -h . Filesystem Size Used Avail Use% Mounted on /dev/sdb1 21T 20T 784G 97% /mseas-data-0-1 [root at nas-0-1 mseas-data-0-1]# df -i . Filesystem Inodes IUsed IFree IUse% Mounted on /dev/sdb1 3290047552 4391552 3285656000 1% /mseas-data-0-1 I don't know if the following is relevant but the disk in question is served as one...

...ormance.write-behind-window-size: 4MB performance.cache-refresh-timeout: 1 performance.cache-size: 4GB network.frame-timeout: 60 performance.cache-max-file-size: 1GB As you can see 2 of the bricks are smaller and they're full. The gluster volume is not full of course: gl0:/w-vol 25T 21T 4.0T 84% /W/Projects I'm not able to write to the volume. Why? Is it an issue? If so, is it known? How can I stop writing to full nodes? Thanks, tamas

...80% /disco2TB-0 tmpfs 51G 4,0K 51G 1% /run/user/0 *gluster1:VMS 4,6T 3,6T 970G 80% /vms* /dev/fuse 128M 36K 128M 1% /etc/pve proxmox01:/vms/images# cd 103 proxmox01:/vms/images/103# ls vm-103-disk-0.qcow2 vm-103-disk-1.qcow2 proxmox01:/vms/images/103# ls -lh total 21T *-rw-r----- 1 root root 101G nov 11 15:53 vm-103-disk-0.qcow2-rw-r----- 1 root root 210G nov 11 15:45 vm-103-disk-1.qcow2* proxmox01:/vms/images/103# qemu-img info vm-103-disk-0.qcow2 image: vm-103-disk-0.qcow2 file format: qcow2 *virtual size: 100 GiB (107374182400 bytes)disk size: 3.78 TiB* clu...

...G ?80% /disco2TB-0 tmpfs ? ? ? ? ? ?51G ?4,0K ? 51G ? 1% /run/user/0 gluster1:VMS ? ?4,6T ?3,6T ?970G ?80% /vms /dev/fuse ? ? ? 128M ? 36K ?128M ? 1% /etc/pve proxmox01:/vms/images# cd 103 proxmox01:/vms/images/103# ls vm-103-disk-0.qcow2 ?vm-103-disk-1.qcow2 proxmox01:/vms/images/103# ls -lh total 21T -rw-r----- 1 root root 101G nov 11 15:53 vm-103-disk-0.qcow2 -rw-r----- 1 root root 210G nov 11 15:45 vm-103-disk-1.qcow2 proxmox01:/vms/images/103# qemu-img info vm-103-disk-0.qcow2 image: vm-103-disk-0.qcow2 file format: qcow2 virtual size: 100 GiB (107374182400 bytes) disk size: 3.78 TiB cluste...

Hello all, I have just configured a 64-bit CentOS 5.5 machine to support an XFS filesystem as specified in the subject line. The filesystem will be used to store an extremely large number of files (in the tens of millions). Due to its extremely large size, would there be any non-standard XFS build/configuration options I should consider? Thanks. Boris. -------------- next part -------------- An

Hi All I downloaded the binary package of Samba 2.2.2 on Friday from one of the Samba mirror sites, I think Belgium, and installed it on a Sun E450 running Solaris 2.6. Today everything has fallen flat on its face. Unfortunately I am on holiday this week so not able to deal with the problem directly, but via telephone calls. Apparently what is happening is that smbd is gobbling up all the

...0VQO<V5523H@*D-8 M7T,R1%]#;VYT<F%S=`T*#0HJ3W!E;E5)("I#6%]#,D1?4D="5V]R:V9L;W<O M4D="(%=O<FMF;&]W.B!0:6-K3VYE#0HJ3W)D97)$97!E;F1E;F-Y.B`R,"!$ M;V-U;65N=%-E='5P("I#6%]#,D1?4D="5V]R:V9L;W<-"BI$969A=6QT0UA? M0S)$7U)'0E=O<FMF;&]W.B!$96921T)#4T$-"BI#6%]#,D1?4D="5V]R:V9L M;W<@1&5F4D="0U-!+U!R:6YT97(G<R!$969A=6QT.B`B)5-#25!01#H@1$9% M(%)'0E]#4T$@4')I;G1E<B=S(@T**D-87T,R1%]21T)7;W)K9FQO=R!5<V53 M;W5R8V4O57-E(%-O=7)C92!#4T$Z("(E4T-)4%!$.B!$1D4@4D="7T-302!3 M;W5R8V4B#0HJ0UA?0S)$7U)'0E=O&...