search for: 15t

...197T 61T 136T 31% /volumedisk1 [root at stor3 ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sdb1 25T 638G 24T 3% /mnt/disk_b1/glusterfs/vol0 /dev/sdb2 25T 654G 24T 3% /mnt/disk_b2/glusterfs/vol0 /dev/sdc1 50T 15T 35T 30% /mnt/disk_c/glusterfs/vol1 /dev/sdd1 50T 15T 35T 30% /mnt/disk_d/glusterfs/vol1 stor3data:/volumedisk0 101T 3,3T 97T 4% /volumedisk0 stor3data:/volumedisk1 197T 61T 136T 31% /volumedisk1 However I'm concerned be...

...volumedisk1 > > > [root at stor3 ~]# df -h > Filesystem Size Used Avail Use% Mounted on > /dev/sdb1 25T 638G 24T 3% /mnt/disk_b1/glusterfs/vol0 > /dev/sdb2 25T 654G 24T 3% /mnt/disk_b2/glusterfs/vol0 > /dev/sdc1 50T 15T 35T 30% /mnt/disk_c/glusterfs/vol1 > /dev/sdd1 50T 15T 35T 30% /mnt/disk_d/glusterfs/vol1 > stor3data:/volumedisk0 > 101T 3,3T 97T 4% /volumedisk0 > stor3data:/volumedisk1 > 197T 61T 136T 31% /volumedisk1 >...

...; >> [root at stor3 ~]# df -h >> Filesystem Size Used Avail Use% Mounted on >> /dev/sdb1 25T 638G 24T 3% /mnt/disk_b1/glusterfs/vol0 >> /dev/sdb2 25T 654G 24T 3% /mnt/disk_b2/glusterfs/vol0 >> /dev/sdc1 50T 15T 35T 30% /mnt/disk_c/glusterfs/vol1 >> /dev/sdd1 50T 15T 35T 30% /mnt/disk_d/glusterfs/vol1 >> stor3data:/volumedisk0 >> 101T 3,3T 97T 4% /volumedisk0 >> stor3data:/volumedisk1 >> 197T 61T 136T 31...

...48G 21G 25G 46% / > tmpfs 32G 80K 32G 1% /dev/shm > /dev/sda1 190M 62M 119M 35% /boot > /dev/sda4 395G 251G 124G 68% /data > /dev/sdb1 26T 601G 25T 3% /mnt/glusterfs/vol0 > /dev/sdc1 50T 15T 36T 29% /mnt/glusterfs/vol1 > stor1data:/volumedisk0 > 76T 1,6T 74T 3% /volumedisk0 > stor1data:/volumedisk1 > *148T* 42T 106T 29% /volumedisk1 > > Exactly 1 brick minus: 196,4 TB - 49,1TB = 148TB > > It's a produc...

...at stor3 ~]# df -h >>> Filesystem Size Used Avail Use% Mounted on >>> /dev/sdb1 25T 638G 24T 3% /mnt/disk_b1/glusterfs/vol0 >>> /dev/sdb2 25T 654G 24T 3% /mnt/disk_b2/glusterfs/vol0 >>> /dev/sdc1 50T 15T 35T 30% /mnt/disk_c/glusterfs/vol1 >>> /dev/sdd1 50T 15T 35T 30% /mnt/disk_d/glusterfs/vol1 >>> stor3data:/volumedisk0 >>> 101T 3,3T 97T 4% /volumedisk0 >>> stor3data:/volumedisk1 >>>...

...nted on /dev/sda2 48G 21G 25G 46% / tmpfs 32G 80K 32G 1% /dev/shm /dev/sda1 190M 62M 119M 35% /boot /dev/sda4 395G 251G 124G 68% /data /dev/sdb1 26T 601G 25T 3% /mnt/glusterfs/vol0 /dev/sdc1 50T 15T 36T 29% /mnt/glusterfs/vol1 stor1data:/volumedisk0 76T 1,6T 74T 3% /volumedisk0 stor1data:/volumedisk1 *148T* 42T 106T 29% /volumedisk1 Exactly 1 brick minus: 196,4 TB - 49,1TB = 148TB It's a production system so I hope you can help me....

