> patch 563 now uses "option read-node" and not "option read-schedule" > We thought about "option read-node child1,child3" but this wont really > be used in the sense that users would want to read either from local > storage or all the children. But there might be a case where one of the > sobvols might be a low end machine where we dont want to schedule > reads. Still thinking if it is worth implementing this particular feature. I think you should rename it to 'option read-subvolumes' just to be consistant with the naming conventions. avati -- It always takes longer than you expect, even when you take into account Hofstadter's Law. -- Hofstadter's Law
