On Wed, Jul 12, 2006 at 02:45:40PM -0700, Darren Dunham wrote: > > There may be several parity sectors per row so adding another column doesn't > > work. > > But presumably it would be possible to use additional columns for future > writes?
I guess that could be made to work, but then the data on the disk becomes much (much much) more difficult to interpret because you have some rows which are effectively one width and others which are another (ad infinitum). It also doesn't really address the issue since you assume that you want to add space because the disks are getting full, but this scheme, as you mention, only applies the new width to empty rows. I'm not sure I even agree with the notion that this is a real problem (and if it is, I don't think is easily solved). Stripe widths are a function of the expected failure rate and fault domains of the system which tend to be static in nature. A coarser solution would be to create a new pool where you zfs send/zfs recv the filesystems of the old pool. Adam -- Adam Leventhal, Solaris Kernel Development http://blogs.sun.com/ahl _______________________________________________ zfs-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
