Date: Tue, 21 Jan 2014 15:46:09 +0100 From: Joar Jegleim <joar.jegleim@gmail.com> To: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: hast and zfs Message-ID: <CAFfb-hq4R-f7yNCbAGS9X8wW4FcYY8%2B_jyxsqRsPxcnkYtEA7g@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Hi list ! I've setup hast with zfs on 9.1-RELEASE-p10 I've got an lsi hba connected to an external sas hp msa that has 20 disks in it, same setup on both nodes. I've created a hast disk dev such as /dev/hast/disk1a, /dev/hast/disk1b etc... ( see attached hast.conf ) And built a zpool mirror accross the 20 disks. While setting up this, and testing, all looked pretty good, I've tried numerous failovers and so on. When I just switched over to this setup in production, it worked for about half an hour until the primary node got a zfs hang where zpool list hung and hastctl status hung completely . There was no output in dmesg nor /var/log/messages that said anything related to this (?) . The server serves some 3 000 000 jpegs for a site, I see anything from 50 to just above 1000 iops, though the average iops is bellow 100. It's completely random what pictures are being fetched at any time. Could there be some sysctls to tune related to this setup mabye ? Anybody using hast and zfs in production got any tip ? -- ---------------------- Joar Jegleim Homepage: http://cosmicb.no Linkedin: http://no.linkedin.com/in/joarjegleim fb: http://www.facebook.com/joar.jegleim AKA: CosmicB @Freenode ---------------------- [-- Attachment #2 --] checksum sha256 replication fullsync listen 192.168.77.11 #timeout 5 resource disk1a { on store01 { local /dev/da2 remote store02 } on store02 { local /dev/da2 remote store01 } } resource disk1b { on store01 { local /dev/da3 remote store02 } on store02 { local /dev/da3 remote store01 } } resource disk2a { on store01 { local /dev/da4 remote store02 } on store02 { local /dev/da4 remote store01 } } resource disk2b { on store01 { local /dev/da5 remote store02 } on store02 { local /dev/da5 remote store01 } } resource disk3a { on store01 { local /dev/da6 remote store02 } on store02 { local /dev/da6 remote store01 } } resource disk3b { on store01 { local /dev/da7 remote store02 } on store02 { local /dev/da7 remote store01 } } resource disk4a { on store01 { local /dev/da8 remote store02 } on store02 { local /dev/da8 remote store01 } } resource disk4b { on store01 { local /dev/da9 remote store02 } on store02 { local /dev/da9 remote store01 } } resource disk5a { on store01 { local /dev/da10 remote store02 } on store02 { local /dev/da10 remote store01 } } resource disk5b { on store01 { local /dev/da11 remote store02 } on store02 { local /dev/da11 remote store01 } } resource disk6a { on store01 { local /dev/da12 remote store02 } on store02 { local /dev/da12 remote store01 } } resource disk6b { on store01 { local /dev/da13 remote store02 } on store02 { local /dev/da13 remote store01 } } resource disk7a { on store01 { local /dev/da14 remote store02 } on store02 { local /dev/da14 remote store01 } } resource disk7b { on store01 { local /dev/da15 remote store02 } on store02 { local /dev/da15 remote store01 } } resource disk8a { on store01 { local /dev/da16 remote store02 } on store02 { local /dev/da16 remote store01 } } resource disk8b { on store01 { local /dev/da17 remote store02 } on store02 { local /dev/da17 remote store01 } } resource disk9a { on store01 { local /dev/da18 remote store02 } on store02 { local /dev/da18 remote store01 } } resource disk9b { on store01 { local /dev/da19 remote store02 } on store02 { local /dev/da19 remote store01 } } resource disk10a { on store01 { local /dev/da20 remote store02 } on store02 { local /dev/da20 remote store01 } } resource disk10b { on store01 { local /dev/da21 remote store02 } on store02 { local /dev/da21 remote store01 } }
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFfb-hq4R-f7yNCbAGS9X8wW4FcYY8%2B_jyxsqRsPxcnkYtEA7g>
