[Ocfs2-tools-devel] [PATCH 1/1] Ocfs2-tools: Let debugfs.ocfs2 correctly dump the fast symlink.

[tristan.ye]

On Wed, 2009-06-03 at 15:33 +0800, Tao Ma wrote:
> Hi Tristan,
> 
> Tristan Ye wrote:
> > Currently dump and rdump command in debugfs.ocfs2 didn't handle the
> > fast symlink correctly but a error encountered.
> > 
> > To improve the current situation, I'm going to follow up the symlink
> > recursively until its real target get reached, we got the target's content
> > when dumping symlink with debugfs.ocfs2 just like read(2) operation on a symlink.
> No, I don't think we should follow it, just the link is OK. The reason is:
> symlink is just a symlink, it can be any file actually. What if the 
> target file isn't in our ocfs2 volume? And even if it is a file within 
> ocfs2, it can have an absolute path("/mnt/ocfs2/bla/bla"). You don't 
> know the mount point, how could you get the target's file content?
> 
> Look at what we do for a symlink file(not a fast one), it just dumps the 
> file's content(the link).

Yes, what you're saying make sense!  I may be going the wrong direction.

Thank you tao.



> 
> Regards,
> Tao