search for: 136g

Hi, OS : Solaris 10 11/06 zpool list doesn''t reflect pool usage stats instantly. Why? # ls -l total 209769330 -rw------T 1 root root 107374182400 Apr 30 14:28 deleteme # zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT wo 136G 100G 36.0G 73% ONLINE - # rm deleteme # zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT wo 136G 100G 36.0G 73% ONLINE - ---> why ..... time passes # zpool list NAME SIZE US...

...(rest of cluster). Here's some df statments to help clarify: > > (brick1 = engine; brick2=data, brick4=iso): > Filesystem Size Used Avail Use% Mounted on > /dev/mapper/gluster-engine 25G 12G 14G 47% /gluster/brick1 > /dev/mapper/gluster-data 136G 125G 12G 92% /gluster/brick2 > /dev/mapper/gluster-iso 25G 7.3G 18G 29% /gluster/brick4 > 192.168.8.11:/engine 15G 9.7G 5.4G 65% > /rhev/data-center/mnt/glusterSD/192.168.8.11:_engine > 192.168.8.11:/data 136G 125G 12G 92% > /rhev/data-ce...

Hi, am I doing something wrong, ZFS does not support that or there is a bug that zvol clone does not show up under /dev/zvol after creating it from other zvol snapshot? # zfs list -t all | grep local local 136G 76.8G 144K none local/home 117G 76.8G 117G /home local/vm 18.4G 76.8G 144K none local/vm/vbox_pcbsd_10 5.35G 76.8G 5.35G - local/vm/vbox_windows_7 10.8G 76.8G 9.86G - local/vm/vbox_wi...

...when I do, I get this error: # zpool destroy oradata_fs1 cannot open ''oradata_fs1'': I/O error # The pools I have on this box look like this: #zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT oradata_fs1 532G 119K 532G 0% DEGRADED - rpool 136G 28.6G 107G 21% ONLINE - # Why can''t I delete this pool? This is on Solaris 10 5/09 s10s_u7.

...? - controller is a hp/compaq p400 (ciss) - da0 - da7 are raid0 volumes (controller not jbod capable) - freebsd 9.1 REL (same error message with 9-STABLE from 2013-03-24) - server is zfs-only # diskinfo -v da0 da0 512 # sectorsize 146778685440 # mediasize in bytes (136G) 286677120 # mediasize in sectors 0 # stripesize 0 # stripeoffset 35132 # Cylinders according to firmware. 255 # Heads according to firmware. 32 # Sectors according to firmware....

...gt; There is a *huge* difference between a functional Solr setup & squat > Interesting. Care to elaborate? This is one of those things that has to be experienced to be understood.? When you can perform an FTS search across (pause while I check current stats...): du -c -h /var/mail??? ??? 136G Solr numDocs:??? ??? 520102 and using any IMAP client that supports server-side searches (like Thunderbird & AquaMail) the results are basically instantaneous...it's worth the effort.? And that's searching a Dovecot virtual folder defined as "* all", including all my arch...

...etween a functional Solr setup & squat >> Interesting. Care to elaborate? > > This is one of those things that has to be experienced to be > understood.? When you can perform an FTS search across (pause while I > check current stats...): > > du -c -h /var/mail??? ??? 136G > > Solr numDocs:??? ??? 520102 > > and using any IMAP client that supports server-side searches (like > Thunderbird & AquaMail) the results are basically instantaneous...it's > worth the effort.? And that's searching a Dovecot virtual folder defined > as &quot...

Good day, Please am new on CentOS, may you help me with the upgrade from 5.8 to 6.2 using? Thanks a lot -- -- You Truly Eric Kom System Administrator - Metropolitan College _________________________________________ / You are scrupulously honest, frank, and \ | straightforward. Therefore you have few | \ friends. / -----------------------------------------

On 12/21/2018, 11:19:42 AM, Daniel Miller via dovecot <dovecot at dovecot.org> wrote: > There is a *huge* difference between a functional Solr setup & squat Interesting. Care to elaborate?

Looking for help regaining access to encrypted ZFS file systems that stopped accepting the encryption key. I have a file server with a setup as follows: Solaris 11 Express 1010.11/snv_151a 8 x 2-TB disks, each one divided into three equal size partitions, three raidz3 pools built from a "slice" across matching partitions: Disk 1 Disk 8 zpools +--+ +--+ |p1| .. |p1| <-

Hi: I need advice on implementing a storage server. I really do not have the $ to spend for a Dell iSCSI storage divice and I am thinking trunning CentOS 5.x with ftp or FreeNAS. Here is what I am looking at and concerned about. Situation: My current storage needs are approximately 1.5 TB annually. This will increase to about 3.5 TB annually over the next 5 years (rough est.). This box