src/sbin/mdconfig/mdconfig.8, branch release/6.0.0_cvsFreeBSD source treehttp://cgit.freebsd.org/src/atom?h=release%2F6.0.0_cvs2005-11-03T00:35:26ZThis commit was manufactured by cvs2svn to create tag2005-11-03T00:35:26Zcvs2svncvs2svn@FreeBSD.org2005-11-03T00:35:26Zurn:sha1:3640cb54210edbb7edbf1b12ef0127ecfcea967d
'RELENG_6_0_0_RELEASE'.
This commit was manufactured to restore the state of the 6.0-RELEASE image.
Allow to specify device size in bytes.2005-01-22T20:02:01ZPawel Jakub Dawidekpjd@FreeBSD.org2005-01-22T20:02:01Zurn:sha1:0d79319a76a9559ccadba0bd1bfd09870895c91d
MFC after: 1 week
Bump .Dd, replace missing letter, and prefer to use a verb that2004-11-06T14:03:37ZDima Dorfmandd@FreeBSD.org2004-11-06T14:03:37Zurn:sha1:df5f8fa751cd5f46e10d306e9b6f7d42f60ff27a
matches the option letter.
Submitted by: ru
Should know better by now: dd
Update the description of -l to reflect reality. After mdconfig.c2004-11-06T10:21:12ZDima Dorfmandd@FreeBSD.org2004-11-06T10:21:12Zurn:sha1:e08f2053fc90833edfb91b068a78841dddd47170
1.25, -l without -u only lists the names, so specifying -u does more
than just limit the output to one device.
- Make md(4) 64-bit clean.2004-09-16T21:32:13ZPawel Jakub Dawidekpjd@FreeBSD.org2004-09-16T21:32:13Zurn:sha1:b830359bc58e3733d84002a4e2c438c378ff5b30
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.
Mechanically kill hard sentence breaks.2004-07-02T21:45:06ZRuslan Ermilovru@FreeBSD.org2004-07-02T21:45:06Zurn:sha1:9806e231322307da0109e101ae2ef997a4a22290Assorted markup, grammar, and spelling fixes.2004-05-17T08:35:43ZRuslan Ermilovru@FreeBSD.org2004-05-17T08:35:43Zurn:sha1:d04b5dfe6cb5c950c97bcc0c5742c01d1d8d33f9Fix a long-standing deadlock issue with vnode backed md(4) devices:2004-03-10T20:41:09ZPoul-Henning Kampphk@FreeBSD.org2004-03-10T20:41:09Zurn:sha1:7a6b2b64294749875e4dc9ae49feac24c1d862e5
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/2004-02-19T19:53:07ZPoul-Henning Kampphk@FreeBSD.org2004-02-19T19:53:07Zurn:sha1:91f9647d4952a642756c1ccb915a0bf361069b67Note that geometry can also be specified on vnode backed deviecs.2004-01-12T10:54:09ZPoul-Henning Kampphk@FreeBSD.org2004-01-12T10:54:09Zurn:sha1:79ae25f61fbae37ab553e2d0bc29f4784395dc54