I don't know it there's a module available to do that. But I suppose that as a general rule it won't be an easy thing since, AFAIK while filesystem and related system calls return relevant information in the direction filename => inode, they do not do the opposite. So you can gather them from comparing files. Of course this is made easier by the fact that

Update: ok, here I try my hand at this with a minimal example/proof of concept:

#!/usr/bin/perl -ln use strict; use warnings; BEGIN { @ARGV='find . -xdev|' } our %files; my ($ino, $nlink)=(stat)[1,3]; next unless $nlink and $nlink > 1; if ($nlink == push @{ $files{$ino} }, $_) { print "$_ => $ino" for @{ $files{$ino} }; delete $files{$ino}; } __END__

In reply to Re: Finding Hard links by blazar
in thread Finding Hard links by jesuashok

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.