Re: Regarding zfs send / receive

sounds like a good idea, I might look into that, thnx. Terje: zpool.cache is only 860 bytes, I don't think that should cause any problems (?) -- -- Joar Jegleim Homepage: http://cosmicb.no Linkedin: http://no.linkedin.com/in/joarjegleim fb: http://www.faceboo

Re: Regarding zfs send / receive

the one I'm using . In fact, I'm gonna take a closer look at that script and see what differs from my script (apart from it being much prettier :p ) I didn't know about zpool.cache, gonna check that tomorrow, thanks. -- -- Joar Jegleim Homepage: http://cosmicb

Regarding zfs send / receive

Hi FreeBSD ! So I've got this setup where we have a storage server delivering about 2 million jpeg's as a backend for a website ( it's ~1TB of data) The storage server is running zfs and every 15 minutes it does a zfs send to a 'slave', and our proxy will fail over to the slave if the main storage

Re: 3 TB disk troubles

B, I think the 'problem' was OS agnostic, since the same happened on my girlfriends mac. regards Joar Jegleim On 14 February 2013 12:16, Scott Bennett wrote: > I recently bought a 3 TB external hard drive. I attached it to the > Firewire (400) bus and waited for my

Re: regarding carp and nginx

ntil the passive node takes over I could live with that, but if I've configured something wrong or missing some important part I need to make the failover seamless I have to make this right :p -- -- Joar Jegleim Homepage: http://cosmicb.no Linkedin: http://no.linkedin.c

regarding carp and nginx

I've set the following in sysctl.conf #Accept incoming CARP packets. Enabled by default. net.inet.carp.allow=1 #This option downs all of the CARP interfaces on the host when one of them goes down. Disabled by default net.inet.carp.preempt=1 #A value of 0 disables any logging. A Value of 1 enables logging o