On Sat, 15 Mar 2008, Richard Elling wrote:
>
> My observation, is that each metaslab is, by default, 1 MByte in size. Each
> top-level vdev is allocated by metaslabs. ZFS tries to allocate a top-level
> vdev's metaslab before moving onto another one. So you should see eight
> 128kByte allocs per
Bob Friesenhahn wrote:
> Can someone please describe to me the actual underlying I/O operations
> which occur when a 128K block of data is written to a storage pool
> configured as shown below (with default ZFS block sizes)? I am
> particularly interested in the degree of "striping" across mirr
Can someone please describe to me the actual underlying I/O operations
which occur when a 128K block of data is written to a storage pool
configured as shown below (with default ZFS block sizes)? I am
particularly interested in the degree of "striping" across mirrors
which occurs. This would
Anton B. Rang acm.org> writes:
> Looking at the AMD 690 series manual (well, the family
> register guide), the max payload size value is deliberately
> set to 0 to indicate that the chip only supports 128-byte
> transfers. There is a bit in another register which can be
> set to ignore max-payload
On 3/14/08, Vahid Moghaddasi wrote:
On Fri, Mar 14, 2008 at 11:26 PM, Tim wrote:
replace your LUNs one at a time:
zpool replace -f rd_01 c4t6006048187870150525244353543d0
first_lun_off_dmx-3
zpool replace -f rd_01 c4t6006048187870150525244353942d0
secon
