16.0E ExpandSize? -- New Server
Steven Hartland
killing at multiplay.co.uk
Tue Jan 31 18:30:34 UTC 2017
Your issue is the reported vdev_max_asize > vdev_asize:
vdev_max_asize: 11947471798272
vdev_asize: 11947478089728
max asize is smaller than asize by 6291456
For raidz1 Xsize should be the smallest disk Xsize * disks so:
1991245299712 * 6 = 11947471798272
So your max asize looks right but asize looks too big
Expand Size is calculated by:
if (vd->vdev_aux == NULL && tvd != NULL && vd->vdev_max_asize != 0) {
vs->vs_esize = P2ALIGN(vd->vdev_max_asize - vd->vdev_asize,
1ULL << tvd->vdev_ms_shift);
}
So the question is why is asize too big?
Given you seem to have some random disk sizes do you have auto expand
turned on?
On 31/01/2017 17:39, Larry Rosenman wrote:
> vdev_path: n/a, vdev_max_asize: 11947471798272, vdev_asize: 11947478089728
More information about the freebsd-fs
mailing list