How can one undo many hard links?

Question

I foolishly used Dupemerge to change all my duplicate files into hard links. Now Windows XP is not running right, eg, explorer won't start.

Is there a utility which would traverse the filesystem looking for hard links, copy the file, delete the original link, and rename the copy, keeping the original attributes and name?

Answer 1

I doubt that there's a utility for undoing what was done. You can search for duplicates again, check their link counts and attributes (or maybe Dupemerge can help identify hard links to the same files) and do the copying by hand. This may at least help you find out whether hard links are the cause of problems.

Answer 2

• Since you've converted them into hard links, you might be in luck and they might still show up as duplicates using something like DoubleKiller.

• Either way, I doubt there's a utility for this exact task.

If all else fails I recommend a re-install...

Answer 3

to fix the operating system use the system file checker:

insert the windows xp installation CD

press CTRL + ALT + DEL to bring up the task manager, go to File > Run (New Task) and type sfc /scannow and click OK.

note: this will only restore the system files, but it will get you going again. as for other software affected you'll have to re-install or repair install where necessary.

Answer 4

Update.

Things that didn't work:

1. I didn't find any nice tool to undo hardlinks (ie, id hardlinks, copy the file, delete hardlink, rename copy to the hardlink name).
2. Ran chkdsk in Recovery console (after uncompressing all files)
3. My Lenovo system disk wouldn't let me reinstall windows xp home, and Lenovo's Rescue and Recovery program would not reinstall Windows
4. copying out (to a 2nd partition) and back didn't help

What I did:

1. copied out my C: drive to another partition in a directory "\c-drive-2009Nov4 using Richcopy

2. In may I installed a new bigger disk, creating a partition on the new disk the same as my old C: partition. Then I copied, using a USB holder, from my old c: to the new C: partition on the new disk. Then I moved the data & installs out to a new large data partition, leaving a 70GB c: system partition on the outer faster ring of the HD. So I just did it again, using a live boot linux GParted to copy my partition from May to my trashed partition.

3. Then I used the copy I made of my current C-drive to bring back any simple files I needed, eg, updated BAT files, and reinstalled any more recent programs.

4. I was using FEBE to backup my Firefox profile, so I used the backup to reset my FF settings, in windows, and in Ubuntu, which I installed on another partition. Ubuntu is how I still had web access and some utility. Worked pretty well, even if stuck on the slow portion of the HD.

Losses: some "giveawayoftheday" programs I cannot reregister, some program settings.

Answer 5

Try Hard Link Magic, it might help.

Also Microsoft's Junction has the ability to recursively traverse directories and list/delete junction-points.

Just be careful to create a system restore point before you do these manipulations.

Answer 6

SameFiles Assistant 3.1

Answer 7

I have written a Perl script that identifies all regular files that are hard links to the same data. The script works fine on UNIX and Cygwin. I haven’t tested it with Strawberry Perl or any other Windows port of Perl, but I thought I’d share it anyhow. On Windows (Cygwin) I would open a terminal and do ./list-dup-hard-links /cygdrive/c/.

#!/usr/bin/perl
#
# NAME
#
#   list-dup-hard-links - list regular file names pointing to the same inode
#
# SYNOPSIS
#
#   list-dup-hard-links DIRECTORY
#
# DESCRIPTION
#
#   For each inode that is referred to by more than one regular file, print
#   the inode number and the list of corresponding files.
#
# AUTHOR
#
#   Peter John Acklam <pjacklam@online.no>

use strict;                             # restrict unsafe constructs
use warnings;                           # control optional warnings
use File::Find;                         # traverse a file tree

if (@ARGV != 1) {
    die "Usage: $0 DIRECTORY\n";
}

my $start_dir = shift;                  # starting directory
my $start_dev = (stat $start_dir)[0];   # device number of where we start
my %inum2files;                         # map each inode number to file(s)

sub wanted {
    return if -l;                       # skip symlinks
    my @fileinfo = stat();              # get file info

    if (-d _) {                         # if a directory
        my $this_dev = $fileinfo[0];    # get device number
        if ($this_dev != $start_dev) {  # if we crossed a device boundary
            $File::Find::prune = 1;     #   mark directory for pruning
            return;                     #   and return
        }
    }

    return unless -f _;                 # continue only if a regular file

    my $inum = $fileinfo[1];            # get inode number
    push @{ $inum2files{$inum} },       # append this file to the list of
      $File::Find::name;                #   all files with this inode number
}

find(\&wanted, $start_dir);             # traverse the file tree

while (my ($inum, $files) = each %inum2files) {
    next if @$files < 2;                # skip non-duplicates

    print "\nInode number: $inum\n\n"   # print header
      or die "$0: print failed: $!\n";

    for my $file (@$files) {
        print "    $file\n"             # print file name
          or die "$0: print failed: $!\n";
    }
}