summaryrefslogtreecommitdiffstats
path: root/sbin
Commit message (Collapse)AuthorAgeFilesLines
* Implemented a mount option "nocto" that disables cache coherencyru2011-05-041-1/+12
| | | | | | | | checking at open time. It may improve performance for read-only NFS mounts. Use deliberately. MFC after: 1 week Reviewed by: rmacklem, jhb (earlier version)
* Add "-a alignment" option to gpart(8). When it specified gpart(8)ae2011-05-032-27/+99
| | | | | | | tries to align partition start offset and size to be multiple of alignment value. MFC after: 2 weeks
* recoverdisk(8): treat output file consistently and abort on EINVALuqs2011-05-012-26/+42
| | | | | | | | | | | | | | | This improves usability a little as we no longer require using touch. Also reword the manpage wrt. parameters and fix usage() [1] With no media in a cd(4) drive, the reads will loop producing EINVAL, abort in that case [2]. Document the shortcoming of sectorsize and MAXPHYS (a quick solution to this might be having MAXPHYS as the "bigsize", in short testing it didn't make a difference on throughput). Submitted by: arundel [1] PR: bin/154528 [2]
* Fix the Makefile for mount_nfs so that it creates armacklem2011-05-011-1/+1
| | | | link for mount_oldnfs.8 instead of mount_newnfs.8.
* Add an -E option to mirror newfs's. The idea is that if you have a systemdes2011-04-295-7/+67
| | | | | | | | | | | | | | | | | | | that was built before ffs grew support for TRIM, your filesystem will have plenty of free blocks that the flash chip doesn't know are free, so it can't take advantage of them for wear leveling. Once you've upgraded your kernel, you enable TRIM on the filesystem (tunefs -t enable), then run fsck_ffs -E on it before mounting it. I tested this patch by half-filling an mdconfig'ed filesystem image, running fsck_ffs -E on it, then verifying that the contents were not damaged by comparing them to a pristine copy using rsync's checksum functionality. There is no reliable way to test it on real hardware. Many thanks to mckusick@, who provided the tricky parts of this patch and reviewed the final version. Reviewed by: mckusick@ MFC after: 3 weeks
* Somewhere around the 473rd time I mistyped "mdconfig file" instead ofdes2011-04-292-20/+49
| | | | | | | "mdconfig -f file", I decided that it would be easier to make mdconfig DWIM than to teach my fingers to type the correct command line. MFC after: 3 weeks
* Another man page update related to the switchover of thermacklem2011-04-291-2/+2
| | | | | | | NFS clients done by r221124. This is a content change. Submitted by: jh
* Update man pages related to the change in default NFS clientrmacklem2011-04-281-4/+8
| | | | | | applied by r221124. I also deleted references to idmapd, since that daemon no longer exists. This is a content change.
* whitespace nit - sorry for the churndes2011-04-271-2/+2
|
* whitespace nitdes2011-04-271-1/+1
|
* This patch changes head so that the default NFS client is now the newrmacklem2011-04-273-11/+7
| | | | | | | | | | | | | | NFS client (which I guess is no longer experimental). The fstype "newnfs" is now "nfs" and the regular/old NFS client is now fstype "oldnfs". Although mounts via fstype "nfs" will usually work without userland changes, an updated mount_nfs(8) binary is needed for kernels built with "options NFSCL" but not "options NFSCLIENT". Updated mount_nfs(8) and mount(8) binaries are needed to do mounts for fstype "oldnfs". The GENERIC kernel configs have been changed to use options NFSCL and NFSD (the new client and server) instead of NFSCLIENT and NFSSERVER. For kernels being used on diskless NFS root systems, "options NFSCL" must be in the kernel config. Discussed on freebsd-fs@.
* Mechanical whitespace cleanup.des2011-04-276-36/+35
| | | | MFC after: 3 weeks
* Fix boo-boo in previous commit.des2011-04-271-7/+7
| | | | MFC after: 3 weeks
* Alphabetize the options. No date bump since no actual change to the text.des2011-04-271-4/+4
| | | | MFC after: 3 weeks
* Add missing ifdef. This fixes build with NO_OPENSSL.trociny2011-04-261-0/+2
| | | | | | Reported by: Pawel Tyll <ptyll@nitronet.pl> Approved by: pjd (mentor) MFC after: 1 week
* Rename HASTCTL_ defines, which are used for conversion between maintrociny2011-04-263-7/+6
| | | | | | | | | | hastd process and workers, remove unused one and set different range of numbers. This is done in order not to confuse them with HASTCTL_CMD defines, used for conversation between hastctl and hastd, and to avoid bugs like the one fixed in in r221075. Approved by: pjd (mentor) MFC after: 1 week
* For conversation between hastctl and hastd we should use HASTCTL_CMDtrociny2011-04-261-5/+5
| | | | | | | defines. Approved by: pjd (mentor) MFC after: 1 week
* Fix assert messages.trociny2011-04-261-2/+2
| | | | Approved by: pjd (mentor)
* Stop trying to zero UFS1 superblocks if we fall off the end of the disk.cperciva2011-04-261-1/+4
| | | | | | | | | | This avoids a potentially many-hours-long loop of failed writes if newfs finds a partially-overwritten superblock (or, for that matter, random garbage which happens to have superblock magic bytes); on one occasion I found newfs trying to zero 800 million superblocks on a 50 MB disk. Reviewed by: mckusick MFC after: 1 week
* Revert r220907 and r220915.adrian2011-04-221-5/+3
| | | | | Changing the size of struct ieee80211_mimo_info changes the STA info data, breaking ifconfig in general.
* Change the MIMO userland export ABI to include flags, number of radio chains,adrian2011-04-211-3/+5
| | | | | | extended EVM statistics and EXT channel data. ifconfig still displays 3 chains worth of ctl noise/rssi.
* Correct comment.pjd2011-04-201-1/+1
| | | | MFC after: 1 week
* When we become primary, we connect to the remote and expect it to be inpjd2011-04-202-13/+56
| | | | | | | | | | secondary role. It is possible that the remote node is primary, but only because there was a role change and it didn't finish cleaning up (unmounting file systems, etc.). If we detect such situation, wait for the remote node to switch the role to secondary before accepting I/Os. If we don't wait for it in that case, we will most likely cause split-brain. MFC after: 1 week
* If we act in different role than requested by the remote node, log itpjd2011-04-201-1/+1
| | | | | | as a warning and not an error. MFC after: 1 week
* Timeout must be positive.pjd2011-04-201-0/+4
| | | | MFC after: 1 week
* When calling XPT_REL_SIMQ to ajust number of openings, do not try to reallymav2011-04-201-0/+1
| | | | | release device. We haven't frozen the device before and attempt to release it will at least cause warning message from kernel.
* Scenario:pjd2011-04-192-0/+20
| | | | | | | | | | | | | | | | | | | - We have two nodes connected and synchronized (local counters on both sides are 0). - We take secondary down and recreate it. - Primary connects to it and starts synchronization (but local counters are still 0). - We switch the roles. - Synchronization restarts but data is synchronized now from new primary (because local counters are 0) that doesn't have new data yet. This fix this issue we bump local counter on primary when we discover that connected secondary was recreated and has no data yet. Reported by: trociny Discussed with: trociny Tested by: trociny MFC after: 1 week
* Rewrite NAT configuration parser, so that memory allocation size isglebius2011-04-191-186/+189
| | | | | | calculated dynamically. PR: kern/143653
* Furthermore condition IP waiting behaviour also on -dynamic flag.sobomax2011-04-181-4/+8
| | | | | | This should preserve POLA in all other cases (foreground || non-dynamic). MFC after: 2 weeks
* Only wait for the IP to appear on the interface if natd is running in thesobomax2011-04-181-5/+5
| | | | | | | | | | | background. Suggested by: Garrett Cooper <yanegomi@gmail.com> Use EAGAIN instead of magic value of -2 to report this condition from the SetAliasAddressFromIfName routine. MFC after: 2 weeks
* More whitespace fixes.glebius2011-04-184-41/+41
| | | | Checked with: md5, diff -x -w
* Whitespace fixes.glebius2011-04-186-268/+266
| | | | Checked with: md5, diff -w
* Changed "conscontrol unset" to accept an existing virtualru2011-04-182-24/+12
| | | | | | | console device as an argument. Unsetting virtual console using /dev/console seems to have never worked. MFC after: 3 days
* Remove hast_proto_recv(). It was used only in one place, wheretrociny2011-04-173-21/+1
| | | | | | | | hast_proto_recv_hdr() may be used. This also fixes the issue (introduced by r220523) with hastctl, which crashed on assert in hast_proto_recv_data(). Suggested and approved by: pjd (mentor)
* If we can retrieve interface address sleep for one second and try again.sobomax2011-04-171-9/+29
| | | | | | | This can happen during start-up, when natd starts before dhclient has a chance to receive IP address from the upstream provider. MFC after: 2 weeks
* Remove vestiges of disklabel(5).pluknet2011-04-141-3/+1
| | | | | Reviewed by: uqs MFC after: 5 days
* The replication mode that is currently support is fullsync, not memsync.pjd2011-04-121-1/+8
| | | | | | | Correct this and print a warning if different replication mode is configured. MFC after: 1 week
* In hast_proto_recv() remove unnecessary check. The size is checkedtrociny2011-04-101-6/+1
| | | | | | | later in hast_proto_recv_data(). Approved by: pjd (mentor) MFC after: 1 week
* In hast_proto_recv_data() check that the size of the data to betrociny2011-04-101-2/+5
| | | | | | | received does not exceed the buffer size. Approved by: pjd (mentor) MFC after: 1 week
* Fix a typo in comments.trociny2011-04-101-1/+1
| | | | | Approved by: pjd (mentor) MFC after: 3 days
* hastd(8) maintains a map of dirty extents, not hastctl(8). Fix this.trociny2011-04-101-2/+2
| | | | | Approved by: pjd (mentor) MFC after: 3 days
* Correct 'list scan' description in the examples. The previous descriptiongjb2011-04-061-1/+1
| | | | | | | | | was incorrect - 'list scan' does not actually do a scan, but instead lists the results of the background 'scan' cache. Submitted by: Fabian Keil (freebsd-listen of fabiankeil de) (via email) Discussed with: bschmidt MFC after: 3 days
* * Add the readline(3) API to libedit. The libedit versions ofobrien2011-04-052-3/+4
| | | | | | | | | | | | | | | | {readline,history}.h are in /usr/include/edit so as to not conflict with the GNU libreadline versions. To use the libedit readline(3) one should add "-I/usr/include/edit" to their Makefile (spelled "-I${DESTDIR}/${INCLUDEDIR}/edit" within the FreeBSD source tree). * Enable its use in the BSD licensed utilities that support readline(3). * To make it easier to sync libedit development with NetBSD, histedit.h is moved into libedit's directory as history shows shown we keep merging it into that location. Obtained from: NetBSD Sponsored by: Juniper Networks
* Increase default timeout from 5 seconds to 20 seconds. 5 seconds is definitelypjd2011-04-022-3/+3
| | | | | | | to short under heavy load and I was experiencing those timeouts in my recent tests. MFC after: 1 week
* Handle ENOBUFS on send(2) by retrying for a while and logging the problem.pjd2011-04-021-0/+22
| | | | MFC after: 1 week
* When we are operating on blocking socket and get EAGAIN on send(2) or recv(2)pjd2011-04-021-4/+35
| | | | | | | | this means that request timed out. Translate the meaningless EAGAIN to ETIMEDOUT to give administrator a hint that he might need to increase timeout in configuration file. MFC after: 1 month
* Declare directions for sockets between primary and secondary.pjd2011-04-022-0/+12
| | | | | | | In HAST we use two sockets - one for only sending the data and one for only receiving the data. MFC after: 1 month
* Allow to disable sends or receives on a socket using shutdown(2) bypjd2011-04-021-0/+22
| | | | | | | interpreting NULL 'data' argument passed to proto_common_send() or proto_common_recv() as a will to do so. MFC after: 1 month
* Handle the problem described in r220264 by using GEOM GATE queue of unlimitedpjd2011-04-021-1/+1
| | | | | | length. This should fix deadlocks reported by HAST users. MFC after: 1 week
* Because ggatel(8) operates on local GEOM providers, use unlimited queue size inpjd2011-04-022-18/+4
| | | | | | GEOM GATE to fix the issue described in r220264. This also means that we no longer need -q option, remove it. Don't bother to leaving it as a no-op, as ggatel(8) is just an example utility.
OpenPOWER on IntegriCloud