summaryrefslogtreecommitdiffstats
path: root/sbin/hastd
Commit message (Collapse)AuthorAgeFilesLines
* Check remote protocol version only for the first connection (when ittrociny2013-12-101-6/+6
| | | | | | | | | is actually sent by the remote node). Otherwise it generated confusing "Negotiated protocol version 1" debug messages when processing the second connection. MFC after: 2 weeks
* Send wakeup to threads waiting on empty queue before releasing thetrociny2013-12-102-16/+7
| | | | | | | lock to decrease spurious wakeups. Submitted by: davidxu MFC after: 2 weeks
* In remote_send_thread, if sending a request fails don't take thetrociny2013-12-101-11/+2
| | | | | | | | | | | | | | | | | | request back from the receive queue -- it might already be processed by remote_recv_thread, which lead to crashes like below: (primary) Unable to receive reply header: Connection reset by peer. (primary) Unable to send request (Connection reset by peer): WRITE(954662912, 131072). (primary) Disconnected from kopusha:7772. (primary) Increasing localcnt to 1. (primary) Assertion failed: (old > 0), function refcnt_release, file refcnt.h, line 62. Taking the request back was not necessary (it would properly be processed by the remote_recv_thread) and only complicated things. MFC after: 2 weeks
* Fix compiler warnings.trociny2013-12-102-4/+4
| | | | MFC after: 2 weeks
* Add some macros to make the code more readable (no functional chages).trociny2013-12-101-6/+9
| | | | MFC after: 2 weeks
* For memsync replication, hio_countdown is used not only as antrociny2013-12-101-111/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | indication when a request can be moved to done queue, but also for detecting the current state of memsync request. This approach has problems, e.g. leaking a request if memsynk ack from the secondary failed, or racy usage of write_complete, which should be called only once per write request, but for memsync can be entered by local_send_thread and ggate_send_thread simultaneously. So the following approach is implemented instead: 1) Use hio_countdown only for counting components we waiting to complete, i.e. initially it is always 2 for any replication mode. 2) To distinguish between "memsync ack" and "memsync fin" responses from the secondary, add and use hio_memsyncacked field. 3) write_complete() in component threads is called only before releasing hio_countdown (i.e. before the hio may be returned to the done queue). 4) Add and use hio_writecount refcounter to detect when write_complete() can be called in memsync case. Reported by: Pete French petefrench ingresso.co.uk Tested by: Pete French petefrench ingresso.co.uk MFC after: 2 weeks
* Correct alignment.pjd2013-11-031-1/+1
|
* Make hastctl list command output current queue sizes.trociny2013-10-264-1/+85
| | | | | Reviewed by: pjd MFC after: 1 month
* Merging local and remote bitmaps must be protected by hr_amp lock.trociny2013-10-261-1/+1
| | | | | | | | | | This is believed to fix hastd crashes, which might occur during synchronization, triggered by the failed assertion: Assertion failed: (amp->am_memtab[ext] > 0), function activemap_write_complete, file activemap.c, line 351. MFC after: 1 week
* Fix comments.trociny2013-09-191-3/+2
| | | | | Approved by: re (marius) MFC after: 3 days
* When updating the map of dirty extents, most recently used extents aretrociny2013-09-192-9/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | kept dirty to reduce the number of on-disk metadata updates. The sequence of operations is: 1) acquire the activemap lock; 2) update in-memory map; 3) if the list of keepdirty extents is changed, update on-disk metadata; 4) release the lock. On-disk updates are not frequent in comparison with in-memory updates, while require much more time. So situations are possible when one thread is updating on-disk metadata and another one is waiting for the activemap lock just to update the in-memory map. Improve this by introducing additional, on-disk map lock: when in-memory map is updated and it is detected that the on-disk map needs update too, the on-disk map lock is acquired and the on-memory lock is released before flushing the map. Reported by: Yamagi Burmeister yamagi.org Tested by: Yamagi Burmeister yamagi.org Reviewed by: pjd Approved by: re (marius) MFC after: 2 weeks
* Use cv_broadcast() instead of cv_signal() when waking up threadstrociny2013-09-192-3/+3
| | | | | | | | | | | | | | | | | | | | waiting on an empty queue as the queue may have several consumers. Before the fix the following scenario was possible: 2 threads are waiting on empty queue, 2 threads are inserting simultaneously. The first inserting thread detects that the queue is empty and is going to send the signal, but before it sends the second thread inserts too. When the first sends the signal only one of the waiting threads receive it while the other one may wait forever. The scenario above is is believed to be the cause of the observed cases, when ggate_recv_thread() was getting stuck on taking free request, while the free queue was not empty. Reviewed by: pjd Tested by: Yamagi Burmeister yamagi.org Approved by: re (marius) MFC after: 2 weeks
* Change the cap_rights_t type from uint64_t to a structure that we can extendpjd2013-09-051-3/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | in the future in a backward compatible (API and ABI) way. The cap_rights_t represents capability rights. We used to use one bit to represent one right, but we are running out of spare bits. Currently the new structure provides place for 114 rights (so 50 more than the previous cap_rights_t), but it is possible to grow the structure to hold at least 285 rights, although we can make it even larger if 285 rights won't be enough. The structure definition looks like this: struct cap_rights { uint64_t cr_rights[CAP_RIGHTS_VERSION + 2]; }; The initial CAP_RIGHTS_VERSION is 0. The top two bits in the first element of the cr_rights[] array contain total number of elements in the array - 2. This means if those two bits are equal to 0, we have 2 array elements. The top two bits in all remaining array elements should be 0. The next five bits in all array elements contain array index. Only one bit is used and bit position in this five-bits range defines array index. This means there can be at most five array elements in the future. To define new right the CAPRIGHT() macro must be used. The macro takes two arguments - an array index and a bit to set, eg. #define CAP_PDKILL CAPRIGHT(1, 0x0000000000000800ULL) We still support aliases that combine few rights, but the rights have to belong to the same array element, eg: #define CAP_LOOKUP CAPRIGHT(0, 0x0000000000000400ULL) #define CAP_FCHMOD CAPRIGHT(0, 0x0000000000002000ULL) #define CAP_FCHMODAT (CAP_FCHMOD | CAP_LOOKUP) There is new API to manage the new cap_rights_t structure: cap_rights_t *cap_rights_init(cap_rights_t *rights, ...); void cap_rights_set(cap_rights_t *rights, ...); void cap_rights_clear(cap_rights_t *rights, ...); bool cap_rights_is_set(const cap_rights_t *rights, ...); bool cap_rights_is_valid(const cap_rights_t *rights); void cap_rights_merge(cap_rights_t *dst, const cap_rights_t *src); void cap_rights_remove(cap_rights_t *dst, const cap_rights_t *src); bool cap_rights_contains(const cap_rights_t *big, const cap_rights_t *little); Capability rights to the cap_rights_init(), cap_rights_set(), cap_rights_clear() and cap_rights_is_set() functions are provided by separating them with commas, eg: cap_rights_t rights; cap_rights_init(&rights, CAP_READ, CAP_WRITE, CAP_FSTAT); There is no need to terminate the list of rights, as those functions are actually macros that take care of the termination, eg: #define cap_rights_set(rights, ...) \ __cap_rights_set((rights), __VA_ARGS__, 0ULL) void __cap_rights_set(cap_rights_t *rights, ...); Thanks to using one bit as an array index we can assert in those functions that there are no two rights belonging to different array elements provided together. For example this is illegal and will be detected, because CAP_LOOKUP belongs to element 0 and CAP_PDKILL to element 1: cap_rights_init(&rights, CAP_LOOKUP | CAP_PDKILL); Providing several rights that belongs to the same array's element this way is correct, but is not advised. It should only be used for aliases definition. This commit also breaks compatibility with some existing Capsicum system calls, but I see no other way to do that. This should be fine as Capsicum is still experimental and this change is not going to 9.x. Sponsored by: The FreeBSD Foundation
* Make hastctl(1) ('list' command) output a worker pid.trociny2013-07-011-0/+1
| | | | | Reviewed by: pjd MFC after: 3 days
* Correct some grammar.schweikh2013-06-301-18/+18
|
* Don't let hastd use C11 atomics.ed2013-06-291-5/+5
| | | | | | | Due to possible concerns about the stability of C11 atomics, use our existing atomics API instead. Requested by: pjd
* Let hastd use C11 atomics.ed2013-06-151-5/+5
| | | | | | | C11 atomics now work on all the architectures. Have at least a single piece of software in our base system that uses C11 atomics. This somewhat makes it less likely that we break it because of LLVM imports, etc.
* Improve compatibility with old flex and fix build with GCC.jkim2013-05-223-3/+5
|
* Get rid of libl dependency. We needed it only to provide yywrap. Buttrociny2013-05-112-1/+2
| | | | | | | yywrap is not necessary when parsing a single hast.conf file. Suggested by: kib Reviewed by: pjd
* Partially revert my last change.ed2013-04-271-5/+5
| | | | | I forgot that I still had a locally applied patch to my copy of Clang that needs to be pushed in before we should use C11 atomics.
* Use C11 <stdatomic.h> instead of our non-standard <machine/atomic.h>.ed2013-04-272-11/+21
| | | | Reviewed by: pjd
* Add the Clang specific -Wmissing-variable-declarations to WARNS=6.ed2013-04-191-0/+1
| | | | | | | | | | | | | This compiler flag enforces that that people either mark variables static or use an external declarations for the variable, similar to how -Wmissing-prototypes works for functions. Due to the fact that Yacc/Lex generate code that cannot trivially be changed to not warn because of this (lots of yy* variables), add a NO_WMISSING_VARIABLE_DECLARATIONS that can be used to turn off this specific compiler warning. Announced on: toolchain@
* Now that ioctl(2) is allowed in capability mode and we can limit ioctls for thepjd2013-03-141-16/+48
| | | | | | | | | given descriptors, use Capsicum sandboxing for hastd in primary and secondary modes. Allow for DIOCGDELETE and DIOCGFLUSH ioctls on provider descriptor and for G_GATE_CMD_MODIFY, G_GATE_CMD_START, G_GATE_CMD_DONE and G_GATE_CMD_DESTROY on GEOM Gate descriptor. Sponsored by: The FreeBSD Foundation
* Minor corrections.pjd2013-03-141-4/+4
|
* Delete requests can be larger than MAXPHYS.pjd2013-03-141-1/+1
|
* Add i/o error counters to hastd(8) and make hastctl(8) displaytrociny2013-02-254-1/+65
| | | | | | | them. This may be useful for detecting problems with HAST disks. Discussed with and reviewed by: pjd MFC after: 1 week
* - Add support for 'memsync' mode. This is the fastest replication mode that'spjd2013-02-178-43/+334
| | | | | | | | | | why it will now be the default. - Bump protocol version to 2 and add backward compatibility for version 1. - Allow to specify hosts by kern.hostid as well (in addition to hostname and kern.hostuuid) in configuration file. Sponsored by: Panzura Tested by: trociny
* Fix socket calls on error post-r243965.kevlo2012-12-211-1/+1
| | | | Submitted by: Garrett Cooper
* Revert r228695. We use __func__ here as a format to distinguish betweenpjd2012-11-051-1/+1
| | | | | abort and assert. It would be cleaner to use NULL or "" here, but gcc complains in both cases.
* Metaflush on/off values don't need quotes.trociny2012-07-161-4/+4
| | | | | Reviewed by: pjd MFC after: 3 days
* Make use of GEOM Gate direct reads feature. This allows HAST to servepjd2012-07-041-1/+31
| | | | | | | | | | | | | | reads with native speed of the underlying provider. There are three situations when direct reads are not used: 1. Data is being synchronized and synchronization source is the secondary node, which means secondary node has more recent data and we should read from it. 2. Local read failed and we have to try to read from the secondary node. 3. Local component is unavailable and all I/O requests are served from the secondary node. Sponsored by: Panzura, http://www.panzura.com MFC after: 1 month
* Check if there is cmsg at all.pjd2012-07-011-1/+1
| | | | MFC after: 3 days
* Revert: r236909hselasky2012-06-111-1/+1
| | | | Pointyhat: me
* Use the correct clock source when computing timeouts.hselasky2012-06-111-1/+1
| | | | MFC after: 1 week
* Simplify the code by using snprlcat().pjd2012-06-031-27/+24
| | | | MFC after: 3 days
* Fixes to man8 groff mandoc style, usage mistakes, or typos.wblock2012-05-241-1/+1
| | | | | | | PR: 168016 Submitted by: Nobuyuki Koganemaru Approved by: gjb MFC after: 3 days
* Fix world after byacc import:bapt2012-05-222-291/+296
| | | | | | | | - old yacc(1) use to magicially append stdlib.h, while new one don't - new yacc(1) do declare yyparse by itself, fix redundant declaration of 'yyparse' Approved by: des (mentor)
* General mdoc(7) and typo fixes.gjb2012-05-121-2/+2
| | | | | | PR: 167804 Submitted by: Nobuyuki Koganemaru (kogane!jp.freebsd.org) MFC after: 3 days
* If hastd is invoked with "-P pidfile" option always create pidfiletrociny2012-03-291-5/+7
| | | | | | | | | | | regardless of whether -F (foreground) option is set or not. Also, if -P option is specified, ignore pidfile setting from configuration not only on start but on reload too. This fixes the issue when for hastd run with -P option reload caused the pidfile change. Reviewed by: pjd MFC after: 1 week
* Fix typo.trociny2012-03-231-7/+7
| | | | MFC after: 3 days
* Nice range comparison.pjd2012-02-111-5/+3
| | | | MFC after: 3 days
* If a local write request is from the synchronization thread, when ittrociny2012-02-051-1/+2
| | | | | | | | | | | | | is synchronizing data that is out of date on the local component, we should not send G_GATE_CMD_DONE acknowledge to the kernel. This fixes the issue, observed in async mode, when on synchronization from the remote component the worker terminated with "G_GATE_CMD_DONE failed" error. Reported by: Artem Kajalainen <artem kayalaynen ru> Reviewed by: pjd MFC after: 1 week
* Fix the regression introduced in r226859: if the local component istrociny2012-02-051-1/+1
| | | | | | | | out of date BIO_READ requests got lost instead of being sent to the remote component. Reviewed by: pjd MFC after: 1 week
* Fix typo in comment.pjd2012-02-041-1/+1
| | | | MFC after: 3 days
* - Fix documentation to note that /etc/hast.conf is the default configurationpjd2012-01-241-4/+6
| | | | | | | | file for hastd(8) and hastctl(8) and not hast.conf. - In copyright statement correct that this file is documentation, not software. - Bump date. MFC after: 3 days
* Free memory that won't be used in child.pjd2012-01-221-3/+7
| | | | MFC after: 1 week
* Fix minor memory leak.pjd2012-01-211-0/+1
| | | | MFC after: 3 days
* Remove another unused token.pjd2012-01-201-1/+1
| | | | MFC after: 3 days
* Remove unused token 'port'.pjd2012-01-202-2/+1
| | | | MFC after: 3 days
* Style cleanups.pjd2012-01-131-6/+11
| | | | MFC after: 3 days
OpenPOWER on IntegriCloud