[FUG-BR] entusiasmo com o ZFS

William David Armstrong - FUGBr fugbr em biosystems.ath.cx
Quinta Setembro 23 11:12:33 BRT 2010


bom até onde eu conheço nao se deve utilizar cache  com ZFS em raidZ
pois o cache pode corromper a gravação da  paridade no disco.
esta no manual do zfs atualizado.

Consider the following points when determining whether to create a ZFS storage pool with cache devices:
added and removed after the pool is created. For more information, see Example 4–4. Chapter4 • ManagingOracleSolarisZFSStoragePools	71
Creating and Destroying ZFS Storage Pools
Creating and Destroying ZFS Storage Pools
Cache devices cannot be mirrored or be part of a RAID-Z configuration.
If a read error is encountered on a cache device, that read I/O is reissued to the original storage pool device, which might be part of a mirrored or a RAID-Z configuration. The content of the cache devices is considered volatile, similar to other system caches.

espero ter ajudado

 estou esperando o  ZFS v28  que o PWD esta portando pra versão estável do freebsd.

Em 23/09/2010, às 10:53, Ion-Mihai Tetcu escreveu:

> On Wed, 22 Sep 2010 15:06:23 -0300
> Alessandro de Souza Rocha <etherlinkii em gmail.com> wrote:
> 
>> eu fiz um raid1 com 2 hds de 80gb.
>> alessandro em nslink:/home/alessandro# zpool list
>> NAME    SIZE   USED  AVAIL    CAP  HEALTH  ALTROOT
>> zroot  69.5G  5.14G  64.4G     7%  ONLINE  -
> 
> My desktop:
> 
> root(itetcu)@it> /usr/ports/editors/vim [16:21:21] 0
> # zpool status
>  pool: tank
> state: ONLINE
> scrub: none requested
> config:
> 
>        NAME        STATE     READ WRITE CKSUM
>        tank        ONLINE       0     0     0
>          raidz2    ONLINE       0     0     0
>            ad6     ONLINE       0     0     0
>            ad8     ONLINE       0     0     0
>            ad10    ONLINE       0     0     0
>            ad12    ONLINE       0     0     0
>            ad14    ONLINE       0     0     0
>        cache
>          da0       UNAVAIL      0     0     0  cannot open
>          da1       UNAVAIL      0     0     0  cannot open
> 
> errors: No known data errors
> root(itetcu)@it> /usr/ports/editors/vim [16:21:23] 0
> # zfs list
> NAME                       USED  AVAIL  REFER  MOUNTPOINT
> tank                       739G   621G  32.2K  /tank
> tank/compat                261M   621G  32.2K  none
> tank/compat/linux          261M   621G   261M  /compat/linux
> tank/usr                   739G   621G  32.2K  none
> tank/usr/home              728G   621G  34.0K  /usr/home
> tank/usr/home/itetcu       728G   621G   720G  /usr/home/itetcu
> tank/usr/local            5.66G   621G  5.59G  /usr/local
> tank/usr/ports            4.76G   621G  1.38G  /usr/ports
> tank/usr/ports/distfiles  3.32G   621G  3.31G  /usr/ports/distfiles
> tank/var                   254M   621G  34.0K  none
> tank/var/db                254M   621G  32.2K  none
> tank/var/db/pkg           47.3M   621G  42.4M  /var/db/pkg
> tank/var/db/portindex     93.6M   621G  61.0M  /var/db/portindex
> tank/var/db/ports         3.07M   621G  2.61M  /var/db/ports
> tank/var/db/sup            110M   621G  34.8M  /var/db/sup
> root(itetcu)@it> /usr/ports/editors/vim [16:22:34] 0
> # zfs list -t snapshot | wc -l
>     958
> 
> Os dois dispositivos de cache sao dois sticks USB que morreu.
> 
> 
> 
> -- 
> IOnut - Un^d^dregistered ;) FreeBSD "user"
>  "Intellectual Property" is   nowhere near as valuable   as "Intellect"
> FreeBSD committer -> itetcu em FreeBSD.org, PGP Key ID 057E9F8B493A297B
> -------------------------
> Histórico: http://www.fug.com.br/historico/html/freebsd/
> Sair da lista: https://www.fug.com.br/mailman/listinfo/freebsd



Mais detalhes sobre a lista de discussão freebsd