...-h >>>> Filesystem Size Used Avail Use% Mounted on >>>> /dev/sdb1 25T 638G 24T 3% /mnt/disk_b1/glusterfs/vol0 >>>> /dev/sdb2 25T 654G 24T 3% /mnt/disk_b2/glusterfs/vol0 >>>> /dev/sdc1 50T 15T 35T 30% /mnt/disk_c/glusterfs/vol1 >>>> /dev/sdd1 50T 15T 35T 30% /mnt/disk_d/glusterfs/vol1 >>>> stor3data:/volumedisk0 >>>> 101T 3,3T 97T 4% /volumedisk0 >>>> stor3data:/volumedisk1 >>>>...

...th ZFS. Consolidating a pair of other file servers that used to have a dozen or so NFS exports in /etc/dfs/dfstab similar to; /export/solaris/images /export/tools /export/ws ..... and so on.... For the new server, I have one large zfs pool; -bash-3.00# df -hl bigpool 16T 1.5T 15T 10% /export that I am starting to populate. Should I simply share /export, or should I separately share the individual dirs in /export like the old dfstab did? I am assuming that one single command; # zfs set sharenfs=ro bigpool would share /export as a read-only NFS point? Opinions/comm...

...b kernel: EXT3-fs error (device sd(8,1)): ext3_new_block: block(1852807396) >= blocks count(1651339086) - block_group = 0, es == f78b6400 Only the first partition is damaged (/dev/sda1) but that's the / in the fs. Filesystem Size Used Avail Use% Mounted on /dev/sda1 15T 15T 0 100% / /dev/sda2 13G 3.2G 9.1G 26% /home none 504M 0 503M 0% /dev/shm or something like that... I have already tried to install the RH7.3 (with no need dpt drivers), but it was the same problem. That's curieus because, I have ran redhat 7.2 fo...

...>> Filesystem Size Used Avail Use% Mounted on >>>>> /dev/sdb1 25T 638G 24T 3% /mnt/disk_b1/glusterfs/vol0 >>>>> /dev/sdb2 25T 654G 24T 3% /mnt/disk_b2/glusterfs/vol0 >>>>> /dev/sdc1 50T 15T 35T 30% /mnt/disk_c/glusterfs/vol1 >>>>> /dev/sdd1 50T 15T 35T 30% /mnt/disk_d/glusterfs/vol1 >>>>> stor3data:/volumedisk0 >>>>> 101T 3,3T 97T 4% /volumedisk0 >>>>> stor3data:/volumedisk1 &gt...

...EE;#TX-S8U-#,R,0H*6T1R:79E($-="E!A=&@]+VUN="]W M:6Y?8PI4>7!E/6AD"DQA8F5L/4U3+41/4PI&:6QE<WES=&5M93UM<V1O<PH* M6T1R:79E($1="E!A=&@]+VUN="]C9')O;0I4>7!E/6-D<F]M"DQA8F5L/4-$ M+5)O;0I&:6QE<WES=&5M/7=I;CDU"@I;1')I=F4@15T*4&%T:#TO;6YT+W=I M;E]C+W=I;F1O=W,O=&5M<`I4>7!E/6AD"DQA8F5L/51M<"!$<FEV90I&:6QE M<WES=&5M/7=I;CDU"@I;1')I=F4@1ET*4&%T:#TD>TA/345]"E1Y<&4];F5T M=V]R:PI,86)E;#U(;VUE"D9I;&5S>7-T96T]=VEN.34*"EMW:6YE70I7:6YD M;W=S/6,Z7...

Hi, we have a new fileserver running on X4275 hardware with Solaris 10U8. On this fileserver we created one test dir with quota and mounted these on another Solaris 10 system. Here the quota command didnot show the used quota. Does this feature only work with OpenSolaris or is it intended to work on Solaris 10? Here what we did on the server: # zfs create -o mountpoint=/export/home2

Dear Devs, I have x4 4TB HDDs formatted with: mkfs.btrfs -L bu-16TB_0 -d raid1 -m raid1 /dev/sd[cdef] /etc/fstab mounts with the options: noatime,noauto,space_cache,inode_cache All on kernel 3.8.13. Upon using rsync to copy some heavily hardlinked backups from ReiserFS, I''ve seen: The following "block rsv returned -28" is repeated 7 times until there is a call trace

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