| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Reported by: ru
|
|
|
|
|
|
|
|
| |
and disklabel.5. Refrencing bsdlabel.5 is somewhat bogus as it is not
connected to the build and is mostly unwritten at this point.
Reported by: Matthias Andree <matthias.andree at web.de>
PR: docs/72020
|
|
|
|
|
|
| |
correct to change the cast from unsigned int to uint32_t.
Pointed out by: luigi
|
|
|
|
| |
Pointed out by: -current users
|
| |
|
| |
|
|
|
|
| |
Submitted by: ssouhlal
|
|
|
|
| |
commands.
|
|
|
|
|
| |
- When command is not available, just say it, instead of says, that command
is unknown. Old behaviour seems to be too confusing.
|
|
|
|
|
|
|
|
|
| |
After this change it should be possible to use very big md(4) devices.
- Clean up and simplify the code a bit.
- Use humanize_number(3) to print size of md(4) devices.
- Add 't' suffix which stands for terabyte.
- Make '-S' to really work with all types of devices.
- Other minor changes.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
and sent to the DIVERT socket while the original packet continues with the
next rule. Unlike a normally diverted packet no IP reassembly attemts are
made on tee'd packets and they are passed upwards totally unmodified.
Note: This will not be MFC'd to 4.x because of major infrastucture changes.
PR: kern/64240 (and many others collapsed into that one)
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
contain O_UID, O_GID and O_JAIL opcodes, the F_NOT or F_OR logical
operator bits get clobbered. Making it impossible to use the ``NOT'' or
``OR'' operators with uid, gid and jail based constraints.
The ipfw_insn instruction template contains a ``len'' element which
stores two pieces of information, the size of the instruction
(in 32-bit words) in the low 6 bits of "len" with the 2 remaining
bits to implement OR and NOT.
The current code clobbers the OR and NOT bits by initializing the
``len'' element to the size, rather than OR'ing the bits. This change
fixes this by changing the initialization of cmd->len to an OR operation
for the O_UID, O_GID and O_JAIL opcodes.
This may be a MFC candidate for RELENG_5.
Reviewed by: andre
Approved by: luigi
PR: kern/63961 (partially)
|
|
|
|
|
| |
PR: bin/71485
Submitted by: Jukka A. Ukkonen
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
0xffffffff sectors. Document this limit and avoid installing bogus
labels on disks with more sectors.
Allowing the installation of labels addressing as much of the disk as
possiable may be a useful addition in some situations, but this was easy
to implement and should reduce confusion.
PR: bin/71408
|
|
|
|
|
|
|
| |
also print out the option that is unknow so that the user knows what (s)he
did wrong..
MFC after: 3 days
|
|
|
|
|
| |
fix a 5.x'ism that 4.x needs protection from.
make this code compile standalone.
|
| |
|
|
|
|
|
|
| |
e.g. mirror/<name>, stripe/<name>.
Approved by: phk
|
|
|
|
|
|
|
|
|
| |
increasing it. Add code to ifconfig to use this size to find the
sockaddr_dl after the struct if_data in the routing message. This
allows struct if_data to grow (up to 255 bytes) without breaking
ifconfig.
Submitted by: peter
|
| |
|
|
|
|
| |
Inspired by: kan
|
| |
|
|
|
|
| |
Ok'ed by: fjoe
|
|
|
|
| |
sysctl tool to print a more readable value for temperatures.
|
|
|
|
|
|
|
| |
of parity component, because we can't return an EIO error for read of
every sector which wasn't written first.
Discussed with: phk
|
|
|
|
|
|
|
|
|
|
|
| |
keyword but without 'logamount' limit the amount of their log messages
by net.inet.ip.fw.verbose_limit sysctl value.
RELENG_5 candidate.
PR: kern/46080
Submitted by: Dan Pelleg
MFC after: 1 week
|
| |
|
|
|
|
| |
Requested by: Michael Handler <handler@grendel.net>
|
|
|
|
|
| |
only.
- Use getprogname() function when informing about versions problem.
|
|
|
|
|
|
| |
PR: bin/70311
Submitted by: Pawel Malachowski <pawmal-posting@freebsd.lublin.pl>
MFC after: 3 days
|
|
|
|
| |
Submitted by: kuriyama
|
| |
|
|
|
|
|
|
|
|
| |
verification of regular data when device is in complete state.
On verification error, EIO error is returned for the bio and sysctl
kern.geom.raid3.stat.parity_mismatch is increased.
Suggested by: phk
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
as well, even if device is in complete state.
I observe 40% of speed-up with this option for random read operations,
but slowdown for sequential reads.
Basically, without this option reading from a RAID3 device built from 5
components (c0-c4) looks like this:
Request no. Used components
1 c0+c1+c2+c3
2 c0+c1+c2+c3
3 c0+c1+c2+c3
With the new feature:
Request no. Used components
1 c0+c1+c2+c3
2 (c1^c2^c3^c4)+c1+c2+c3
3 c0+(c0^c2^c3^c4)+c2+c3
4 c0+c1+(c0^c1^c3^c4)+c3
5 c0+c1+c2+(c0^c1^c2^c4)
6 c0+c1+c2+c3
[...]
|
|
|
|
|
|
|
|
| |
has only been partly initialized via newfs(8) so that it applies to both
UFS1 and UFS2.
Submitted by: "Xin LI" delphij at frontfree dot net
MFC: maybe?
|
|
|
|
|
| |
- Connect it to the build.
- Inform geom(8) about it.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Add manual page for gmirror(8) utility.
|
|
|
|
|
|
|
| |
- Connect it to the build.
- Inform geom(8) manual page about it.
Reviewed by: trhodes
|
|
|
|
|
|
|
| |
rather than the one from libz, corresponding to a function, when
linking statically.
PR: bin/70392
|
| |
|
|
|
|
|
|
|
| |
transformation and graid3(8) userland utility, which can be used for
configuration. No manual page yet, sorry.
Hardware provided by: Daniel Seuffert
|