> >
> > Does the machine respond to ping?
>
> Yes
>
> >
> > If there is a gui does the mouse pointer move?
> >
>
> There is no GUI (nexentastor)
>
> > Does the keyboard numlock key respond at all ?
>
> Yes
>
> >
> > I just find it very hard to believe that such a
> > situation could exist as I
> > have done some *abusive* tests on a SunFire X4100
> > with Sun 6120 fibre
> > arrays ( in HA config ) and I could not get it to
> > become a warm brick like
> > you describe.
> >
> > How many processors does your machine have ?
>
> Full data:
>
> Motherboard: Asus m2n68-CM
> Initial memory: 3 Gb DDR2 ECC
> Actual memory: 8 GB DDR2 800
> CPU: Athlon X2 5200
> HD: 2 Seagate 1 WD (1,5 TB each)
> Pools: 1 RAIDZ pool
> datasets: 5 (ftp: 30 GB, varios: 170 GB, multimedia:
> 1,7TB, segur: 80 Gb prueba: 50 Mb)
> ZFS ver: 22
>
> The pool was created with EON-NAS 0.6 ... dedupe on,
Similar situation but with Opensolaris b133. Can ping machine but its frozen
about 24 hours. I was deleting 25GB of dedup data. If I move 1-2 GB of data
then the machine stops responding for 1 hour but comes back after that. I have
munin installed and the graphs stop updating during that time and you can not
use ssh. I agree that memory seems to not be enough as I see a lot of 20kb
reads before it stops responding (reading DDT entries I guess). Maybe dedup has
to be redesigned for low memory machines (a batch process instead of inline ?)
This is my home machine so I can wait but businesses would not be so happy if
the machine becomes so unresponsive that you can not access your data.
NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT
data 5.44T 4.76T 691G 87% 1.18x ONLINE -
rpool 111G 11.3G 99.7G 10% 1.00x ONLINE -
DDT-sha256-zap-duplicate: 2390516 entries, size 503 on disk, 386 in core
DDT-sha256-zap-unique: 13224217 entries, size 374 on disk, 190 in core
DDT histogram (aggregated over all DDTs):
bucket allocated referenced
______ ______________________________ ______________________________
refcnt blocks LSIZE PSIZE DSIZE blocks LSIZE PSIZE DSIZE
------ ------ ----- ----- ----- ------ ----- ----- -----
1 12.6M 1.53T 1.49T 1.49T 12.6M 1.53T 1.49T 1.49T
2 2.12M 241G 228G 228G 4.70M 534G 504G 503G
4 161K 14.8G 12.2G 12.2G 727K 66.2G 54.4G 54.4G
8 6.05K 419M 293M 294M 56.1K 3.69G 2.49G 2.50G
16 603 9.72M 5.45M 5.59M 12.4K 198M 111M 114M
32 351 18.5M 14.5M 14.6M 15.0K 861M 678M 680M
64 66 1.90M 734K 750K 5.60K 169M 64.0M 65.4M
128 25 1.51M 616K 622K 4.02K 224M 80.1M 80.9M
256 3 1.50K 1.50K 2.24K 912 456K 456K 682K
512 4 134K 6.50K 7.48K 2.89K 81.2M 5.77M 6.47M
1K 3 129K 1.50K 2.24K 4.19K 160M 2.09M 3.13M
8K 1 128K 512 766 9.22K 1.15G 4.61M 6.89M
Total 14.9M 1.78T 1.73T 1.73T 18.1M 2.12T 2.04T 2.04T
car...@quad:~$ ping 192.168.1.87
PING 192.168.1.87 (192.168.1.87) 56(84) bytes of data.
64 bytes from 192.168.1.87: icmp_seq=1 ttl=255 time=0.193 ms
64 bytes from 192.168.1.87: icmp_seq=2 ttl=255 time=0.187 ms
64 bytes from 192.168.1.87: icmp_seq=3 ttl=255 time=0.189 ms
64 bytes from 192.168.1.87: icmp_seq=4 ttl=255 time=0.160 ms
64 bytes from 192.168.1.87: icmp_seq=5 ttl=255 time=0.189 ms
64 bytes from 192.168.1.87: icmp_seq=6 ttl=255 time=0.184 ms
64 bytes from 192.168.1.87: icmp_seq=7 ttl=255 time=0.193 ms
--- 192.168.1.87 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 5998ms
rtt min/avg/max/mdev = 0.160/0.185/0.193/0.010 ms
System Specs:
Memory: 8GB DDR3
CPU: Core i7-860 2.8GHz (4 cores / 8 threads)
HD: 4 x 1.5TB Seagate 7200.11 Raidz
--
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
