| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
with geometry. And they do recalculation of user specified parameters.
MBR, PC98, VTOC8, EBR schemes are doing that. For these schemes an
auto alignment feature (ie. gpart add -a alignment) would not work.
But it can work for GPT and BSD schemes. BSD scheme usualy is created
inside MBR, so we can use knowledge about offset of MBR partition to
calculate aligned values for BSD partitions.
Use "offset" attribute of the parent provider for better alignment.
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
clear the options of the current media, i.e. only inherit the instance,
which matches what NetBSD does. Without this it's really non-intuitive
that the following sequence:
ifconfig bge0 media 1000baseT mediaopt full-duplex
ifconfig bge0 media 100baseTX
results in 100baseTX full-duplex to be set or that:
ifconfig bge0 media autoselect mediaopt flowcontrol
ifconfig bge0 media 1000baseT mediaopt full-duplex
tries to set 1000baseT full-duplex with flowcontrol, which isn't suported
und thus fails while the following:
ifconfig re0 media 1000baseT mediaopt flowcontrol,full-duplex
ifconfig re0 media autoselect
just switches to autoselection without flowcontrol.
MFC after: 2 weeks
|
|
|
|
|
|
| |
"start" and "end" config attributes.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
because we need to do ioctl(2)s, which are not permitted in the capability
mode. What we do now is to chroot(2) to /var/empty, which restricts access
to file system name space and we drop privileges to hast user and hast
group.
This still allows to access to other name spaces, like list of processes,
network and sysvipc.
To address that, use jail(2) instead of chroot(2). Using jail(2) will restrict
access to process table, network (we use ip-less jails) and sysvipc (if
security.jail.sysvipc_allowed is turned off). This provides much better
separation.
MFC after: 1 week
|
|
|
|
| |
one of them have some problems.
|
|
|
|
| |
See sys/dev/usb/usb_device.c for what devctl_notify() gets.
|
|
|
|
|
|
|
|
| |
operate on one type of filesystem, mention this.
While here, capitalise the use of "UFS" in growfs.8 to match other uses of
the term in other man pages.
MFC after: 1 week
|
|
|
|
|
|
|
| |
'none' was defined as a value for checksum.
Reported by: trasz
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
kern.geom.eli.version
kern.geom.eli.key_cache_limit
kern.geom.eli.key_cache_hits
kern.geom.eli.key_cache_misses
MFC after: 1 week
|
|
|
|
|
|
|
| |
belongs to our node, and was returning false positive if the first
part of a node name matches short hostname.
Approved by: pjd (mentor)
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
|
| |
tries to align partition start offset and size to be multiple of
alignment value.
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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]
|
|
|
|
| |
link for mount_oldnfs.8 instead of mount_newnfs.8.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
"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
|
|
|
|
|
|
|
| |
NFS clients done by r221124.
This is a content change.
Submitted by: jh
|
|
|
|
|
|
| |
applied by r221124. I also deleted references to idmapd, since that
daemon no longer exists.
This is a content change.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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@.
|
|
|
|
| |
MFC after: 3 weeks
|
|
|
|
| |
MFC after: 3 weeks
|
|
|
|
| |
MFC after: 3 weeks
|
|
|
|
|
|
| |
Reported by: Pawel Tyll <ptyll@nitronet.pl>
Approved by: pjd (mentor)
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
defines.
Approved by: pjd (mentor)
MFC after: 1 week
|
|
|
|
| |
Approved by: pjd (mentor)
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
Changing the size of struct ieee80211_mimo_info changes
the STA info data, breaking ifconfig in general.
|
|
|
|
|
|
| |
extended EVM statistics and EXT channel data.
ifconfig still displays 3 chains worth of ctl noise/rssi.
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
as a warning and not an error.
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
| |
release device. We haven't frozen the device before and attempt to release
it will at least cause warning message from kernel.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- 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
|
|
|
|
|
|
| |
calculated dynamically.
PR: kern/143653
|
|
|
|
|
|
| |
This should preserve POLA in all other cases (foreground || non-dynamic).
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Checked with: md5, diff -x -w
|
|
|
|
| |
Checked with: md5, diff -w
|
|
|
|
|
|
|
| |
console device as an argument. Unsetting virtual console
using /dev/console seems to have never worked.
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
Reviewed by: uqs
MFC after: 5 days
|
|
|
|
|
|
|
| |
Correct this and print a warning if different replication mode is
configured.
MFC after: 1 week
|
|
|
|
|
|
|
| |
later in hast_proto_recv_data().
Approved by: pjd (mentor)
MFC after: 1 week
|
|
|
|
|
|
|
| |
received does not exceed the buffer size.
Approved by: pjd (mentor)
MFC after: 1 week
|
|
|
|
|
| |
Approved by: pjd (mentor)
MFC after: 3 days
|