diff --git a/Hardlinks/Check-if-hardlinks-are-working/index.html b/Hardlinks/Check-if-hardlinks-are-working/index.html index 24867f98e..93d080dfc 100644 --- a/Hardlinks/Check-if-hardlinks-are-working/index.html +++ b/Hardlinks/Check-if-hardlinks-are-working/index.html @@ -3253,27 +3253,36 @@
  • - + - Method 1: Using ls + Mac or Linux Method 1: Using ls
  • - + - Method 2: Using stat + Mac or Linux Method 2: Using stat
  • - + - Method 3: Using Inode copies + Mac or Linux Method 3: Using Inode copies + + + +
  • + +
  • + + + Windows Method 1: Using fsutil @@ -3438,27 +3447,36 @@
  • - + + + Mac or Linux Method 1: Using ls + + + +
  • + +
  • + - Method 1: Using ls + Mac or Linux Method 2: Using stat
  • - + - Method 2: Using stat + Mac or Linux Method 3: Using Inode copies
  • - + - Method 3: Using Inode copies + Windows Method 1: Using fsutil @@ -3513,7 +3531,7 @@

    If you are using Usenet, these examples won't work due to making use of instant/atomic moves and not hardlinks.

    Still want to test if it works?

    Test an import of a 4k remux, or any other big file, and you should notice it's almost instant and not a slower and more I/O intensive copy + delete.

    -

    Method 1: Using ls

    +

    Mac or Linux Method 1: Using ls

    This is the easiest to check in our opinion.

    In your terminal cd to your download location and run ls -al or type ls -al /path/to/your/download/location/

    You will get a listing of all your files and on the left side you will see a couple of numbers, every file with a number above 1 are hardlinks.

    @@ -3524,7 +3542,7 @@
  • Blue rectangle - Folders/Directories you will need to go into them to check if the files are hardlinked.

  • -

    Method 2: Using stat

    +

    Mac or Linux Method 2: Using stat

    This way requires a bit more work.