Hi Sam, Comments are inlined. On Jan 23, 2008 1:47 AM, Sam Douglas <sam.douglas32@xxxxxxxxx> wrote: > Hello, > > If you attempt to rename a file on a unify subvolume that is unavailable, > the operation will fail, however the file in the namespace will be renamed > regardless. When the volume comes back online, the old file will be > self-healed > back into the namespace, and the renamed file will not be present on any > subvolumes. > > For example: > [file /clusterfs/foo exists on a currently inaccessible volume and in > the namespace] > > # mv /clusterfs/foo /clusterfs/bert > mv: cannot move `/clusterfs/foo' to `/clusterfs/bert': No such file or > directory > [exitstatus = 1] Its the intended behaviour since 'mv oldfile newfile' has 'failed'. But a small doubt, does 'ls' in the directory rename was performed (here cluster), show newfile or oldfile or both? > > > -- Sam Douglas > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxx > http://lists.nongnu.org/mailman/listinfo/gluster-devel > -- Raghavendra G A centipede was happy quite, until a toad in fun, Said, "Prey, which leg comes after which?", This raised his doubts to such a pitch, He fell flat into the ditch, Not knowing how to run. -Anonymous
