| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
in-memory changes only and as such are only useful for prototyping
and regression testing purposes.
|
|
|
|
|
|
|
| |
up. This make iostat report operations passed down to the device driver
instead of operations passed down to GEOM disk. The transfer size limit
imposed by the device driver is no longer hidden, improving the correlation
between iostat output and device driver workload.
|
|
|
|
|
|
|
| |
- Do not allow rw access.
Submitted by: Dario Freni <saturnero at freesbie dot org>
MFC after: 3 days
|
|
|
|
|
| |
o Don't set the error twice when the named class does not exist.
It causes ioctl(2) to return with error EEXIST.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
requests. The following features have been added:
1. Extensive checking and validation of both the primary and
secondary headers to protect against corrupted data and to
take advantage of the redundancy to allow the GPT to be
used in the face of recoverable corruption.
2. Dynamic data-structures to avoid hardcoding gratuitous
table limits so as to support the creation of GPT tables
of (as of yet) unspecified size.
3. Only allow kernel dumps to swap partitions to provide the
necessary anti-footshooting measures. Linux swap partitions
are allowed.
4. Complete dump of the GPT configuration, including labels.
5. Supports Byte Order Mark (U+FEFF) handling for big-endian,
little-endian and mixed-endian partition names.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
state where sleeping on a sleep queue is not allowed. The facility
doesn't support recursion but uses a simple private per-thread flag
(TDP_NOSLEEPING). The sleepq_add() function will panic if the flag is
set and INVARIANTS is enabled.
- Use this new facility to replace the g_xup and g_xdown mutexes that were
(ab)used to achieve similar behavior.
- Disallow sleeping in interrupt threads when invoking interrupt handlers.
MFC after: 1 week
Reviewed by: phk
|
|
|
|
|
|
|
|
|
|
|
|
| |
it is destroyed in GEOM, in addition to being removed from /dev.
Before this patch, if you applied a new MBR which deleted a slice,
the deleted slice would not be in /dev, but it would still appear
in kern.geom.conftxt and kern.geom.confxml, which would confused
the diskPartitionEditor in sysinstall.
Submitted by: pjd
Tested by: pjd, rodrigc
MFC after: 1 week
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
| |
Reported by: Nick Evans <nevans@syphen.net>
MFC after: 3 days
|
|
|
|
|
| |
be destroyed. That way the GEOM system handles all deallocations
and we don't have to do it ourselves.
|
|
|
|
|
|
|
|
|
|
|
|
| |
waiting for geom events to happen:
Instead of maintaining a count of outstanding events, simply look if
the queue is empty. Make sure to not remove events from the queue
until they are executed in order to not open a new race.
Much work by: pjd
Tested by: kris
MT6: yes, should be.
|
| |
|
|
|
|
| |
This should hopefully allow to track down "duplicate free of g_bio" panics.
|
|
|
|
|
| |
in progress, and be a bit more user friendly in terms of error
messages returned from the kernel.
|
| |
|
|
|
|
|
|
|
|
|
| |
This way, the VINUMDRIVE class is loaded before the VINUM class,
but since geom does the tasting for newly arrived classes
last-in-first-out, the VINUM class tastes first.
This removes the need to call gv_parse_config() in the drive
taste path.
|
|
|
|
| |
MFC after: 2 days
|
|
|
|
| |
Reviewed by:pjd
|
|
|
|
| |
Reported by: Martin <nakal@nurfuerspam.de>
|
|
|
|
| |
This makes degraded RAID5 plexes actually work.
|
|
|
|
|
|
| |
as we have active CPUs and bind each thread to its own CPU.
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
| |
Convinced by: green, Gavin Atkinson, dougb, gordon
MFC after: 1 day
|
|
|
|
|
|
|
|
|
|
|
| |
sizeof(struct g_eli_metadata) will return the exact number of bytes needed
for storing it on the disk.
Without this change GELI was unusable on amd64 (and probably other 64-bit
archs), because sizeof(struct g_eli_metadata) was greater than 512 bytes
and geli(8) was failing on assertion.
Reported by: Michael Reifenberger <mike@Reifenberger.com>
MFC after: 3 days
|
|
|
|
|
|
| |
when there is only one key set.
MFC after: 3 days
|
|
|
|
|
|
| |
- Fix number of spaces.
MFC after: 3 days
|
|
|
|
|
| |
Reviewed by: cperciva
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
There is no performance impact, but allows to allocate memory with
M_WAITOK flag.
As a side effect this simplify code a bit.
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
|
| |
our callback will still be called, just to tell us that requested
failed...
Reported by: Mike Tancsa <mike@sentex.net>
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
| |
|
| |
|
|
|
|
|
|
|
| |
When a drive is newly created, it's state is initially set to 'down',
so it won't allow saving the config to it (thus it will never know of
itself being created). Work around this by adding a new flag, that's
also checked when saving the config to a drive.
|
|
|
|
|
|
| |
the functions which participate in I/O paths.
MFC after: 1 day
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
| |
Submitted by: Stanislav Sedov <stas@310.ru>
PR: kern/84638
MFC after: 1 week
|
|
|
|
|
| |
Idea from: Stanislav Sedov <stas@310.ru>
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
| |
PR: kern/84659
Submitted by: Benjamin Lutz <benlutz@datacomm.ch>
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
For features list and usage see manual page: geli(8).
Sponsored by: Wheel Sp. z o.o.
http://www.wheel.pl
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
Actually, one cannot setup root file system on RAID3 device, but when
other file system exist in /etc/fstab which are placed on RAID3 device,
boot process will be interrupted when these devices are missing.
MFC after: 3 days
X-MFC-note: MFC only to RELENG_6, as RELENG_5 doesn't have root_mount KPI.
|
|
|
|
|
|
|
|
|
|
|
|
| |
the assumption that performance was more important that beancounter
quality statistics.
As it transpires the microoptimization is not measurable in the
real world and the inconsistent statistics confuse users, so revert
the decision.
MT6 candidate: possibly
MT5 candidate: possibly
|
|
|
|
|
|
|
|
|
|
|
| |
It creates very huge provider (41PB) /dev/gzero.
On BIO_READ request it zero-fills bio_data and on BIO_WRITE it does nothing.
You can also set kern.geom.zero.clear sysctl to 0 to do nothing even for
BIO_READ.
I'm using it for performance testing where it is very helpful.
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
|
| |
to destroy it.
PR: kern/81758
Submitted by: trasz <trasz@buziaczek.pl>
MFC after: 3 days
|
|
|
|
| |
- Implement a gctl handler and the verb "write MBR".
|
|
|
|
|
|
| |
*) Plug a possible memory leak. [1]
[1] obtained from: pjd@.
|