Lines Matching refs:segment

24 	  the related segment and not the whole drive.
28 	  writes to the segment array on-media even through a synchronization
41 	* Implement a segment descriptor array for each drive in the
43 	  example, 128MB per segment.  The segment array would be stored
45 	  store the segment state for BOTH disks.
47 	  Thus a 1TBx2 mirror would have 8192x4 segments (4 segment
48 	  descriptors for each logical segment).  The segment descriptor
52 	  A segment descriptor would be, oh I don't know... probably
55 	  Why does each disk need to store a segment descriptor for both
60 	* The state of the segment descriptor must be consulted when reading
73 	  MEDIA_READ_DEGRADED	0: No I/O read error occured on this segment
74 				1: I/O read error(s) occured on this segment
76 	  MEDIA_WRITE_DEGRADED	0: No I/O write error occured on this segment
77 				1: I/O write error(s) occured on this segment
81 				1: Mastership operation for this segment
87 	  UNINITIALIZED		0: The segment contains normal data.
89 				1: The entire segment is empty and should
99 				recopied after the related segment has been
104 				recopied after the related segment has been
108 	  segment descriptor as well in order to resolve certain situations.
110 	* Since updating a segment descriptor on-media is expensive
112 	  course a nasty seek), segment descriptors on-media are updated
114 	  meaning the segment is undergoing active writing.
116 	  Changing a segment descriptor from unstable to stable can be
123     The actions taken will be based on the segment state for the segment
124     involved in the I/O.  Any I/O which crosses a segment boundary would
127     Remember there are four descriptors for each segment, two on each drive:
141     only one drive is operational then the state stored in the segment
155 	* If doing a write operation and the segment is marked UNITIALIZED
156 	  the entire segment must be zero-filled and the bit cleared prior
219 	  The segment array on the drive(s) is used to determine what
222 	* Synchronization occurs when the segment for one drive is
223 	  marked MASTER and the segment for the other drive is not.
226 	  for any given segment) a manual intervention is required to
236 	  drives to hold a header and the segment array, making the
273 	If set any read I/O to the related segment is simply zero-filled.
275 	When writing we have to zero-fill the segment (write zeros to the
276 	whole 128MB segment) and then clear the UNINITIALIZED flag before
282 	segment down into 4MB pieces and only zero-fill/write portions
283 	of the 128MB segment instead of having to do the whole segment.