| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
Found by: kris
MFC after: 3 days
|
|
|
|
|
| |
Pointed out by: marck
X-MFC-after: few seconds
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 3 weeks
|
|
|
|
| |
MFC after: 3 weeks
|
|
|
|
|
| |
Reported by: stefanf
MFC after: 3 days
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
| |
usage for a subcommand, so no 'usage' function has to be implemented
in class library.
- Bump version number as it breaks ABI, but don't provide backward
compatibility, because there are probably no external consumers of this
geom(8).
This allows to print more precise usage for standard commands and simplify
class libraries a bit.
MFC after: 1 week
|
|
|
|
|
|
| |
just leave reference to geom(8).
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
# gmirror status
Name Status Components
mirror/root COMPLETE ad0s1a
ad2s1a
mirror/data DEGRADED da0
da1 (76%)
da2
# gmirror status -s
Name Status Components
mirror/root COMPLETE ad0s1a
mirror/root COMPLETE ad2s1a
mirror/data DEGRADED da0
mirror/data DEGRADED da1 (76%)
mirror/data DEGRADED da2
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
| |
warning on 64-bit platforms. Explicitly cast these values to int
to work around this issue, as these values are tend to be small.
Spotted by: ia64 tinderbox
|
|
|
|
|
|
| |
- Update copyrights.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For example:
# gmirror status
Name Status Components
mirror/root COMPLETE ad0s1a
ad2s1a
mirror/data DEGRADED da0
da1 (76%)
da2
MFC after: 1 week
|
| |
|
|
|
|
|
|
| |
'list_one_*'.
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
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
|
| |
|