Date: Mon, 16 Sep 2013 15:10:33 +0300 From: Dmitriy Makarov <supportme@ukr.net> To: Steven Hartland <killing@multiplay.co.uk> Cc: "Justin T. Gibbs" <gibbs@freebsd.org>, freebsd-current@freebsd.org, Borja Marcos <borjam@sarenet.es> Subject: Re[2]: ZFS secondarycache on SSD problem on r255173 Message-ID: <1379333192.127359970.ma5jnbc5@fmst-6.ukr.net> In-Reply-To: <DEF92E3685F3411D9B605ACFBEA16D94@multiplay.co.uk> References: <1379069539.824504225.3b9xwugp@fmst-6.ukr.net> <EAD621124C1549208BD93D20657E1BD0@multiplay.co.uk> <74C1D072-77BB-4D6C-B78F-C8D2731FA0CF@sarenet.es> <DEF92E3685F3411D9B605ACFBEA16D94@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
There is no problem with ZIL devices, they reports ashift: 12
children[1]:
type: 'disk'
id: 1
guid: 6986664094649753344
path: '/dev/gpt/zil1'
phys_path: '/dev/gpt/zil1'
whole_disk: 1
metaslab_array: 67
metaslab_shift: 25
ashift: 12
asize: 4290248704
is_log: 1
create_txg: 22517
Problem with cache devices only, but in zdb output tere is nothing at all about them.
--- Исходное сообщение ---
От кого: "Steven Hartland" < killing@multiplay.co.uk >
Дата: 16 сентября 2013, 14:18:31
Cant say I've ever had a issue with gnop, but I haven't used it for
some time.
I did have a quick look over the weekend at your issue and it looks
to me like warning for the cache is a false positive, as the vdev
for cache doesn't report an ashift in zdb so could well be falling
back to a default value.
I couldn't reproduce the issue for log here, it just seems to work
for me, can you confirm what ashift is reported for your devices
using: zdb <pool>
Regards
Steve
----- Original Message -----
From: "Borja Marcos" <
---
Дмитрий Макаров
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1379333192.127359970.ma5jnbc5>