Documentation
History
Donations
|
UNC Name support |
A local path can be a UNC name, which maybe reached
from outside the computer via share. Sometimes it is neccessary to use UNC names
to refer to local pathes. ln resolves local UNC names to local path names and does its job on those resolved path names. e.g.: ln \\local_computer\ls\sourcefile.txt x:\dir_on_local_computer\destination.txt In the above example there is a share called ls on your local_computer which conains a file sourcefile.txt. ln resolves the UNC name to a local path if possible, and creates a link between the resolved location and destination.txt in x:\dir_on_local_computer. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Recursive support |
ln.exe can recursivley hardlink all files found below a given directory location
to a newly created directory structure under a different location. In other words this means, the given directory structure is rebuilt under a different location, and all files from the given directory structure are hardlinked to the newly generated structure. Something like a xcopy but the files are hardlinked and not copied:
ln --recursive x:\dir\dir2 x:\dir\newdir
In the above example the directories below x:\dir\dir2 are rebuilt below
x:\dir\newdir, and all files from x:\dir\dir2 are hardlinked to their
corresponding locations under x:\dir\newdir.
ln --unroll --recursive x:\dir\dir2 x:\dir\newdir
In the above example the directories below x:\dir\dir2 are rebuilt below
x:\dir\newdir, all files from x:\dir\dir2 are hardlinked to their
corresponding locations under x:\dir\newdir and all junctions/symbolic links
are unrolled.
Output
Shell Integration |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Symbolic Links |
When used under Vista or Windows7/8 ln.exe can create symbolic
links ln --symbolic Sourcefile.txt SymbolicLinkToSourceFile.txt In the above example a symbolic link SymbolicLinkToSourceFile.txt is created which points to sourcefile.txt.
ln --symbolic SourceDirectory SymbolicLinkToSourceDirectory
ln.exe can also only show the target of a symbolic link. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Absolute Symbolic Links |
The target
of a symbolic link can either be
If the creation of absolute target pathnames should be forced use the --absolute option. ln --absolute --symbolic sourcefile.txt destination.txt In the above example sourcefile.txt gets symbolycally linked to destination.txt, but the target path in the symbolic link is absolute.
ln --absolute --symbolic SourceDirectory DestinationDirectory
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Normal linking |
Just for completeness: ln.exe can do the normal ln stuff
too. ln sourcefile.txt destination.txt In the above example sourcefile.txt gets linked to destination.txt |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Smart Copy |
Smart Copy basically creates a copy of the directory
structure from the source location to the destination, but it preserves the inner
hardlink structure and inner junction/symbolic link relations of the source, and
recreates this inner hardlink structure and inner junction/symbolic link relation
at the destination location:
With hardlinks it behaves as follows: 
By closely looking at the above picture one can find three different types of files:
With junctions or symbolic link directories the default behaviour during smartcopy is as follows: 
By closely looking at the above picture one can find three different types of folders/junctions:
Windows7/8 and Windows Vista support Symbolic Links, which behave as follows during Smart Copy: 
By closely looking at the above picture one can find three different types of files/symbolic links:
ln --copy x:\dir\dir2 y:\dir\newdir In the above example the directories and files below x:\dir\dir2 are copied to y:\dir\newdir, and all hardlinks/junctions/symbolic links within x:\dir\dir2 are copied/tied to their new locations under y:\dir\newdir. The --copy operation only copies if the files in the destination are either not there, or if the files in the source are newer. Otherwise the item is skipped. See also the note on quotes. If you use ln.exe as a backup tool with the --copy option, please make sure you test that everything is copied. I tested ln --copy many times, and had no problems, but when it comes to backing up data, one has to be careful. Smart Copy is a must if e.g. the whole content of a hard disk, which has lots of hardlinks/junctions/symbolic links, should be copied to another hard disk. During the Smart Copy operation empty folders get copied too and the date/time stamps of folders/junctions/symbolic links are also restored at the corresponding destination locations. Because Smart Copy creates inner hardlinks/junctions/symbolic links, this feature is only available on NTFS volumes. Smart Copy also processes all available alternative NTFS streams of a file. OutputSee Output among Delorean Copy for a detailed descritption of Smart Copies output. Shell Integration The Copy or Smart Copy functionality is also available via Link Shell Extension |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Crop/Unroll/Splice Outer Junctions/ Symbolic Links |
During SmartCopy,
Smart Mirror, Delorean Copy and
Clone so called Outer Junctions/Symlink directories
may need processing. There are 3 different ways to deal with those Outer Junctions/Symlink
directories:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Multiple Source |
Multpiple source locations can be specified for SmartCopy, Clone and
Delorean Copy. If there are junctions/symlinks between these source locations, they are handled as
inner junctions/symlinks, because all source locations are dealt like a common root.
In the above example Location 1 and Location 2 are copied to Destination. Location2/Junction_Symlink is treated as inner junctions to Location1/Folder 10 in the source, and that's why Destination/Junction_Symlink points to Destination/Folder 10 in the Destination. The objective behind this is to treat all junctions/symlinks as inner junctions/symlinks as long as they are in the set of source folders. The command line invocation below copies from "c:\Location 1" and "c:\Location 2" to c:\Destination : ln --source "c:\Location2" --copy "c:\Location1" "c:\Destination" There can be more than one additional --source command-line switches: ln --source "c:\Location 2" --source "d:\Location 5" --copy "c:\Location 1" c:\Destination Specifying additional source pathes can be combined with --splice or --unroll: ln --unroll --source "c:\Location 2" --copy "c:\Location 1" c:\Destination |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
--mirror Smart Mirror |
Smart Mirror is very similar to Smart Copy
and not only copies but synchronises the folder Source to Destination:
Different Items means: Either the file size changed, or the 'Last Write Date' changed.
e.g.:
The filters of --includeXXX or --excludeXXX are applied in the soure and the destination location See also the note on quotes.
Shell Integration
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
--mirror --symbolic Clone Mirror |
The Clone Mirror function is a combination of Smart Mirror
and SmartClone. Basically it creates a Symbolic Link Clone from Source to Destination directory,
but also synchronises the folder Source to Destination:
Different Items means: The 'Last Write Date' has changed.
e.g.: See also the note on quotes.
Shell Integration
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Smart Move |
Smart Move enables folders with junctions and symbolic
links beneath to be renamed, and the junctions and symbolic links' targets are updated
below that folder. Without Smart Move renaming of such folders would end in dangling
junctions and symbolic links.
With junctions or symbolic link directories it behaves as follows:
By closely looking at the above picture one can find three different types of folders/junctions:
ln --move x:\dir\dir2 x:\dir\newdir In the above example the directory x:\dir\dir2 is moved to x:\dir\newdir, and all symbolic links and junctions within x:\dir\dir2 are updated with respect to their new locations under x:\dir\newdir. See also the note on quotes.
Shell Integration
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
--delorean DeLorean Copy |
DeLorean Copy is a way of creating incremental backups
by using a combination of hardlink clone and Smart Copy.
The following picture gives an overview what DeLorean Copy is about
In general a DeLorean Copy has 3 principals: Source(t), InitialBackup and Backup(n).
The point is that all files in Backup1 are transparently accessible, but really little space is used, because not all files in the Source(t+1) changed, so that there was only the need to effectively copy over a few files from Source(t+1) to Backup1. Different items means: Either the file size has changed, or the 'Last Write Date' has changed.
See also the note on quotes.
The statistics of DeLorean Copy only counts the operations, which are performed during the
Mirror phase between Source and Backup(n+1). The operations which are performed during
cloning between Backup(n) and Backup(n+1) are not counted in the final DeLorean Copy statistics. Total: The total number of items as they were found under the Source. Total is the sum of all other columns but the Removed column. Copied:
Linked:
Skipped:
Removed:
Failed:
Overall: Time used up for the whole DeLorean Copy including the Clone from
Backup(n) to Backup(n+1) and the Mirror from Source to Backup(n+1) Clone: Time used up for the Clone from Backup(n) to Backup(n+1) Mirror: Time used up for the the Mirror from Source to Backup(n+1) Limitations It is little known, but NTFS has a limit to create a maximum of 1023 hardlinks to one file. For DeLorean Copy this means that it will display an error message if this limit is exceeded, because exceeding this limit means loss of data among the most recent backup sets: Delorean Copy FAILED! The NTFS link limit of 1023 has been exceeded for: The reason for exceeding this limit could either be, that there have been more than 1023 backup sets but no hardlinks within the Source, or there are hardlinks within the Source and less than 1023 backup sets.
The filters of --includeXXX or --excludeXXX are applied in the soure and the destination location Shell Integration DeLorean Copy functionality is also available via Link Shell Extension |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
--exclude Exclude files via wildcards |
In certain situations not all files below a path should
be used in Smart Copy, Smart Mirror, Delorean Copy or Clone. To accomplish this ln.exe
can be run with wildcards specified to exclude certain files.
ln --exclude *.ocx --exclude *.dll --delorean c:\source d:\b\dest d:\b\bk1 Basically any arbitrary wildcard expressions can be used, because the wildcard expressions are translated into a regular expression. This means that e.g *file*.ext*.* is also a valid wildcard expression for --exclude. The wildcard expression specified under --exclude is applied to the filename only. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
--excludedir Exclude directories via wildcards |
In certain situations not all directories should
be used in Smart Copy, Smart Mirror, Delorean Copy or Clone. To accomplish this ln.exe
can be run with wildcards to exclude certain directories.
ln --excludedir *test* --delorean c:\source d:\b\dest d:\b\bk1 Basically any arbitrary wildcard expressions can be used, because the wildcard expressions are translated into a regular expression. This means that e.g *file*.ext*.* is also a valid wildcard expression for --excludedir. The wildcard expression specified under --excludedir is applied to the whole path, which means that e.g ln --excludedir "fotos\\temp" --copy c:\source d:\b\dest will exclude all directories containing 'fotos\temp' and their subdirectories. The above expample will e.g. exclude 'fotos\tempur\myfotos', 'fotos\temp\myfotos' or 'fotos\tempomat\myfotos'. Please make sure that '\' has to be escaped via '\\'
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
--excluderegexp Exclude files via regular expressions |
In certain situations not all files below a path should
be used in Smart Copy, , Smart Mirror, Delorean Copy or Clone. To accomplish this ln.exe
can be run with regular expressions specified to exclude certain files.
ln --excluderegexp "[a-z]*" --copy c:\source d:\b\dest The regular expressions used must conform to POSIX 1003.2 extended RE (ERE) syntax. The regular expression specified under --excluderegexp is applied to the filename only. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
--excluderegexpdir Exclude directories via regular expressions |
In certain situations not all directories should
be used with Smart Copy, Smart Mirror, Delorean Copy or Clone. To accomplish this ln.exe
can be run with regular expressions to exclude certain directories.
ln --excluderegexpdir "[a-z]*" --delorean c:\source d:\b\dest d:\b\bk1 The regular expressions used must conform to POSIX 1003.2 extended RE (ERE) syntax. The regular expression specified under --excluderegexpdir is applied to the whole path. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
--enum Enum hardlinks |
Sometimes it is convenient to find out which files
are linked together, because hardlinked files might be spread around a NTFS volume.
This is somehow the inverse hardlink functionality and it can be invoked as follows ln --enum path In the above example files below path are searched, and the files which are hardlinked are printed out. The --enum option first prints so called saturated and afterwards unsaturated hardlinks. For saturated hardlinks the number of files found below path matches the hardlink reference count of these files, but unsaturated hardlinks have a reference count greater than the number found below path. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
--include Include files via wildcards |
To selectivley run Smart Copy, Smart Mirror, Delorean Copy or Clone on a certain
set of files, the --include option can be used with wildcards.
ln --include *.ocx --include *.dll --delorean c:\source d:\b\dest d:\b\bk1 Basically any arbitrary wildcard expressions can be used, because the wildcard expressions are translated into a regular expression. This means that e.g *file*.ext*.* is also a valid wildcard expression for --include. The wildcard expression specified under --include is applied to the filename only. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
--includedir Include directories via wildcards |
To selectivley run Smart Copy, Smart Mirror, Delorean Copy or Clone on a certain
set of directories, the --includedir option can be used with wildcards.
ln --includedir *test --delorean c:\source d:\b\dest d:\b\bk1 Basically any arbitrary wildcard expressions can be used, because the wildcard expressions are translated into a regular expression. This means that e.g *src\\sub?older* is also a valid wildcard expression for --includedir. The wildcard expression specified under --includedir is applied to the whole path, which means that e.g ln --includedir "*fotos\\temp*" --copy c:\source d:\b\dest will include all directories containing 'fotos\temp' and their subdirectories. The above expample will e.g. include 'fotos\tempur\myfotos', 'fotos\temp\myfotos' or 'fotos\tempomat\myfotos'. Please make sure that '\' has to be escaped via '\\'
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
--includeregexp Include files via regular expressions |
To selectivley run Smart Copy, Smart Mirror, Delorean Copy or Clone on a certain
set of files, the --includeregexp option can be used with regular expressions specified to include certain files.
ln --includeregexp "[a-z]*" --copy c:\source d:\b\dest The regular expressions used must conform to POSIX 1003.2 extended RE (ERE) syntax. The regular expression specified under --includeregexp is applied to the filename only. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
--includeregexpdir Include directories via regular expressions |
To selectivley run Smart Copy, Smart Mirror, Delorean Copy or Clone on a certain
set of directories, the --includedir option can be used with regular expressions to include certain directories.
ln --includeregexpdir "[a-z]*" --delorean c:\source d:\b\dest d:\b\bk1 The regular expressions used must conform to POSIX 1003.2 extended RE (ERE) syntax. The regular expression specified under --includeregexpdir is applied to the whole path. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
--junction Create Junctions |
ln.exe can also create junctions, and print the target
of junctions ln --junction JunctionName TargetDirectory In the above example a junctionJunctionName is created, which point to TargetDirectory ln --junction JunctionName In the above example the junctionJunctionName is searched for its Target and the target is printed out. rd JunctionName In the above example the junctionJunctionName removed. This is accomplished with an simple built in command prompt command. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
--list List Hardlink siblings |
With Vista finding out the siblings of a hardlink
is very simple and needs no timeconsuming operations
ln --list filename In the above example the hardlink siblings for filename are printed out.
With XP, W2K or W2K3 finding the hardlink siblings now also works, but it takes
more time, because in the worst case the whole logical volume must be searched.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
--output Redirect Output |
The ouptut of ln.exe can be redirected to files via commandline option
ln --output filename --copy src dest In the above example all output is redirected to filename .
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
--quiet specify log level |
The amount of output during various operations can be controlled
via the --quiet switch: ln --quiet ... The --quiet option without arguments totally disables any output during ln.exe' operations. To specify the amount of output more granular an optional argument can be passed to the --quiet switch:
ln --quiet 2 ... In the above example only changes are shown. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
--skipfiles |
This option is a modifier to Smart Copy, Smart Mirror, Delorean Copy, or Clone, so that only directories
symlinks and junctions are processed. The files are ommitted with this modifier used.
ln --skipfiles --copy source destination |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
--smartrename Smart Rename |
Smart Rename is very similar to Smart Move, but
only renames junctions/symbolic links references below a given folder. ln --smartrename x:\dir\dir2 x:\dir\newdir In the above example the symbolic links/junction references below x:\dir\dir2 are renamed to x:\dir\newdir. This leaves x:\dir\dir2 with dangling symbolic links/junction, but this feature is useful if someone wants to migrate a whole disk to another physical media.
ln --copy x:\ y:\
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
--timetolerance |
During --mirror and --delorean it is sometimes useful to not have an exact timestamp comparison bewteen
source and dest, but kind of a fuzzy comparison, because the systemtime of NAS drives is not exactly synced
with the host.
To overcome this ln.exe has a --timetolerance switch to specify a value in milliseconds ln --timetolerance 2000 --mirror source destination |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
--traditional Traditional mode |
Some NAS boxes only support a very outdated version of the SMB protocol. SMB is
used when network drives are connected. This old version of SMB in certain situations does not support the
fast enumeration methods of ln.exe, which causes ln.exe to simply do nothing in SmartXXX functions.
To overcome this ln.exe has a --traditional switch, which forces ln.exe to enumerate files the old, but a little slower way. ln --traditional --copy source destination ... |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
--trueSize Size calculation |
Prints the true space used taking into account hardlinks. This means that a file with a size of e.g 12345kb and
a reference count 5, will be listed with 61725kb by explorer, but indeed it only uses 12345kb, because it has a
refcount of 5.
ln --truesize path returns the following output
The --truesize option does not return info on alternate data streams right now. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Quotes around path |
If there are blanks in the argument path to ln.exe, the pathname has to be put under quotes, e.g.
ln --copy "x:\dir with blanks\dir2" "y:\destination with blanks\newdir" Please make sure not to end a quoted path with \ because ln.exe treats this as escaping of the quote (\") and can not parse the command line.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ln.exe checks these situations when it comes to allow the creation of hardlinks, and as a consequence allows the creation of hardlinks among different logical drives if they resolve to the same NTFS volume.
There are two ways to acchieve this:
The way with a drive-letter
ln.exe can be used to create consistent copies from a snapshot: 4 files are needed: vshadow.exe, robocopy.exe, dosdev.exe, vss-exec.cmd. Place the files where you want, but vshadow.exe and dosdev.exe need to be in the path.
A backup of an entire e.g. E:\ or parts from it can be accomplished with this command:
vshadow.exe -script=vss-setvar.cmd -exec=vss-exec.cmd e:
The -script=vss-setvar.cmd is a command line argument to vshadow.exe that gives the shadow copy an identifier string so that a drive letter can be assigned to it - which allows ln.exe to access the files.
The -script=vss-exec.cmd is a command line argument to vshadow.exe that contains the name of a file, which is executed within vshadow.exe and does the very backup job:
REM
REM called from vshadow via commandline e.g
REM
REM vshadow.exe -script=vss-setvar.cmd -exec=vss-exec.cmd e:
REM
REM vss-setvar.cmd is generated by vshadow.exe
REM
call vss-setvar.cmd
REM assign a DOS device to the created snapshot
REM
dosdev x: %shadow_device_1%
REM run the intended copy job
REM
set LN=c:\tools\ln.exe
%LN% --copy x:\path e:\backup
REM finally remove the drive letter
REM
dosdev -r -d x:
The event process is this:
The vshadow.exe program creates a shadow copy, and then calls the on the fly generated vss-setvar.cmd that assigns a variable to the shadow copy. Then the given batch file vss-exec.cmd is executed within vshadow.exe. Dosdev.exe first assigns the drive letter x: to the shadow copy. ln.exe can be called now with whatever parameters are neccessary at this time. By the end dosdev.exe removes the drive letter and vshadow.exe is allowed to exit.
The vshadow.exe generates an e.g vss-setvar.cmd:
@echo.
@echo [This script is generated by VSHADOW.EXE for the shadow set {95a6cd9f-bc45-43b8-8722-6c25ec06fe94}]
@echo.
SET SHADOW_SET_ID={95a6cd9f-bc45-43b8-8722-6c25ec06fe94}
SET SHADOW_ID_1={e38169c1-6aa7-4843-ac50-4c7b652397b3}
SET SHADOW_DEVICE_1=\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
There are different versions of vshadow.exe (32bit, 64bit, workstation, and server). You can download them from here in the same way as for dosdev
The way with a UNC share
If for some reason no drive letter is available, the same strategy as above can be done via UNC share. The vss_unc-exec.cmd script can be found here.
A backup of an entire e.g. E:\ or parts from it can be accomplished with this command:
vshadow.exe -script=vss-setvar.cmd -exec=vss_unc-exec.cmd e:
BUT: There are filter drivers available from Masatoshi Kimura for even WindowsXP, which enable symbolic links under XP. These drivers can be downloaded from his home page for 64 bit and for 32 bit. The sources are also available.
Installation of these drivers is also quite simple.
ln.exe enables its symbolic link functions even under WindowsXP, if it finds this driver installed.
Delete all hardlink siblings. This .bat file uses the --list option to enumerate all hardlinks and successivley deletes them.
Usage: DeleteAllHardlinks.bat Filename
Create timestamped DeLorean Copies as Link Shellextension does: 'data - yyyy-mm-dd hh-mm-ss', e.g 'MyData 2010-09-11 17-04-03'. Furthermore the number of backup-sets to be kept can be specified via the optional KeepEntries argument.
Usage: DeloreanCopy.bat SourceDir BackupDir [KeepEntries]
Tower of Hanoi backup rotation scheme using Delorean Copies.
Creates a number of backups using the Tower of Hanoi backup rotation scheme Usage: DeloreanHanoi.bat SourceDir BackupDir [BackupSets]
| 0 | Success. Everything is fine. |
|
|
|
| -1 |
The source directory given via command line parameters,
does not exist. This happens in recursive mode if the first command line argument is not there |
|
|
|
| -2 | The first command line argument in recursive mode specifies a directory, and it is not a directory, but some other kind of file. |
|
|
|
| -3 | The second command line argument specifies a file, or in recursive mode a directory, which already exists. |
|
|
|
| -4 | The destination directory could not be created in recursive mode. |
|
|
|
| -5 | The source file aka first command line parameter does not exist in normal mode. |
|
|
|
| -6 | The filesystem is not NTFS and does not support the creation of hardlinks. |
|
|
|
| -7 | For some unknown reason the creation of a hardlink failed. |
|
|
|
| -8 | Less arguments were given via command line. |
|
|
|
| -9 | Ln was not able to enumerate the files in a directory. This might happen in recursive or in hardlink eunumeration mode if the file permissions for a directory are insufficient. |
|
|
|
| -12 | Ln.exe was not able to create a SmartCopy. |
|
|
|
| -14 | Ln.exe was not able to create a clone. |
|
|
|
So what are hardlinks in detail. It is common knowledge, that a file has a name and data associated to it. By opening the explorer, the NTFS filesystem of NT4/W2K/WXP can be browsed comfortably. There is a 1:1 relationship between the filename and the filedata, but this assumption does not hold for every filesystem.
Some filesystems, such as UFS, XFS, or NTFS have a N:1 relationship between filename and the filedata. So this means there is more than one directory entry for a file.
But how does one create those multiple entries? There is a command under Unix called ln, which creates many file entries for a file, so that there are many filenames or also called hardlinks for one filedata.
For each hardlink created, the filesystem increments a reference count stored with the filedata, so that the filedata stores how many filenames point to it. If a filename pointing to a hardlinked filedata gets deleted, the reference count stored with the filedata gets decremented by one. The filedata gets deleted when the reference count of the filedata decreases to zero.
HardLinks can only be created on NTFS volumes, under the supported plattforms.
HardLinks can only be created within one NTFS volumes, and can not span accross NTFS volumes.
volumes.
Delorean Copy/Smart Copy currently does not copy alternative datastreams.
Delorean Copy/Smart Copy currently does not copy ACLs.
| May 9th, 2013 |
Version 2.7.4.9
|
| June 24th, 2012 |
Version 2.7.2.0
|
| April 11th, 2012 |
Version 2.7.1.6
|
| May 15th 2011 |
Version 2.6.5.0
|
| April 17th 2011 |
Version 2.6.0.4
|
| December 20th 2010 |
Version 2.5.5.5
|
| October 3rd 2010 |
Version 2.4.0.0
|
| May 22nd 2010 |
Version 2.3.5.4
|
| March 9th 2009 |
Version 2.2.0.6 Enumerate hardlink siblings for Vista
& Wxp, Symbolic link support vista Under W2K it turned out, that CreateHardlink() from kernel32.dll with long pathnames (e.g. \\?\) was broken. |
| September 12th 2008 |
Version 1.997 Introduced the --copy
option Enabled the --symbolic option for Vista Introduced the --list option under Vista Added long (32k) path support |
| February 17th 2006 |
Version 1.810 Various small fixes related to commandline
parsing.
|
| February 18th 2005 |
Version 1.803 Fixed NT4 compatibility issues.
|
| February 7th 2005 |
Version 1.800 Fixed a few minor internal flaw related
to hardlink enumeration. Improved html documenation and added description for return
values.
|
| November 26th 2004 |
Version 1.711 decides between saturated and unsaturated
hardlinks when used with the --enum option. |
| November 18th 2004 |
Version 1.600 supports the enumerate functionality
via --enum switch |
| June 24th 2004 |
Version 1.502 released |
Endre Both for beeing a great tester with endless patience and for excellent constructive feedback on features during dvelopment.
Feature requests?
- Jos Branders has a tool called
Link Magic 1.0, which deals in depth with NTFS junctions.
- Ville Laurikari developed an exceptional free regular expression parser.
- Kevin Locke developed a great command line parser,
called ultragetopt.
- This program is provided as is. See license.txt from this distribution for legal issues.
- ln.exe uses tre as the regular expression machine. See the tre license.
- ln.exe uses ultragetopt for command line parsing. See the ultragetopt license.
- ln.exe uses the Rockall v4.0 heapmanager for fast heap operations. See the EULA.
ln.exe is and will be freeware, but if ln.exe was really helpful for you and saved lots of your time please think of donations either via PayPal
or by flattring me
|
Windows 2000 Windows XP Windows Server 2003 Windows Server 2008 Windows Vista Windows 7 Windows 8 |
Please make sure that the necessary runtime .dlls are
installed on your system. This prerequisites package can be downloaded from Microsoft: Afterwards install the |
|
Windows XP64 Windows Vista64 Windows 7 64bit Windows 8 64bit |
Please make sure that the necessary runtime .dlls are
installed on your system. This prerequisites package can be downloaded from Microsoft: Afterwards install the |
|
Windows Itanium Windows 7 Itanium Windows 8 Itanium |
Please make sure that the necessary runtime .dlls are
installed on your system. This prerequisites package can be downloaded from Microsoft: Afterwards install the |
|
Symbolic Link Driver for Windows XP |
The driver to enable even WindowsXP with
symbolic link functionality is provided courtesy of Masatoshi Kimura. Yo ucan download the driver from his
homepage or from my site acting as a mirror.
|