>>> 1. AFR is up >>> 2. touch file f1 >>> 3. brick1 crashes >>> 4. ls on mount point, f1 exists and everything is normal (ls read from >>> brick2) >>> 5. file system repair removes f1 from brick1 Glusterfs removes f1 from brick1? Or do you manually remove it? Could you also check with a later release. As a related bug was fixed. Thanks >>> 6. gclusterfsd start on brick1 >>> 7. ls on mount point does not show f1 anymore (ls read only from brick1?) >>> 8. cat f1 on mount point replicates file and it becomes visible On Fri, Jul 4, 2008 at 7:03 AM, baggio liu <baggioss at gmail.com> wrote: > Hi, > A file can't "ls " ,but can "less ". > I think this action is a little weird. If this action can not be > supp
