bugGluster - Bugs: bug #20838, Recursive symlinks

 
 

bug #20838: Recursive symlinks

Submitted by:  Bruce <hook>
Submitted on:  Sun 19 Aug 2007 11:24:39 PM UTC  
 
Category: GlusterFSSeverity: 3 - Normal
Priority: 5 - NormalItem Group: Improper behaviour
Status: Works For MePrivacy: Public
Assigned to: NoneOriginator Name: 
Open/Closed: ClosedRelease: 
Operating System: GNU/LinuxReproducibility: None

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Thu 06 Dec 2007 12:51:45 PM UTC, comment #5:

forgot to close earlier :O

Amar Tumballi <amarts>
Project Member
Thu 06 Dec 2007 12:50:53 PM UTC, comment #4:

Marking it Closed as there is no update on the bug in last two months, neither any reports on similar behavior.

Bruce, I hope you didn't get the problem again, and its solved for you.

Amar Tumballi <amarts>
Project Member
Fri 05 Oct 2007 05:33:26 AM UTC, comment #3:

Any updates on this bug?
Shall I mark it invalid if no one can reproduce it?

Team, I hope this bug is fixed in later releases.

Amar Tumballi <amarts>
Project Member
Tue 21 Aug 2007 06:27:39 AM UTC, comment #2:

Hmm, I cant reproduce it now. It was a once off but caused major stability issues until I reverted the system and found the cause. (which was not shown at the fluysterfs but the filesystem level, glusterfs was showing a different location)

When I said old I meant older 2.6 kernels (eg. the stock 2.6 kernel in Debian Sarge)

It may have been a once off bug, but I know it caused major issues with some applications.

Bruce <hook>
Tue 21 Aug 2007 06:06:02 AM UTC, comment #1:

Hi Bruce,

I am not able to reproduce the problem. Accesses to recursive symbolic links pose no problems to me. Also there is nothing in the design of glusterfs that should cause problem, as far as the underlying disk based file system works fine with recursive symlinks.

Here is my system configuration:
root@darkstar:~# uname -a
Linux darkstar 2.4.33.3 #1 Fri Sep 1 01:48:52 CDT 2006 i686 prescott i386 GNU/Linux

I am using fuse kernel module from fuse-2.4.3 and libfuse from fuse-2.6.2.
underlying filesystem: reiserfs

Also what is the system configuration of the setup on which you stumbled across this bug? And were you able to access the recursive symlinks without hang-ups just on the disk-based filesystem (not through glusterfs)?

raghavendra.

Raghavendra <raghavendra>
Project Member
Sun 19 Aug 2007 11:24:39 PM UTC, original submission:

Recursive symlinks seem to cause problems with glusterfs,

When following a symlink created in the following way:
ln -s mail mail
(eg. it points to itself)
is not checked for recursiveness and can kernel panic older kernels and cause programs to lock up (become Defunct) when attempting to access it.

ext3 handles this issue by giving a recusive error after it follows the link 4 or 5 ties (not sure of the exact number as its pretty quick) glusterfs should also do this.

PS. im not sure how the symlink which done this in testing was created, it was found after clearing out the namespace and allowing unfiy to recreate it (beforehand it was locking up as described)

Bruce <hook>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by amarts (Posted a comment)
  • -unavailable- added by raghavendra (Posted a comment)
  • -unavailable- added by hook (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 2 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Thu 06 Dec 2007 12:51:45 PM UTCamartsStatusNone=>Works For Me
      Open/ClosedOpen=>Closed

    Back to the top


    Powered by Savane 3.1-cleanup1