summaryrefslogtreecommitdiffstats
path: root/sys/geom
Commit message (Collapse)AuthorAgeFilesLines
* - Prevent error status leak if write to some of the RAID1/1E volume disksmav2012-05-112-4/+29
| | | | | | | failed while write to some other succeeded. Instead mark disk as failed. - Make RAID1E less aggressive in failing disks to avoid volume breakage. MFC after: 2 weeks
* Clarify error that geli generateseadler2012-05-091-3/+4
| | | | | | | | | | when it finds corrupt data. PR: kern/165695 Submitted by: Robert Simmons <rsimmons0@gmail.com> Reviewed by: pjd Approved by: cperciva MFC after: 1 week
* Remove some hardcoded constants from code.mav2012-05-061-8/+11
|
* Plug small memory leaks.mav2012-05-062-1/+5
|
* Add support for RAID5R. Slightly improve support for RAIDMDF.mav2012-05-064-21/+60
|
* Fix `gmultipath configure` for big-endian machines.mav2012-05-061-9/+10
| | | | MFC after: 1 week
* Fix bug causing memory corruption and panics with big-endian metadata.mav2012-05-041-1/+1
|
* Implement read-only support for volumes in optimal state (without usingmav2012-05-042-36/+72
| | | | redundancy) for the following RAID levels: RAID4/5E/5EE/6/MDF.
* Add optional -o argument to the `graid label ` to specify some metadatamav2012-05-035-14/+63
| | | | | format options. Use it for specifying byte order for the DDF metadata: big-endian defined by specification and little-endian used by Adaptec.
* Improve spare disks support. Unluckily, for some reason Adaptec 1430SAmav2012-05-011-68/+134
| | | | | RAID BIOS doesn't want to understand spare disks created by graid. But at least spares created by BIOS are working fine now.
* Implement volume deletion if disk has more then one partition.mav2012-05-011-30/+37
|
* Improve DDF metadata writing.mav2012-05-011-54/+92
|
* Add to GEOM RAID class module, supporting the DDF metadata format, asmav2012-04-302-0/+3245
| | | | | | | | | | | | | | | defined by the SNIA Common RAID Disk Data Format Specification v2.0. Supports multiple volumes per array and multiple partitions per disk. Supports standard big-endian and Adaptec's little-endian byte ordering. Supports all single-layer RAID levels. Dual-layer RAID levels except RAID10 are not supported now because of GEOM RAID design limitations. Some work is still to be done, but the present code already manages basic interoperation with RAID BIOS of the Adaptec 1430SA SATA RAID controller. MFC after: 1 month Sponsored by: iXsystems, Inc.
* s/gmirror/graid/mav2012-04-291-2/+2
|
* Fix RAID5 level names changed at r234603.mav2012-04-275-6/+6
|
* Fix copy-paste typo in r234603.mav2012-04-231-2/+2
| | | | Submitted by: kan
* Add names for all primary RAID levels defined by DDF 2.0 specification.mav2012-04-234-19/+180
|
* Add sos@ copyrights to RAID metadata modules, respecting his efforts inmav2012-04-235-0/+5
| | | | decoding metadata formats in ataraid(4) code.
* Add to GEOM RAID class module for reading non-degraded RAID5 volumes andmav2012-04-198-29/+468
| | | | | | | | some environment to differentiate 4 possible RAID5 on-disk layouts. Tested with Intel and AMD RAID BIOSes. MFC after: 2 weeks
* VMware environments are not unusual now. Add VMware partitions recognitionmarck2012-04-184-0/+14
| | | | | | | | (both MBR for ESXi <= 4.1 and GPT for ESXi 5) to g_part. Reviewed by: ae Approved by: ae MFC after: 2 weeks
* Some improvements to GEOM MULTIPATH:mav2012-04-181-21/+95
| | | | | | | | | | | | | | | | - Implement "configure" command to allow switching operation mode of running device on-fly without destroying and recreation. - Implement Active/Read mode as hybrid of Active/Active and Active/Passive. In this mode all paths not marked FAIL may handle reads same time, but unlike Active/Active only one path handles write requests at any point in time. It allows to closer follow original write request order if above layers need it for data consistency (not waiting for requisite write completion before sending dependent write). - Hide duplicate messages about device status change. - Remove periodic thread wake up with 10Hz rate. MFC after: 2 weeks Sponsored by: iXsystems, Inc.
* Expand locking around identification of filesystem mount point whenmckusick2012-04-081-5/+17
| | | | | | | accounting for I/O counts at completion of I/O operation. Also switch from using global devmtx to vnode mutex to reduce contention. Suggested and reviewed by: kib
* VMDB offset should be greater than logical volume size only for MBR.ae2012-03-291-1/+1
|
* Do proper cleanup for the GPT case when an error occurs.ae2012-03-291-14/+19
|
* Keep track of the mount point associated with a special devicemckusick2012-03-281-1/+30
| | | | | | | | | | | | | | | | | to enable the collection of counts of synchronous and asynchronous reads and writes for its associated filesystem. The counts are displayed using `mount -v'. Ensure that buffers used for paging indicate the vnode from which they are operating so that counts of paging I/O operations from the filesystem are collected. This checkin only adds the setting of the mount point for the UFS/FFS filesystem, but it would be trivial to add the setting and clearing of the mount point at filesystem mount/unmount time for other filesystems too. Reviewed by: kib
* Check that scheme is not already registered. This may happens when aae2012-03-231-7/+16
| | | | | | | | | | | | KLD is preloaded with loader(8) and leads to infinity loops. Also do not return EEXIST error code from MOD_LOAD handler, because we have undocumented(?) ability replace kernel's module with preloaded one. And if we have so, then preloaded module will be initialized first. Thus error in MOD_LOAD handler will be triggered for the kernel. PR: kern/165573 MFC after: 3 weeks
* Add CTLFLAG_TUN to sysctls.ae2012-03-191-4/+4
| | | | MFC after: 1 month
* Add new GEOM_PART_LDM module that implements the Logical Disk Managerae2012-03-191-0/+1504
| | | | | | | | | | | | | | | | | scheme. The LDM is a logical volume manager for MS Windows NT and it is also known as dynamic volumes. It supports about 2000 partitions and also provides the capability for software RAID implementations. This version implements only partitioning scheme capability and based on the linux-ntfs project documentation and several publications across the Web. NOTE: JBOD, RAID0 and RAID5 volumes aren't supported. An access to the LDM metadata is read-only. When LDM is on the disk partitioned with MBR we can also destroy metadata. For the GPT partitioned disks destroy action is not supported. Reviewed by: ivoras (previous version) MFC after: 1 month
* Make kern.geom.part node not static. Also add CTLFLAG_TUN to theae2012-03-191-3/+4
| | | | | | check_integrity sysctl. MFC after: 1 month
* Add MODULE_DEPEND() to geom_part modules.ae2012-03-152-1/+3
| | | | MFC after: 2 weeks
* Remove unactionable message about label geometryemaste2012-03-081-7/+0
| | | | | | | | It's not clear to a user what they should do after seeing the "geometry does not match label" kernel message, and it does not appear to present a problem in practice. Thus, just remove the messages. Approved by: marcel
* If nested scheme allows dump kernel to its partition, we may allowae2012-02-201-2/+5
| | | | | | dump for the parent partition too. MFC after: 2 weeks
* Add alias for the partition type 0x0f. Now "ebr" name is used for bothae2012-02-201-0/+1
| | | | | | | types 0x05 and 0x0f, but 0x05 is preferred and used when partition is created with "gpart add -t ebr ...". This should keep EBR partitions accessible after r231754 for those, who have EBR on the partition with type 0x0f.
* Add additional check to EBR probe and create methods:ae2012-02-151-8/+19
| | | | | | | | | | | | don't try probe and create EBR scheme when parent partition type is not "ebr". This fixes error messages about corrupted EBR for some partitions where is actually another partition scheme. NOTE: if you have EBR on the partition with different than "ebr" (0x05) type, then you will lost access to partitions until it will be changed. MFC after: 2 weeks
* Add PART::type attribute handler. It returns partition type as string.ae2012-02-151-0/+4
| | | | MFC after: 2 weeks
* Add alias for the partition with type 0x42 to the MBR scheme.ae2012-02-101-0/+1
| | | | MFC after: 1 week
* Let's be more realistic and limit maximum number of partition to 4k.ae2012-02-101-1/+1
| | | | MFC after: 1 week
* Current implementations of sync(2) and syncer vnode fsync() VOP useskib2012-02-061-10/+3
| | | | | | | | | | | | | | | | | | | | | | mnt_noasync counter to temporary remove MNTK_ASYNC mount option, which is needed to guarantee a synchronous completion of the initiated i/o before syscall or VOP return. Global removal of MNTK_ASYNC option is harmful because not only i/o started from corresponding thread becomes synchronous, but all i/o is synchronous on the filesystem which is initiated during sync(2) or syncer activity. Instead of removing MNTK_ASYNC from mnt_kern_flag, provide a local thread flag to disable async i/o for current thread only. Use the opportunity to move DOINGASYNC() macro into sys/vnode.h and consistently use it through places which tested for MNTK_ASYNC. Some testing demonstrated 60-70% improvements in run time for the metadata-intensive operations on async-mounted UFS volumes, but still with great deviation due to other reasons. Reviewed by: mckusick Tested by: scottl MFC after: 2 weeks
* Correct typo in comment (numbver)emaste2012-02-041-1/+1
|
* The scheme code may not know about some inconsistency in the metadata.ae2012-02-011-0/+3
| | | | | | So, add an integrity check after recovery attempt. MFC after: 1 week
* Avoid to check the same cache line/variable from all the lockingattilio2012-01-284-0/+4
| | | | | | | | | | | | | | | | primitives by breaking stop_scheduler into a per-thread variable. Also, store the new td_stopsched very close to td_*locks members as they will be accessed mostly in the same codepaths as td_stopsched and this results in avoiding a further cache-line pollution, possibly. STOP_SCHEDULER() was pondered to use a new 'thread' argument, in order to take advantage of already cached curthread, but in the end there should not really be a performance benefit, while introducing a KPI breakage. In collabouration with: flo Reviewed by: avg MFC after: 3 months (or never) X-MFC: r228424
* Experimental support for booting CHRP-type PowerPC systems from hard disks.nwhitehorn2012-01-251-0/+1
|
* Allow an MBR primary or extended Linux swap partition to be specifiedtruckman2012-01-132-4/+6
| | | | | | | | | as the system dump device. This was already allowed for GPT. The Linux swap metadata at the beginning of the partition should not be disturbed because the crash dump is written at the end. Reviewed by: alfred, pjd, marcel MFC after: 2 weeks
* Add support for >2TB disks in GEOM RAID for Intel metadata format.jimharris2012-01-091-49/+122
| | | | | | Reviewed by: mav Approved by: scottl MFC after: 1 week
* GEOM_UNCOMPRESS module, can be used with uzip images and with new ulzma images.ray2012-01-041-0/+670
| | | | Approved by: adrian (mentor)
* replace uses of libkern gets with cngetsavg2011-12-171-1/+2
| | | | MFC after: 2 months
* Close race between geom destruction on g_vfs_close() when softc destroyedmav2011-12-021-1/+3
| | | | | | and g_vfs_orphan() call that tries to access softc, intruced at r227015. PR: kern/162997
* Add an ability to increase number of allocated APM entries when weae2011-11-281-30/+47
| | | | | | | | have reserved free space in the APM area. Also instead of one write request per each APM entry, use MAXPHY sized writes when we are updating APM. MFC after: 1 month
* The size of APM could be bigger than number of already allocated entries.ae2011-11-281-1/+1
| | | | | | And the first usable sector should not start from the inside of APM area. MFC after: 1 month
* Temporary revert r227009 to fix freeze on UP systems without PREEMPTION.mav2011-11-141-27/+12
| | | | | | | | | | | Before r215687, if some withered geom or provider could not be destroyed, g_event thread went to sleep for 0.1s before retrying. After that change it is just restarting immediately. r227009 made orphaned (withered) provider to not detach immediately, but only after context switch. That made loop inside g_event thread infinite on UP systems without PREEMPTION. To address original problem with possible dead lock addressed by r227009 we have to fix r215687 change first, that needs some time to think and test.
OpenPOWER on IntegriCloud