Hi guys,
I'm trying to implement AFR across 2 servers and I was wondering if there is
any option that would allow me to exclude some subdirectories from replicating
each other. Say I have a directory structure like this:
/var/www/domain1/htdocs
/var/www/domain1/logs
/var/www/domain2/htdocs
/var/www/domain2/logs
....
I want to AFR /var/www across the 2 servers, but exclude the logs directories
from replication. Is there any translator that would help me achieve that?
Any help is appreciated.
Claudiu
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://supercolony.gluster.org/pipermail/gluster-users/attachments/20081115/d455cff6/attachment.html>
well, I''m not sure (maybe one of the devs knows a better answer), but what I''ve done is (using your naming convention): mkdir /var/wwwlogs cd /var/www for i in *; do mv $i/logs /var/wwwlogs/$i;ln -s /var/wwwlogs/$i $i/logs; done; then mount gluster on /var/www so people can view their logs (for a particular server) using the same path, and you can use the same path for your http config. but the web roots are AFRed it''s probably more efficient than using an exclude if one exists, but it may require some changes if you have scripts which create thes "domain#"s automatically. Keith At 01:02 AM 11/15/2008, claudiu ciurdariu wrote:>Hi guys, > >I''m trying to implement AFR across 2 servers and I was wondering if >there is any option that would allow me to exclude some >subdirectories from replicating each other. Say I have a directory >structure like this: > >/var/www/domain1/htdocs >/var/www/domain1/logs >/var/www/domain2/htdocs >/var/www/domain2/logs >.... > >I want to AFR /var/www across the 2 servers, but exclude the logs >directories from replication. Is there any translator that would >help me achieve that? > >Any help is appreciated. > >Claudiu > >_______________________________________________ >Gluster-users mailing list >Gluster-users at gluster.org >http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
well, I''m not sure (maybe one of the devs knows a better answer), but what I''ve done is (using your naming convention): mkdir /var/wwwlogs cd /var/www for i in *; do mv $i/logs /var/wwwlogs/$i;ln -s /var/wwwlogs/$i $i/logs; done; then mount gluster on /var/www so people can view their logs (for a particular server) using the same path, and you can use the same path for your http config. but the web roots are AFRed it''s probably more efficient than using an exclude if one exists, but it may require some changes if you have scripts which create thes "domain#"s automatically. Keith At 01:02 AM 11/15/2008, claudiu ciurdariu wrote:>Hi guys, > >I''m trying to implement AFR across 2 servers and I was wondering if >there is any option that would allow me to exclude some >subdirectories from replicating each other. Say I have a directory >structure like this: > >/var/www/domain1/htdocs >/var/www/domain1/logs >/var/www/domain2/htdocs >/var/www/domain2/logs >.... > >I want to AFR /var/www across the 2 servers, but exclude the logs >directories from replication. Is there any translator that would >help me achieve that? > >Any help is appreciated. > >Claudiu > >_______________________________________________ >Gluster-users mailing list >Gluster-users at gluster.org >http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
well, I'm not sure (maybe one of the devs knows a better answer), but what I've done is (using your naming convention): mkdir /var/wwwlogs cd /var/www for i in *; do mv $i/logs /var/wwwlogs/$i;ln -s /var/wwwlogs/$i $i/logs; done; then mount gluster on /var/www so people can view their logs (for a particular server) using the same path, and you can use the same path for your http config. but the web roots are AFRed it's probably more efficient than using an exclude if one exists, but it may require some changes if you have scripts which create thes "domain#"s automatically. Keith At 01:02 AM 11/15/2008, claudiu ciurdariu wrote:>Hi guys, > >I'm trying to implement AFR across 2 servers and I was wondering if >there is any option that would allow me to exclude some >subdirectories from replicating each other. Say I have a directory >structure like this: > >/var/www/domain1/htdocs >/var/www/domain1/logs >/var/www/domain2/htdocs >/var/www/domain2/logs >.... > >I want to AFR /var/www across the 2 servers, but exclude the logs >directories from replication. Is there any translator that would >help me achieve that? > >Any help is appreciated. > >Claudiu > >_______________________________________________ >Gluster-users mailing list >Gluster-users at gluster.org >http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
well, I''m not sure (maybe one of the devs knows a better answer), but what I''ve done is (using your naming convention): mkdir /var/wwwlogs cd /var/www for i in *; do mv $i/logs /var/wwwlogs/$i;ln -s /var/wwwlogs/$i $i/logs; done; then mount gluster on /var/www so people can view their logs (for a particular server) using the same path, and you can use the same path for your http config. but the web roots are AFRed it''s probably more efficient than using an exclude if one exists, but it may require some changes if you have scripts which create thes "domain#"s automatically. Keith At 01:02 AM 11/15/2008, claudiu ciurdariu wrote:>Hi guys, > >I''m trying to implement AFR across 2 servers and I was wondering if >there is any option that would allow me to exclude some >subdirectories from replicating each other. Say I have a directory >structure like this: > >/var/www/domain1/htdocs >/var/www/domain1/logs >/var/www/domain2/htdocs >/var/www/domain2/logs >.... > >I want to AFR /var/www across the 2 servers, but exclude the logs >directories from replication. Is there any translator that would >help me achieve that? > >Any help is appreciated. > >Claudiu > >_______________________________________________ >Gluster-users mailing list >Gluster-users at gluster.org >http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
Claudiu, You can use unify over afr. And use switch translator to schedule your log files to a subvolume which does not replicate (without afr) and rest of the files to afr. volume unify type cluster/unify option scheduler switch option switch.case <pattern>:<non-replicated-subvolume>;*:<afr-subvolume> option namespace <namespace> subvoumes <non-replicated-subvolume> <afr-subvolume> end-volume -- gowda On Sat, Nov 15, 2008 at 2:32 PM, claudiu ciurdariu <clauc_007 at yahoo.com>wrote:> Hi guys, > > I'm trying to implement AFR across 2 servers and I was wondering if there > is any option that would allow me to exclude some subdirectories from > replicating each other. Say I have a directory structure like this: > > /var/www/domain1/htdocs > /var/www/domain1/logs > /var/www/domain2/htdocs > /var/www/domain2/logs > .... > > I want to AFR /var/www across the 2 servers, but exclude the logs > directories from replication. Is there any translator that would help me > achieve that? > > Any help is appreciated. > > Claudiu > > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users > >-- hard work often pays off after time, but laziness always pays off now -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20081116/e52cf58f/attachment.html>
in this case, the namespace brick should be AFR''ed then correct? would that break things if log files are on some clients and not others? At 08:57 PM 11/15/2008, Basavanagowda Kanur wrote:>Claudiu, > You can use unify over afr. And use switch translator to schedule > your log files to a subvolume which does not replicate (without > afr) and rest of the files to afr. > >volume unify > type cluster/unify > option scheduler switch > option switch.case <pattern>:<non-replicated-subvolume>;*:<afr-subvolume> > option namespace <namespace> > subvoumes <non-replicated-subvolume> <afr-subvolume> >end-volume > >-- >gowda > >On Sat, Nov 15, 2008 at 2:32 PM, claudiu ciurdariu ><<mailto:clauc_007 at yahoo.com>clauc_007 at yahoo.com> wrote: >Hi guys, > >I''m trying to implement AFR across 2 servers and I was wondering if >there is any option that would allow me to exclude some >subdirectories from replicating each other. Say I have a directory >structure like this: > >/var/www/domain1/htdocs >/var/www/domain1/logs >/var/www/domain2/htdocs >/var/www/domain2/logs >.... > >I want to AFR /var/www across the 2 servers, but exclude the logs >directories from replication. Is there any translator that would >help me achieve that? > >Any help is appreciated. > >Claudiu > > >_______________________________________________ >Gluster-users mailing list ><mailto:Gluster-users at gluster.org>Gluster-users at gluster.org >http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users > > > > >-- >hard work often pays off after time, but laziness always pays off now >_______________________________________________ >Gluster-users mailing list >Gluster-users at gluster.org >http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
in this case, the namespace brick should be AFR''ed then correct? would that break things if log files are on some clients and not others? At 08:57 PM 11/15/2008, Basavanagowda Kanur wrote:>Claudiu, > You can use unify over afr. And use switch translator to schedule > your log files to a subvolume which does not replicate (without > afr) and rest of the files to afr. > >volume unify > type cluster/unify > option scheduler switch > option switch.case <pattern>:<non-replicated-subvolume>;*:<afr-subvolume> > option namespace <namespace> > subvoumes <non-replicated-subvolume> <afr-subvolume> >end-volume > >-- >gowda > >On Sat, Nov 15, 2008 at 2:32 PM, claudiu ciurdariu ><<mailto:clauc_007 at yahoo.com>clauc_007 at yahoo.com> wrote: >Hi guys, > >I''m trying to implement AFR across 2 servers and I was wondering if >there is any option that would allow me to exclude some >subdirectories from replicating each other. Say I have a directory >structure like this: > >/var/www/domain1/htdocs >/var/www/domain1/logs >/var/www/domain2/htdocs >/var/www/domain2/logs >.... > >I want to AFR /var/www across the 2 servers, but exclude the logs >directories from replication. Is there any translator that would >help me achieve that? > >Any help is appreciated. > >Claudiu > > >_______________________________________________ >Gluster-users mailing list ><mailto:Gluster-users at gluster.org>Gluster-users at gluster.org >http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users > > > > >-- >hard work often pays off after time, but laziness always pays off now >_______________________________________________ >Gluster-users mailing list >Gluster-users at gluster.org >http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
in this case, the namespace brick should be AFR''ed then correct? would that break things if log files are on some clients and not others? At 08:57 PM 11/15/2008, Basavanagowda Kanur wrote:>Claudiu, > You can use unify over afr. And use switch translator to schedule > your log files to a subvolume which does not replicate (without > afr) and rest of the files to afr. > >volume unify > type cluster/unify > option scheduler switch > option switch.case <pattern>:<non-replicated-subvolume>;*:<afr-subvolume> > option namespace <namespace> > subvoumes <non-replicated-subvolume> <afr-subvolume> >end-volume > >-- >gowda > >On Sat, Nov 15, 2008 at 2:32 PM, claudiu ciurdariu ><<mailto:clauc_007 at yahoo.com>clauc_007 at yahoo.com> wrote: >Hi guys, > >I''m trying to implement AFR across 2 servers and I was wondering if >there is any option that would allow me to exclude some >subdirectories from replicating each other. Say I have a directory >structure like this: > >/var/www/domain1/htdocs >/var/www/domain1/logs >/var/www/domain2/htdocs >/var/www/domain2/logs >.... > >I want to AFR /var/www across the 2 servers, but exclude the logs >directories from replication. Is there any translator that would >help me achieve that? > >Any help is appreciated. > >Claudiu > > >_______________________________________________ >Gluster-users mailing list ><mailto:Gluster-users at gluster.org>Gluster-users at gluster.org >http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users > > > > >-- >hard work often pays off after time, but laziness always pays off now >_______________________________________________ >Gluster-users mailing list >Gluster-users at gluster.org >http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
Keith, Replies inline. On Sun, Nov 16, 2008 at 10:51 AM, Keith Freedman <freedman at freeformit.com>wrote:> in this case, the namespace brick should be AFR'ed then correct?namespace volume can be anything (depending on your needs). namespace contains only directory entries and no other data.> would that break things if log files are on some clients and not others?no. mount-point will show all the files, irrespective of whether they are scheduled to AFR or direct posix subvolume .> > > At 08:57 PM 11/15/2008, Basavanagowda Kanur wrote: > >> Claudiu, >> You can use unify over afr. And use switch translator to schedule your >> log files to a subvolume which does not replicate (without afr) and rest of >> the files to afr. >> >> volume unify >> type cluster/unify >> option scheduler switch >> option switch.case <pattern>:<non-replicated-subvolume>;*:<afr-subvolume> >> option namespace <namespace> >> subvoumes <non-replicated-subvolume> <afr-subvolume> >> end-volume >> >> -- >> gowda >> >> On Sat, Nov 15, 2008 at 2:32 PM, claudiu ciurdariu <<mailto: >> clauc_007 at yahoo.com>clauc_007 at yahoo.com> wrote: >> Hi guys, >> >> I'm trying to implement AFR across 2 servers and I was wondering if there >> is any option that would allow me to exclude some subdirectories from >> replicating each other. Say I have a directory structure like this: >> >> /var/www/domain1/htdocs >> /var/www/domain1/logs >> /var/www/domain2/htdocs >> /var/www/domain2/logs >> .... >> >> I want to AFR /var/www across the 2 servers, but exclude the logs >> directories from replication. Is there any translator that would help me >> achieve that? >> >> Any help is appreciated. >> >> Claudiu >> >> >> _______________________________________________ >> Gluster-users mailing list >> <mailto:Gluster-users at gluster.org>Gluster-users at gluster.org >> http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users >> >> >> >> >> -- >> hard work often pays off after time, but laziness always pays off now >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users at gluster.org >> http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users >> > >-- gowda -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20081116/2db6d89a/attachment.html>
so I got a strange error in gluster logs telling me that I need to delete a directory (tree) from all but the preferred node. gluster 1.4.0qa57 so I deleted the thing from the undelying filesystem on one of my AFR''ed nodes I did the find command and it mostly rebuilt and autohealed. however, it got hung up anytime it ran into a symlink to a file that either doesn''t exist OR does exist but the destination file exists outside of the underlying filesystem. Either seems to be pretty undesirable. I presume this is a bug. Keith
so I got a strange error in gluster logs telling me that I need to delete a directory (tree) from all but the preferred node. gluster 1.4.0qa57 so I deleted the thing from the undelying filesystem on one of my AFR''ed nodes I did the find command and it mostly rebuilt and autohealed. however, it got hung up anytime it ran into a symlink to a file that either doesn''t exist OR does exist but the destination file exists outside of the underlying filesystem. Either seems to be pretty undesirable. I presume this is a bug. Keith
so I got a strange error in gluster logs telling me that I need to delete a directory (tree) from all but the preferred node. gluster 1.4.0qa57 so I deleted the thing from the undelying filesystem on one of my AFR''ed nodes I did the find command and it mostly rebuilt and autohealed. however, it got hung up anytime it ran into a symlink to a file that either doesn''t exist OR does exist but the destination file exists outside of the underlying filesystem. Either seems to be pretty undesirable. I presume this is a bug. Keith
There is a bug fix in self-healing symlinks in patch-628. Can you try the revision off tla? I tried to recreate a similar scenario as you mentioned and things worked fine for me. The log message there too has been fixed (it was not right to delete files in that case from the backend). Thank you for reporting! avati 2008/11/17 Keith Freedman <freedman at freeformit.com>> so I got a strange error in gluster logs telling me that I need to > delete a directory (tree) from all but the preferred node. > > gluster 1.4.0qa57 > > so I deleted the thing from the undelying filesystem on one of my AFR'ed > nodes > > I did the find command and it mostly rebuilt and autohealed. > however, it got hung up anytime it ran into a symlink to a file that > either doesn't exist OR > does exist but the destination file exists outside of the underlying > filesystem. > > Either seems to be pretty undesirable. > > I presume this is a bug. > > Keith > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20081117/a4e985ec/attachment.html>
I''m testing now with qa60, so hopefully that includes the patches you specified. I''m testing the symbolic link issue as well as a couple other problems. here are my findings (my config is at the bottom of the email, but it''s a basic 2 server AFR config with each other as clients and no other clients). 1) symlinks I created a symlink to a non-existing file. this went fine and appeared on both underlying filesystems. I removed the link from one of the underlying filesystems and tried to do an ls of it here''s the results: ]# ls -al /home/testlink /bin/ls: /home/testlink: No such file or directory /bin/ls: cannot read symbolic link /home/testlink: No such file or directory lrwxrwxrwx 1 root root 10 2008-11-17 21:08 /home/testlink gluster logs: 2008-11-17 21:08:41 E [posix.c:1074:posix_chmod] home1: lstat on /gluster/home/testlink failed: No such file or directory 2008-11-17 21:08:41 E [afr-self-heal-metadata.c:296:afr_sh_metadata_sync_cbk] home: setting attributes failed for /testlink on posix-locks-home1 (No such file or directory) 2008-11-17 21:08:41 W [posix.c:1240:posix_utimens] home1: utimes on /gluster/home/testlink: No such file or directory 2008-11-17 21:08:41 E [afr-self-heal-metadata.c:296:afr_sh_metadata_sync_cbk] home: setting attributes failed for /testlink on posix-locks-home1 (No such file or directory) 2008-11-17 21:08:41 W [afr-self-heal-metadata.c:97:afr_sh_metadata_done] home: completed self heal of /testlink 2008-11-17 21:08:41 E [posix.c:2182:posix_getxattr] home1: listxattr failed on /gluster/home/testlink: No such file or directory I can then remove the link from gluster and re-created it with gluster, but again, it creates properly if it''s not on any node, but once it''s on one, and it''s not on the other it doesn''t properly auto-heal. the problem here is when you bring a new empty filesystem online it should auto-heal and ultimately sync all the data to the new node, but it can''t in this scenario. 2) one of the AFR servers goes offline the permissions seem to be wrong on all the files until the other AFR server comes back online --this problem existed in qa 56 and 57 but seems resolved in 60 I''ll keep an eye on things and report if I find anything else. Things seem to be shaping up quite nicely. Keith At 10:29 AM 11/17/2008, Anand Avati wrote:>There is a bug fix in self-healing symlinks in patch-628. Can you >try the revision off tla? I tried to recreate a similar scenario as >you mentioned and things worked fine for me. The log message there >too has been fixed (it was not right to delete files in that case >from the backend). Thank you for reporting! > >avati > >2008/11/17 Keith Freedman ><<mailto:freedman at freeformit.com>freedman at freeformit.com> >so I got a strange error in gluster logs telling me that I need to >delete a directory (tree) from all but the preferred node. > >gluster 1.4.0qa57 > >so I deleted the thing from the undelying filesystem on one of my AFR''ed nodes > >I did the find command and it mostly rebuilt and autohealed. >however, it got hung up anytime it ran into a symlink to a file that >either doesn''t exist OR >does exist but the destination file exists outside of the underlying >filesystem. > >Either seems to be pretty undesirable. > >I presume this is a bug. > >Keith >
I''m testing now with qa60, so hopefully that includes the patches you specified. I''m testing the symbolic link issue as well as a couple other problems. here are my findings (my config is at the bottom of the email, but it''s a basic 2 server AFR config with each other as clients and no other clients). 1) symlinks I created a symlink to a non-existing file. this went fine and appeared on both underlying filesystems. I removed the link from one of the underlying filesystems and tried to do an ls of it here''s the results: ]# ls -al /home/testlink /bin/ls: /home/testlink: No such file or directory /bin/ls: cannot read symbolic link /home/testlink: No such file or directory lrwxrwxrwx 1 root root 10 2008-11-17 21:08 /home/testlink gluster logs: 2008-11-17 21:08:41 E [posix.c:1074:posix_chmod] home1: lstat on /gluster/home/testlink failed: No such file or directory 2008-11-17 21:08:41 E [afr-self-heal-metadata.c:296:afr_sh_metadata_sync_cbk] home: setting attributes failed for /testlink on posix-locks-home1 (No such file or directory) 2008-11-17 21:08:41 W [posix.c:1240:posix_utimens] home1: utimes on /gluster/home/testlink: No such file or directory 2008-11-17 21:08:41 E [afr-self-heal-metadata.c:296:afr_sh_metadata_sync_cbk] home: setting attributes failed for /testlink on posix-locks-home1 (No such file or directory) 2008-11-17 21:08:41 W [afr-self-heal-metadata.c:97:afr_sh_metadata_done] home: completed self heal of /testlink 2008-11-17 21:08:41 E [posix.c:2182:posix_getxattr] home1: listxattr failed on /gluster/home/testlink: No such file or directory I can then remove the link from gluster and re-created it with gluster, but again, it creates properly if it''s not on any node, but once it''s on one, and it''s not on the other it doesn''t properly auto-heal. the problem here is when you bring a new empty filesystem online it should auto-heal and ultimately sync all the data to the new node, but it can''t in this scenario. 2) one of the AFR servers goes offline the permissions seem to be wrong on all the files until the other AFR server comes back online --this problem existed in qa 56 and 57 but seems resolved in 60 I''ll keep an eye on things and report if I find anything else. Things seem to be shaping up quite nicely. Keith At 10:29 AM 11/17/2008, Anand Avati wrote:>There is a bug fix in self-healing symlinks in patch-628. Can you >try the revision off tla? I tried to recreate a similar scenario as >you mentioned and things worked fine for me. The log message there >too has been fixed (it was not right to delete files in that case >from the backend). Thank you for reporting! > >avati > >2008/11/17 Keith Freedman ><<mailto:freedman at freeformit.com>freedman at freeformit.com> >so I got a strange error in gluster logs telling me that I need to >delete a directory (tree) from all but the preferred node. > >gluster 1.4.0qa57 > >so I deleted the thing from the undelying filesystem on one of my AFR''ed nodes > >I did the find command and it mostly rebuilt and autohealed. >however, it got hung up anytime it ran into a symlink to a file that >either doesn''t exist OR >does exist but the destination file exists outside of the underlying >filesystem. > >Either seems to be pretty undesirable. > >I presume this is a bug. > >Keith >
I''m testing now with qa60, so hopefully that includes the patches you specified. I''m testing the symbolic link issue as well as a couple other problems. here are my findings (my config is at the bottom of the email, but it''s a basic 2 server AFR config with each other as clients and no other clients). 1) symlinks I created a symlink to a non-existing file. this went fine and appeared on both underlying filesystems. I removed the link from one of the underlying filesystems and tried to do an ls of it here''s the results: ]# ls -al /home/testlink /bin/ls: /home/testlink: No such file or directory /bin/ls: cannot read symbolic link /home/testlink: No such file or directory lrwxrwxrwx 1 root root 10 2008-11-17 21:08 /home/testlink gluster logs: 2008-11-17 21:08:41 E [posix.c:1074:posix_chmod] home1: lstat on /gluster/home/testlink failed: No such file or directory 2008-11-17 21:08:41 E [afr-self-heal-metadata.c:296:afr_sh_metadata_sync_cbk] home: setting attributes failed for /testlink on posix-locks-home1 (No such file or directory) 2008-11-17 21:08:41 W [posix.c:1240:posix_utimens] home1: utimes on /gluster/home/testlink: No such file or directory 2008-11-17 21:08:41 E [afr-self-heal-metadata.c:296:afr_sh_metadata_sync_cbk] home: setting attributes failed for /testlink on posix-locks-home1 (No such file or directory) 2008-11-17 21:08:41 W [afr-self-heal-metadata.c:97:afr_sh_metadata_done] home: completed self heal of /testlink 2008-11-17 21:08:41 E [posix.c:2182:posix_getxattr] home1: listxattr failed on /gluster/home/testlink: No such file or directory I can then remove the link from gluster and re-created it with gluster, but again, it creates properly if it''s not on any node, but once it''s on one, and it''s not on the other it doesn''t properly auto-heal. the problem here is when you bring a new empty filesystem online it should auto-heal and ultimately sync all the data to the new node, but it can''t in this scenario. 2) one of the AFR servers goes offline the permissions seem to be wrong on all the files until the other AFR server comes back online --this problem existed in qa 56 and 57 but seems resolved in 60 I''ll keep an eye on things and report if I find anything else. Things seem to be shaping up quite nicely. Keith At 10:29 AM 11/17/2008, Anand Avati wrote:>There is a bug fix in self-healing symlinks in patch-628. Can you >try the revision off tla? I tried to recreate a similar scenario as >you mentioned and things worked fine for me. The log message there >too has been fixed (it was not right to delete files in that case >from the backend). Thank you for reporting! > >avati > >2008/11/17 Keith Freedman ><<mailto:freedman at freeformit.com>freedman at freeformit.com> >so I got a strange error in gluster logs telling me that I need to >delete a directory (tree) from all but the preferred node. > >gluster 1.4.0qa57 > >so I deleted the thing from the undelying filesystem on one of my AFR''ed nodes > >I did the find command and it mostly rebuilt and autohealed. >however, it got hung up anytime it ran into a symlink to a file that >either doesn''t exist OR >does exist but the destination file exists outside of the underlying >filesystem. > >Either seems to be pretty undesirable. > >I presume this is a bug. > >Keith >