David, You can use the script "snapmerge" that is included in the distribution to copy changes from your highest priority writable branch to another branch. This will work assuming that the other five disks will be one large array, if they have separate data, you'll need to write something more complex to decide which of the five disks the changes should propagate to.
I'm not sure how much the disks will spin down, because they will still need to be accessed for read-only operations. Charles On Tue, 2005-10-04 at 15:50 +0200, David Guyon Martin wrote: > Hello, > > I look forward using UnionFS for this purpose: > On a six disks array, 5 disks are remounted read-only, and the last > one get all the writings, until we need to commit the changes to the > first 5 disks. > The aim is to spin down those disks most of the time, waking them up > for a batch write of the changes. > > 1st part: > I understand UnionFS can allow us to virtually write to a read-only FS > on a hard disk. > > 2nd part: > Can someone tell us if there is any way to write back the changes to > the source FS after a remount read-write ? > > Thanks, > David G.M. > _______________________________________________ > unionfs mailing list > [email protected] > http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs _______________________________________________ unionfs mailing list [email protected] http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
