| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
| |
crashes, the config remains locked and causes all
subsequent start or read attempts to fail. This is part
of a fix for the recently reported hangs.
Approved by: re (scottl)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- dumpon utility has not used kern.dumpdev sysctl
since rev. 1.14 (sbin/dumpon/dumpon.c) when phk@
updated it to use the DIOCSKERNELDUMP ioctl [1]
- remove obsolete reference to sysctl(3)
While I am there, fix two style nits:
- use .Nm instead of `dumpon'
- change NOTES to IMPLEMENTATION NOTES, to bring
it in line with recommended section headings in
mdoc(7)
Original patch by: Martin Faxer <gmh003532brfmasthugget.se> [1]
PR: docs/39293
Approved and Reviewed by: des (mentor), re (scottl, bmah)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1024-byte boundaries. For many years this was a reasonable
assumption. However, in recent years we have begun seeing
devices with 2048-byte sectors. These devices return errors
when dump tries to read starting in the middle of a sector
or when it tries to read only the first half of a sector.
Rather than change the native block size used by dump (and
thus create an incompatible dump format), this fix checks
for transfer requests that start and/or end on a non-sector
boundary. When such a read is detected, the new code reads
the entire sector and copies out just the part that dump
needs.
Reviewed by: Poul-Henning Kamp <phk@critter.freebsd.dk>
Approved by: re (John Baldwin <jhb@FreeBSD.org>)
Sponsored by: DARPA & NAI Labs.
|
| |
|
|
|
|
| |
Submitted by: Tim Kientzle <kientzle@acm.org> (embellished by me)
|
|
|
|
|
|
|
| |
Install a link to the disklabel(8) name on i386 and alpha platforms.
Leave old disklabel(8) sources intact but disconnected from the build
for now.
|
|
|
|
| |
Spotted by: mbr
|
|
|
|
| |
encrypted with gbde(8).
|
| |
|
| |
|
|
|
|
|
|
| |
Submitted by: Allan Saddi <allan@saddi.com>
vinum_read: White space cleanup.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
work because it referred to plexes which were almost invariably when
referred to. Instead, deprecate the "prefer" keyword for volumes
(though it's still there for the moment) and add a keyword "preferred"
to the plex definition. The relationship is like this:
Old:
vol foo ... prefer foo.p3
New:
plex foo.p3 volume foo preferred
printconfig: Print out the "preferred" keyword for plexes where
appropriate.
Still print out "prefer" for volumes. The kernel module
continues to accept this version, but it's probably not
going to live much longer.
|
| |
|
|
|
|
| |
PR: 46096
|
| |
|
|
|
|
|
|
|
|
|
| |
references to it's man page, which is almost never installed on a
FreeBSD system. The information about using this command with gated
has been retained. I have just made it clear that gated is not a part
of FreeBSD.
PR: docs/51407
|
|
|
|
|
|
|
|
|
|
|
| |
vinum_read:
Accept 0 parameters, hand an empty string to the kernel if so.
Use new ioctl VINUM_READCONFIG, not VINUM_CREATE, to read config.
vinum_start: When passed 0 parameters, drop the devstat kludge and
call vinum_read instead. It's no longer necessary to distinguish
between "start" and "read" if no parameters are passed, and
probably one of them should go away.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Hide all the historical fields of the label, unless people ask for them with -A,
set them to intelligently chosen defaults otherwise.
Distill the manual page to remove inaccuracies, misundertandings and obsolete
information. It can probably still be done better but now at least it is
not misinforming people.
|
| |
|
|
|
|
| |
Various cleanup.
|
| |
|
|
|
|
|
|
|
|
| |
recorded in global variables, rather than checks on the architecture.
Drop horribly code to handle MBR/PC98's embedded in the BSD label area.
If you need to have an MBR or PC98 on your disk, you should not overlap
it with a BSDLABEL, if you don't need it, this code is nothing but trouble.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
for the alpha checksum, and set them depending on the specified architecture
Don't look for disklabels every 16 bytes, look the only place they should
be for the current architecture.
Always read the label from the raw disk and decode it into struct
disklabel rather than trust a cast from random addresses.
When writing to the raw disk, encode the label properly.
|
| |
|
|
|
|
|
| |
from dd(1)'ing the boot code off one drive and have bsdlabel write it
on another.
|
|
|
|
| |
in there to run over the various architectures.
|
|
|
|
|
|
|
| |
However, since NULL was used, and this is C++, this error went
undetected until g++ 3.3 somehow managed to whine about it.
Reported by: obrien
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
remote backups can still be done with Kerberos authentication using
SSH and Kerberos 5.
|
| |
|
| |
|
| |
|
|
|
|
| |
to cope with kernel modules with VINUMDEBUG.
|
|
|
|
| |
Change name of history file to History to avoid name conflicts.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change name of history file to History to avoid name conflicts.
Don't try to make devices unless devfs has been removed.
Don't accept resetconfig command from a file.
Abused by: Jens Schweikhardt <schweikh@schweikhardt.net>
Remove dead code (#if 0)
vinum_mirror: Don't try to create mirrors with 0 drives.
Found by: mismatch between enum kw in two different files.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change name of history file to History to avoid name conflicts.
Rewrite minor number decoding. Now we have only three types of
object: subdisks, plexes and volumes. The encoding for plexes and
subdisks no longer reflects the object to which they belong. The
super devices are high-order volume numbers. This gives vastly more
potential volumes (4 million instead of 256).
Don't try to chown directories if they haven't been created.
|
|
|
|
|
|
|
| |
vinum_info: Use increasing verbosity to show time spent in disk
driver.
Correct a comment.
|
|
|
|
|
|
|
|
| |
be changed, it is very convenient to be able to toggle SDH/Sonet,
idle/unassigned cells and scrambled mode and to see the carrier
state.
Reviewed by: -arch (if_media.h definitions)
|
| |
|
|
|
|
|
| |
this is mostly intended for use with multi-mode 802.11 devices that support
some combination of 11a, 11b, and 11g
|