| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
device info structures as well as the fds[] array. This is a raw
version of the file, unmodified, to be used as a baseline.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1948 zpool list should show more detailed pool information
Display per-vdev information with "zpool list -v".
The added expandsize property has currently no value on FreeBSD.
This changeset allows adding expansion support to individual vdevs
in the future.
References:
https://www.illumos.org/issues/1948
Obtained from: illumos (issue #1948)
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
| |
763 FMD msg URLs should refer to something visible
Replace sun.com URL's with illumos.org
References:
https://www.illumos.org/issues/763
Obtained from: illumos (issue #763)
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
| |
1946 incorrect formatting when listing output of multiple pools with
zpool iostat -v
References:
https://www.illumos.org/issues/1946
Obtained from: illumos (issue #1946)
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
1950 ztest backwards compatibility testing option
References:
https://www.illumos.org/issues/1950
Obtained from: illumos (issue #1950)
MFC after: 2 weeks
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
This seems to fix zdb -e behavior.
PR: bin/155104
Submitted by: swell.k@gmail.com
MFC after: 2 weeks
|
|
|
|
|
|
|
|
| |
This affects behavior of zpool import without -d option.
Reported by: Bruce Cran <bruce@cran.org.uk>
Submitted by: Fabian Keil <freebsd-listen@fabiankeil.de>
MFC after: 2 weeks
|
| |
|
| |
|
|
|
|
| |
Reference sh in the correct location (/bin/sh)
|
|
|
|
|
|
| |
these are unnecessary.
Reference sh in the correct location (/bin/sh)
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
2703 add mechanism to report ZFS send progress
If the zfs send command is used with the -v flag, the amount of bytes
transmitted is reported in per second updates.
References:
https://www.illumos.org/issues/2703
Obtained from: illumos (issue #2703)
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Partial import of illumos changeset 13622:e5889df1eaac
2077 lots of unreachable breaks in illumos gate
References:
https://www.illumos.org/issues/2077
PR: kern/167370
Submitted by: Marcelo Araujo <araujo@FreeBSD.org>
Obtained from: illumos (issue #2077)
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
with the -f flag.
Reimplementation of the illumos changeset 13677:a0cbef703c12
2635 'zfs rename -f' to perform force unmount
References:
https://www.illumos.org/issues/2635
PR: kern/164447
Suggested by: Marcelo Araujo <araujo@FreeBSD.org>
Obtained from: illumos (issue #2635)
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
2088 zdb could use a reasonable manual page
Rewrite new zdb manpage to mdoc(7)
References:
https://www.illumos.org/issues/2088
PR: kern/167467 [1]
Submitted by: Marcelo Araujo <araujo@FreeBSD.org> [1]
Reviewed by: mm
Obtained from: Illumos (issue #2088)
MFC after: 1 week
|
|
|
|
|
|
| |
PR: 167696
Submitted by: Nobuyuki Koganemaru (kogane!jp.freebsd.org)
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
| |
in the system-wide version of <stdlib.h> by wrapping the #include_next
<stdlib.h> within the scope of its own header protection. On FreeBSD this has
no effect, since both header protections are equivalent. However the GNU version
of <stdlib.h> implements a special header protection mechanism which allows it
to be included multiple times (in different modes).
Simply by moving the #include_next off the header protection, we allow
system-wide <stdlib.h> to implement its own protection policy, whichever that
may be.
|
|
|
|
|
|
|
|
|
|
|
| |
to follow the example of OpenSolaris and its descendants, which implemented
cpu as an inline that took a value out of curthread. At certain points in
the FreeBSD scheduler curthread->td_oncpu will no longer be valid (in
particukar, just before the thread gets descheduled) so instead I have
implemented this as its own built-in variable.
Sponsored by: Sandvine Inc.
MFC after: 1 week
|
|
|
|
|
|
| |
automatically mounted. This is similar to the 'zfs receive -u'.
MFC after: 1 week
|
|
|
|
| |
- Use quotes when tab is used.
|
|
|
|
|
| |
Reported by: Glen Barber <gjb@FreeBSD.org>
MFC after: 3 days
|
|
|
|
|
|
|
| |
traced. The use of SIGUSR1 caused traced processes (those attached to
with dtrace -p) to exit when dtrace exited.
MFC in: 1 week
|
| |
|
|
|
|
| |
on MIPS yet
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
CTF format is not cross-platform by design, e.g. it is not guaranteed
that data generated by ctfconvert/ctfmerge on one architecture will
be successfuly read on another. CTF structures are saved/restored
using naive approach. Roughly it looks like:
write(fd, &ctf_struct, sizeof(ctf_struct))
read(fd, &ctf_struct, sizeof(ctf_struct))
By sheer luck memory layout of all type-related CTF structures is the same
on amd64/i386/mips32/mips64. It's different on ARM though. sparc, ia64,
powerpc, and powerpc64 were not tested. So in order to get file compatible
with dtrace on ARM it should be compiled on ARM. Alternative solution would
be to have "signatures" for every platform and ctfmerge should convert host's
reperesentation of CTF structure to target's one using "signature" as template.
This patch checks byte order of ELF files used for generating CTF record
and makes sure that byte order of data written to resulting files is the same
as target's byte order.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
allow.mount.zfs:
allow mounting the zfs filesystem inside a jail
This way the permssions for mounting all current VFCF_JAIL filesystems
inside a jail are controlled wia allow.mount.* jail parameters.
Update sysctl descriptions.
Update jail(8) and zfs(8) manpages.
TODO: document the connection of allow.mount.* and VFCF_JAIL for kernel
developers
MFC after: 10 days
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
add support for "-t <datatype>" argument to zfs get
References:
https://www.illumos.org/issues/1936
Update zfs(8) manpage in respect of [1].
Fix typo in zfs(8) manpage.
Obtained from: illumos (issue #1936)
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
uninitialized variables in zfs(8) may make snapshots undestroyable [1]
References:
https://www.illumos.org/issues/2067 [1]
Obtained from: illumos (issue #2067)
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
| |
happen to have a .exe extension.
While here fix the shebang of a shell script that
was looking for /bin/bash.
Reviewed by: gnn
Approved by: jhb (mentor)
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rev. 13572:
disk sync write perf regression when slog is used post oi_148 [1]
Rev. 13573:
crash during reguid causes stale config [2]
allow and unallow missing from zpool history since removal of pyzfs [5]
Rev. 13574:
leaking a vdev when removing an l2cache device [3]
memory leak when adding a file-based l2arc device [4]
leak in ZFS from metaslab_group_create and zfs_ereport_checksum [6]
References:
https://www.illumos.org/issues/1909 [1]
https://www.illumos.org/issues/1949 [2]
https://www.illumos.org/issues/1951 [3]
https://www.illumos.org/issues/1952 [4]
https://www.illumos.org/issues/1953 [5]
https://www.illumos.org/issues/1954 [6]
Obtained from: illumos (issues #1909, #1949, #1951, #1952, #1953, #1954)
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
illumos rev 13540 [1]:
Removal of pyzfs broke delegation for volumes
illumos rev 13562 [2]:
zfs allow arguments not parsed correctly after pyzfs removal
References:
https://www.illumos.org/issues/1726 [1]
https://www.illumos.org/issues/1977 [2]
Obtained from: illumos (issues #1726, #1977)
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
names and wants to sort them by name, ie. when executes:
# zfs list -t snapshot -o name -s name
Because only name is needed we don't have to read all snapshot properties.
Below you can find how long does it take to list 34509 snapshots from a single
disk pool before and after this change with cold and warm cache:
before:
# time zfs list -t snapshot -o name -s name > /dev/null
cold cache: 525s
warm cache: 218s
after:
# time zfs list -t snapshot -o name -s name > /dev/null
cold cache: 1.7s
warm cache: 1.1s
MFC after: 1 week
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
| |
Reported by: pjd
MFC after: 3 days
|
|
|
|
|
| |
here, as we open /dev/null for test purposes, but it is useful for consistency
and further grepping for such bugs.
|
|
|
|
|
|
| |
snprintf tricks.
MFC after: 1 week
|
|
|
|
|
|
| |
to fprintf as a field width. It should be an int instead, so cast it.
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
uint64_t values are snprintf'd using %llx. On amd64, uint64_t is
typedef'd as unsigned long, so cast the values to u_longlong_t, as is
done similarly in the rest of the file.
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
uint64_t values are snprintf'd using %llx. On amd64, uint64_t is
typedef'd as unsigned long, so cast the values to u_longlong_t, as is
done similarly in the rest of the file.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
dt_popc() function assumes that either _ILP32 or _LP64 is defined,
otherwise it has no suitable implementation.
However, the _ILP32 and _LP64 macros come from isa_defs.h, which is not
included in this file. Add the include now, to get the macros defined.
MFC after: 1 week
|
|
|
|
|
|
| |
correct printf format for a key_t (aka long).
MFC after: 1 week
|
|
|
|
|
|
| |
correct printf format for an unsigned long.
MFC after: 1 week
|
|
|
|
|
|
|
| |
This code only runs on i386 and amd64, so there should be no problems if
buf + sec->dofs_offset is not aligned (which is unlikely anyway).
MFC after: 1 week
|
|
|
|
|
| |
Submitted by: Nobuyuki Koganemaru <n-kogane@syd.odn.ne.jp>
MFC after: 3 days
|
|
|
|
|
| |
Reported by: Nobuyuki Koganemaru <kogane@FreeBSD.org>
MFC after: 3 days
|