Hello.
Patch worked as expected - no compresion on l2, but
a) l2arc couse big overhad on fs io
b) after some time errors apears again.
For now best choice not to use any patch on system
so, for now we delete next changes from system
1)
Cc: Vitalij Satanivskij sa...@ukr.net; Dmitriy Makarov
suppor...@ukr.net; freebsd-current@freebsd.org
SH Sent: Friday, October 25, 2013 8:32 AM
SH Subject: Re: ZFS L2ARC - incorrect size and abnormal system load on r255173
SH
SH
SH Just after system reboot with this patch
SH
SH found
SH
Satanivskij sa...@ukr.net; Dmitriy Makarov suppor...@ukr.net;
freebsd-current@freebsd.org
SH Sent: Friday, October 25, 2013 8:32 AM
SH Subject: Re: ZFS L2ARC - incorrect size and abnormal system load on r255173
SH
SH
SH Just after system reboot with this patch
SH
SH found
SH
I dont apply previos patch on high load server, only on test where find that
it's not disabling compression.
Thank you for help, i will try new patch as soon as posible.
SH
SH Have you seen any l2_io_error or l2_cksum_bad since
SH applying the ashift patch?
SH
Cc: freebsd-current@freebsd.org
VS SH Sent: Thursday, October 10, 2013 6:03 PM
VS SH Subject: Re: ZFS L2ARC - incorrect size and abnormal system load on
r255173
VS SH
VS SH
VS SH AJ Some background on L2ARC compression for you:
VS SH AJ
VS SH AJ http://wiki.illumos.org/display/illumos/L2ARC
Just after system reboot with this patch
found
kstat.zfs.misc.arcstats.l2_compress_successes: 6083
kstat.zfs.misc.arcstats.l2_compress_zeros: 1
kstat.zfs.misc.arcstats.l2_compress_failures: 296
compression on test pool (where I'm test this patch) is lz4
so is it ok ?
Steven Hartland
Sent: Friday, October 25, 2013 8:32 AM
Subject: Re: ZFS L2ARC - incorrect size and abnormal system load on r255173
Just after system reboot with this patch
found
kstat.zfs.misc.arcstats.l2_compress_successes: 6083
kstat.zfs.misc.arcstats.l2_compress_zeros: 1
-current@freebsd.org
Sent: Thursday, October 10, 2013 6:03 PM
Subject: Re: ZFS L2ARC - incorrect size and abnormal system load on r255173
AJ Some background on L2ARC compression for you:
AJ
AJ http://wiki.illumos.org/display/illumos/L2ARC+Compression
I'm alredy see it.
AJ http://svnweb.freebsd.org
10, 2013 6:03 PM
SH Subject: Re: ZFS L2ARC - incorrect size and abnormal system load on r255173
SH
SH
SH AJ Some background on L2ARC compression for you:
SH AJ
SH AJ http://wiki.illumos.org/display/illumos/L2ARC+Compression
SH
SH I'm alredy see it.
SH
SH
SH
SH AJ http
: Thursday, October 10, 2013 6:03 PM
SH Subject: Re: ZFS L2ARC - incorrect size and abnormal system load on r255173
SH
SH
SH AJ Some background on L2ARC compression for you:
SH AJ
SH AJ http://wiki.illumos.org/display/illumos/L2ARC+Compression
SH
SH I'm alredy see it.
SH
SH
SH
SH AJ http
Same situation hapend yesterday again :(
What's confuse me while trying to understend where I'm wrong
Firt some info.
We have zfs pool POOL and one more zfs on it POOL/zfs
POOL - have only primarycache enabled ALL
POOL/zfs - have both primay and secondary for ALL
POOL have compression=lz4
Hm, another strange thing's on another server -
zfs-stats -L
ZFS Subsystem ReportThu Oct 10 12:56:54 2013
L2 ARC
On 2013-10-10 05:22, Vitalij Satanivskij wrote:
Same situation hapend yesterday again :(
What's confuse me while trying to understend where I'm wrong
Firt some info.
We have zfs pool POOL and one more zfs on it POOL/zfs
POOL - have only primarycache enabled ALL
POOL/zfs - have both
AJ Some background on L2ARC compression for you:
AJ
AJ http://wiki.illumos.org/display/illumos/L2ARC+Compression
I'm alredy see it.
AJ http://svnweb.freebsd.org/base?view=revisionrevision=251478
AJ
AJ Are you sure that compression on pool/zfs is off? it would normally
AJ inherit from the
On Mon, Oct 7, 2013, at 13:09, Dmitriy Makarov wrote:
How can L2 ARC Size: (Adaptive) be 1.44 TiB (up) with total physical size
of L2ARC devices 490GB?
http://svnweb.freebsd.org/base?view=revisionrevision=251478
L2ARC compression perhaps?
___
Data on pool have compressratio around 1.4
On diferent servers with same data type and load L2 ARC Size: (Adaptive) can be
diferent
for example 1.04TiB vs 1.45TiB
But it's all have same porblem - grow in time.
More stange for us -
ARC: 80G Total, 4412M MFU, 5040M MRU, 76M
One more question -
we have two counter -
kstat.zfs.misc.arcstats.l2_size: 1256609410560
kstat.zfs.misc.arcstats.l2_asize: 1149007667712
can anybody explain how to understand them i.e. l2_asize - real used space on
l2arc an l2_size - uncompressed size,
or maybe something else ?
Vitalij
17 matches
Mail list logo
