d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
170,846 Commits 4 Branches 49 Tags
Commit Graph

14 Commits

Author SHA1 Message Date
pjd
337b50efa8 Allow to compress on-the-wire data using two algorithms: 
- HOLE - it simply turns all-zero blocks into few bytes header;
	it is extremely fast, so it is turned on by default;
	it is mostly intended to speed up initial synchronization
	where we expect many zeros;
- LZF - very fast algorithm by Marc Alexander Lehmann, which shows
	very decent compression ratio and has BSD license.

MFC after:	2 weeks
 2011-03-06 23:09:33 +00:00
pjd
f56b79fee1 Allow to checksum on-the-wire data using either CRC32 or SHA256. 
MFC after:	2 weeks
 2011-03-06 22:56:14 +00:00
pjd
d2daebca5a Setup another socketpair between parent and child, so that primary sandboxed 
worker can ask the main privileged process to connect in worker's behalf
and then we can migrate descriptor using this socketpair to worker.
This is not really needed now, but will be needed once we start to use
capsicum for sandboxing.

MFC after:	1 week
 2011-02-03 11:39:49 +00:00
pjd
6c89103e58 Remember created control connection so on fork(2) we can close it in child. 
Found with:	procstat(1)
MFC after:	1 week
 2011-01-27 19:33:57 +00:00
pjd
b9551ad06f Don't open configuration file from worker process. Handle SIGHUP in the 
master process only and pass changes to the worker processes over control
socket. This removes access to global namespace in preparation for capsicum
sandboxing.

MFC after:	2 weeks
 2011-01-24 15:04:15 +00:00
pjd
376c59ffe9 Add missing logs. 
MFC after:	1 week
 2011-01-22 23:30:01 +00:00
pjd
e3b328c442 Use int16 for error. 
MFC after:	1 week
 2011-01-22 22:33:27 +00:00
pjd
322c5f284c We close the event socketpair early in the mainloop to prevent spaming with 
error messages, so when we clean up after child process, we have to check if
the event socketpair is still there.

Submitted by:	Mikolaj Golub <to.my.trociny@gmail.com>
MFC after:	3 days
 2010-10-08 15:02:15 +00:00
pjd
3657e3ff87 Fix descriptor leaks: when child exits, we have to close control and event 
socket pairs. We did that only in one case out of three.

MFC after:	3 days
 2010-09-22 18:57:06 +00:00
pjd
33133813bc If we are unable to receive control message is most likely because the main 
process died. Instead of entering infinite loop, terminate.

MFC after:	3 days
 2010-09-22 18:39:43 +00:00
pjd
e7991e6689 Sort includes. 
MFC after:	3 days
 2010-09-22 18:38:02 +00:00
pjd
1d4a51dd2d - Call hook on role change. 
- Document new event.

MFC after:	2 weeks
Obtained from:	Wheel Systems Sp. z o.o. http://www.wheelsystems.com
 2010-08-29 21:42:45 +00:00
pjd
31021ec9f1 Make control_set_role() more public. We will need it soon. 
MFC after:	1 month
 2010-08-05 19:04:29 +00:00
pjd
1c1e2e8b71 Please welcome HAST - Highly Avalable Storage. 
HAST allows to transparently store data on two physically separated machines
connected over the TCP/IP network. HAST works in Primary-Secondary
(Master-Backup, Master-Slave) configuration, which means that only one of the
cluster nodes can be active at any given time. Only Primary node is able to
handle I/O requests to HAST-managed devices. Currently HAST is limited to two
cluster nodes in total.

HAST operates on block level - it provides disk-like devices in /dev/hast/
directory for use by file systems and/or applications. Working on block level
makes it transparent for file systems and applications. There in no difference
between using HAST-provided device and raw disk, partition, etc. All of them
are just regular GEOM providers in FreeBSD.

For more information please consult hastd(8), hastctl(8) and hast.conf(5)
manual pages, as well as http://wiki.FreeBSD.org/HAST.

Sponsored by:	FreeBSD Foundation
Sponsored by:	OMCnet Internet Service GmbH
Sponsored by:	TransIP BV
 2010-02-18 23:16:19 +00:00