| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
device be created read+write, check to see if the backing store is read only
through the use of the access(2) system call. If this check fails returning
EACCES, EPERM or EROFS then gracefully downgrade the access to read only. Also
print a warning message to stderr, informing the user that the access mode
they requested is not available.
This behavior used to be handled by md(4) but was changed in revision 1.154
Discussed with: pjd, phk, Dario Freni <saturnero at freesbie dot org>
Reviewed by: phk
|
| |
|
|
|
|
| |
Split the usage line to not exceed 80 chars.
|
| |
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
show file name for 'mdconfig -l -u <x>' command.
This allows to preserve API/ABI compatibility with version 0 (that's why
I changed version number back to 0) and will allow to merge this change
to RELENG_5.
MFC after: 5 days
|
| |
|
|
|
|
|
| |
'mdconfig -l -u <unit>'.
Bump version number, as this change breaks ABI/API.
|
|
|
|
|
|
| |
empty line. This is consistent with other utilities.
While I'm here, remove artifacts of the previous list implementation.
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
also print out the option that is unknow so that the user knows what (s)he
did wrong..
MFC after: 3 days
|
|
|
|
| |
name MD_MODNAME, and make mdconfig use this new define...
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
always false on 64bit platforms and GCC 3.3.1 issues warning there.
|
|
|
|
|
|
| |
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).
|
|
|
|
| |
testting of GEOM.
|
|
|
|
|
|
|
| |
combinations of mdconfig(8) command-line arguments.
Make mdconfig(8) accept "-a -f file -o options"
equally with "-a -f file" (assuming "-t vnode".)
|
| |
|
|
|
|
|
|
| |
MDIOCLIST ioctl instead.
Spotted by: keramida
|
|
|
|
| |
Reviewed by: phk
|
| |
|
|
|
|
|
| |
Also change one case of blatant __progname abuse (several more remain)
This commit does not touch anything in src/{contrib,crypto,gnu}/.
|
|
|
|
|
| |
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.
|
|
|
|
| |
small, instead of a less meaningful error in newfs(8).
|
|
|
|
|
|
| |
not to needlessly break compatibility, decrement MDIOVERSION to 0.
Approved by: phk
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
sizeof(int) == sizeof(long) assumption; clamp down with WARNS=2.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
implies ``-t vnode''.
Approved by: phk
|
|
|
|
|
|
|
|
|
| |
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"
|
|
|
|
|
|
| |
specify -u.
Spotted by: dcs
|
| |
|
|
|
|
|
|
| |
Implement "-l" option to mdconfig which can list one or all md devices.
Submitted by: Dima Dorfman <dima@unixfreak.org>
|
|
|
|
| |
Submitted by: dcs
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
| |
extension.
Add ability to create a preload disk giving an address and a length
(suggested by imp)
Fix bug relating to very small md(4) devices.
Update md.c copyright to reflect the status of code copied from vn.c.
(noticed by dillon)
|
|
|
|
|
|
| |
Using the mdconfig(8) program you can now configure memory disks
on malloc(9), swap or a file/vnode. preloaded md disks also work
as usual.
|
|
|
|
|
| |
Add a rudimentary man-page. (I'm no mdoc wizard, feel free to attack my
mistakes and blunders)
|
|
I decided to work on the md(4) driver and integrate the vn(4)
functionality into it mainly based on the name being more suitable.
Ideally 'vd' as in "virtual disk" would probably be the most logical
but our sound-master pointed out that this would cause uncontrollable
fits of giggles in the brits. Another complication would the needed
changes to the ramdisk boot/root functionality.
The vn driver will stay around for some time after I complete this
merge for transition reasons, and I'll make it whine to people that
they should migrate to the md(4) driver for some time before it
dies.
The kernel part of the new md(4) driver will be committed after more
testing.
|