summaryrefslogtreecommitdiffstats
path: root/sbin/mdconfig
Commit message (Collapse)AuthorAgeFilesLines
* change the name of the md module, to g_md, introduce a define with thejmg2004-08-091-1/+1
| | | | name MD_MODNAME, and make mdconfig use this new define...
* Give better diagnostic for problems with backing files.phk2004-07-251-0/+4
|
* Mechanically kill hard sentence breaks.ru2004-07-021-1/+2
|
* Assorted markup, grammar, and spelling fixes.ru2004-05-171-11/+16
|
* Fix a long-standing deadlock issue with vnode backed md(4) devices:phk2004-03-102-1/+8
| | | | | | | | | | | | | | | | | | | | | | | | | On vnode backed md(4) devices over a certain, currently undetermined size relative to the buffer cache our "lemming-syncer" can provoke a buffer starvation which puts the md thread to sleep on wdrain. This generally tends to grind the entire system to a stop because the event that is supposed to wake up the thread will not happen until a fair bit of the piled up I/O requests in the system finish, and since a lot of those are on a md(4) vnode backed device which is currently waiting on wdrain until a fair amount of the piled up ... you get the picture. The cure is to issue all VOP_WRITES on the vnode backing the device with IO_SYNC. In addition to more closely emulating a real disk device with a non-lying write-cache, this makes the writes exempt from rate-limited (there to avoid starving the buffer cache) and consequently prevents the deadlock. Unfortunately performance takes a hit. Add "async" option to give people who know what they are doing the old behaviour.
* s/bytes/byte/phk2004-02-191-1/+1
|
* Note that geometry can also be specified on vnode backed deviecs.phk2004-01-121-1/+1
|
* Warn that big malloc disks are a panic(8) implementation.phk2004-01-021-0/+5
| | | | | | | Submitted by: Colin Percival <cperciva@builder.daemonology.net> (Who should really get his own bit one of these days!) PR: 59988
* Add a full example of a file-backed disk creation, I used the Handbook'sblackend2003-10-111-0/+9
| | | | | | | example. PR: docs/51897 Submitted by: Kevin Oberman <oberman@es.net>
* s/disklabel/bsdlabel where needed.blackend2003-10-111-1/+1
|
* Document the -x and -y options.phk2003-09-211-0/+14
|
* Do not compare unsigned int values with ULONG_MAX. The comparison iskan2003-07-111-1/+1
| | | | always false on 64bit platforms and GCC 3.3.1 issues warning there.
* Add "-n" argument, which causes mdconfig to simply print the unitrwatson2003-06-112-5/+16
| | | | | | number X, rather than mdX, making it easier to script tests that use md devices but don't want to make assumptions about any existing md use (such as in diskless environments).
* Add .Xr's to mdmfs(8).dougb2003-04-271-0/+1
| | | | Submitted by: Scot W. Hetzel <hetzels@westbend.net>
* Add a couple of undocumented test options to MD(4) to aid in regressionphk2003-04-091-1/+11
| | | | testting of GEOM.
* Give clearer diagnostics on some cases of invalidyar2003-04-011-0/+6
| | | | | | | combinations of mdconfig(8) command-line arguments. Make mdconfig(8) accept "-a -f file -o options" equally with "-a -f file" (assuming "-t vnode".)
* Add a "-S sectorsize" option to enable Kirk to find a bug :-)phk2003-03-032-2/+10
|
* Don't use the kern.disks sysctl to find a list of md devices, use thephk2003-01-271-41/+7
| | | | | | MDIOCLIST ioctl instead. Spotted by: keramida
* Make sure strsep() gets a nul-terminated string.keramida2002-10-101-1/+2
| | | | Reviewed by: phk
* Don't show disklabel in the examples, it is not necessary.phk2002-09-261-3/+2
|
* s/filesystem/file system/g as discussed on -developerstrhodes2002-08-211-1/+1
|
* Don't use NULL where you really mean 0 to sysctlbyname.imp2002-08-211-1/+1
|
* Replace extra call to "tunefs" with the equivalent of "newfs -U".rse2002-07-151-2/+1
| | | | Reviewed by: phk
* The .Nm utilitycharnier2002-07-061-3/+3
|
* Usage style sweep: spell "usage" with a small 'u'.des2002-04-221-1/+1
| | | | | Also change one case of blatant __progname abuse (several more remain) This commit does not touch anything in src/{contrib,crypto,gnu}/.
* Revert 1.20:mike2002-03-211-2/+0
| | | | | Memory disks may be used for other purposes besides newfs(8), so it isn't helpful to require the minimum size meet newfs(8)'s criteria.
* Provide a proper error message in mdconfig(8) when a filesystem is toomike2002-03-211-0/+2
| | | | small, instead of a less meaningful error in newfs(8).
* Actually make use of the md_version field of 'struct mdio'. In orderdd2001-12-201-0/+2
| | | | | | not to needlessly break compatibility, decrement MDIOVERSION to 0. Approved by: phk
* Default to WARNS=2.obrien2001-12-041-1/+0
| | | | | | Binary builds that cannot handle this must explicitly set WARNS=0. Reviewed by: mike
* mdoc(7) police: removed (now gratuitous) .Xo/.Xc brackets.ru2001-08-101-18/+6
|
* Move all the prototypes to one place.dd2001-08-071-3/+2
|
* Introduce a force option, MD_FORCE, that instructs the driver todd2001-08-072-0/+9
| | | | | | | | | | | | | | | | bypass some extra anti-foot-shooting measures. Currently, its only effect is to allow detaching a device while it's still open (e.g., mounted). This is useful for testing how the system reacts to a disk suddenly going away, which can happen with some removeable media. At this point, the force option is only checked on detach, so it would've been possible to allow the option to be passed with the MDIOCDETACH operation. This was not done to allow the possibility of having the force flag influence other tests in the future, which may not necessarily deal with detaching the device. Reviewed by: sobomax Approved by: phk
* Use MD_NAME and MDCTL_NAME constants where appropriate.dd2001-07-181-1/+2
|
* Remove whitespace at EOL.dd2001-07-151-5/+5
|
* mdoc(7) police: removed HISTORY info from the .Os call.ru2001-07-101-1/+1
|
* Constify mdmaybeload(), add a prototype for usage(), and get rid of add2001-06-212-3/+6
| | | | sizeof(int) == sizeof(long) assumption; clamp down with WARNS=2.
* Don't assume the length of MD_NAME is 2.dd2001-06-211-2/+2
|
* Fail if -s isn't specified for an MD_MALLOC or MD_SWAP disk; thedd2001-06-211-1/+7
| | | | | | | | | | driver itself obviously won't configure such a disk, but the error returned (EDOM) is more cryptic to the average user than it should be. Also assert that the argument to -u is in fact a valid unit; don't just accept any string to mean 0. Approved by: phk
* - Backout botched attempt to introduce MANSECT feature.ru2001-03-261-0/+1
| | | | - MAN[1-9] -> MAN.
* Set the default manual section for sbin/ to 8.ru2001-03-201-1/+0
|
* mdoc(7) police: add a missing An call.ru2001-03-121-1/+2
|
* In the absence of explicit ``-t type'' option assume that ``-f file''sobomax2001-03-091-1/+6
| | | | | | implies ``-t vnode''. Approved by: phk
* Make md(4) and mdconfig(8) take over the role of vn(4) and vnconfig(8)phk2001-03-092-2/+16
| | | | | | | entirely as previously advertised. md(4) adopted all assets of vn(4) some time back and has proper devfs support and cloning abilities to boot.
* 1) If mdconfig isn't given an action argument, it assumes detach.phk2001-03-091-4/+5
| | | | | | | | | 2) Running `mdconfig -l` without any attached devices results in mdconfig printing "md0" to standard output. Submitted by: dd [1] [1] no, not "dd(1)" but "Dima Dorfman"
* Remove "autounit" from settable options, it's the default unless youphk2001-02-262-12/+3
| | | | | | specify -u. Spotted by: dcs
* Forgot to remove unneeded "intcmp" function.phk2001-02-251-8/+0
|
* Make "md" and "mdctl" macroized parameters.phk2001-02-252-10/+134
| | | | | | Implement "-l" option to mdconfig which can list one or all md devices. Submitted by: Dima Dorfman <dima@unixfreak.org>
* Make md/mdconfig do kld.phk2001-02-241-0/+36
| | | | Submitted by: dcs
* Strip optional prefixes "/dev/" and "md" from the -u argument.phk2001-01-311-0/+5
|
* Duh, the version of mdconfig.c I committed came from the wrong machine.phk2001-01-282-20/+1
| | | | | | | Commit the right version, but without the -b option which is too evil for the present. Remove -b and preload from the manpage as well.
OpenPOWER on IntegriCloud