| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
providers.
This prevents from listing geoms like <name>.sync which can be confusing.
It still allows to show details about it by giving its name when listing.
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
shared-last-sector problem.
After this change, even if there is more than one provider with the same
last sector, the proper one will be chosen based on its size.
It still doesn't fix the 'c' partition problem (when da0s1 can be confused
with da0s1c) and situation when 'a' partition starts at offset 0
(then da0s1a can be confused with da0s1 and da0s1c). One can use '-h'
option there, when creating device or avoid sharing last sector.
Actually, when providers share the same last sector and their size is equal,
they provide exactly the same data, so the name (da0s1, da0s1a, da0s1c)
isn't important at all.
- Provide backward compatibility.
- Update copyright's year.
MFC after: 1 week
|
|
|
|
|
|
|
| |
alternative to /lib/geom/ path where shared libraries are stored.
- Improve debugging.
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
| |
|
|
|
|
|
| |
PR: 77437
Submitted by: Paul A. Hoadley <paulh@logicsquad.net> (original version)
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Manual pages fixes by: ru
MFC after: 3 days
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
the given providers. Without even one of the configured components there
should be no way to get the secret.
Supported by: WHEEL Sp. z o.o.
http://www.wheel.pl
|
| |
|
|
|
|
|
|
|
|
|
| |
message, i.e.:
geom: usage: geom <class> <command> [options]
PR: bin/71537
Submitted by: bugghy <bugghy@phenix.rootshell.be>
MFC after: 5 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After this change, when component is disconnected because of an I/O error,
it will not be connected and synchronized automatically, it will be logged
as broken and skipped. Autosynchronization can occur, when component is
disconnected (on orphan event) and connected again - there were no I/O
error, so there is no need to not connected the component, but when there were
writes while it wasn't connected, it will be synchronized.
This fix cases, when component is disconnected because of I/O error and can be
connected again and again.
- Bump version number.
- Implement backward compatibility mechanism. After this change when metadata in
old version is detected, it is automatically upgraded to the new (current)
version.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After this change, when component is disconnected because of an I/O error,
it will not be connected and synchronized automatically, it will be logged
as broken and skipped. Autosynchronization can occur, when component is
disconnected (on orphan event) and connected again - there were no I/O
error, so there is no need to not connected the component, but when there were
writes while it wasn't connected, it will be synchronized.
This fix cases, when component is disconnected because of I/O error and can be
connected again and again.
- Bump version number.
- Add version change history.
- Implement backward compatibility mechanism. After this change when metadata in
old version is detected, it is automatically upgraded to the new (current)
version.
|
| |
|
| |
|
|
|
|
|
| |
when this mode is used.
- Manual page update.
|
| |
|
|
|
|
| |
Reviewed by: pjd
|
|
|
|
| |
Submitted by: ceri
|
|
|
|
| |
Submitted by: ceri
|
| |
|
| |
|
| |
|
|
|
|
| |
Reported by: obrien
|
| |
|
|
|
|
| |
commands.
|
|
|
|
|
| |
- When command is not available, just say it, instead of says, that command
is unknown. Old behaviour seems to be too confusing.
|
|
|
|
|
|
|
| |
of parity component, because we can't return an EIO error for read of
every sector which wasn't written first.
Discussed with: phk
|
| |
|
|
|
|
| |
Requested by: Michael Handler <handler@grendel.net>
|
|
|
|
|
| |
only.
- Use getprogname() function when informing about versions problem.
|
|
|
|
| |
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
[...]
|
|
|
|
|
| |
- 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
|
| |
|
|
|
|
|
|
|
| |
transformation and graid3(8) userland utility, which can be used for
configuration. No manual page yet, sorry.
Hardware provided by: Daniel Seuffert
|
|
|
|
|
| |
be staticaly linked.
This fixes problems on systems compiled with NO_DYNAMICROOT.
|