Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

RFC: 6.2-rc2 experimental shfs hard-link support & appdata share discussion

Featured Replies

  • Author

So now that this was listed in the 6.2 release as a feature is it safe to assume this is no longer experimental? Will this continue to stay as a feature in unRAID or is there a possibility of it being removed? It would be nice to have a definitive answer to this from limetech including an answer to Ignitenz post.

 

Do we still need to do the changes from Page 1 to get hardlinks working in rc3?

Good points.  Yes hard links are now supported.

Side question while I'm at work and not really able to investigate fully...  What is the maximum # of hardlinks per file supported  (Right now I'm testing with ~10,000 hardlinks per file with no problems, but in the next day or so I want to do a test with ~1,000,000 hardlinks per file)...  My quick research seemed to indicate that it would max out at the number of inodes available that the fs was mounted with...

It's going to be whatever the underlying file system supports.

  • 1 month later...
  • Replies 58
  • Views 15.3k
  • Created
  • Last Reply

So now that this was listed in the 6.2 release as a feature is it safe to assume this is no longer experimental? Will this continue to stay as a feature in unRAID or is there a possibility of it being removed? It would be nice to have a definitive answer to this from limetech including an answer to Ignitenz post.

 

Do we still need to do the changes from Page 1 to get hardlinks working in rc3?

Good points.  Yes hard links are now supported.

 

Do we still need to do the changes from Page 1 to get hardlinks working in rc3?

Do we still need to do the changes from Page 1 to get hardlinks working in rc3?

no

Do we still need to do the changes from Page 1 to get hardlinks working in rc3?

no

 

Thanks Squid,

 

On 6.2.4, it seems I still cannot use hard links. Trying cp -l gives me the cross-device link error, and in CouchPotato, the option to link then fall back to copy will always result in a copy. If my understanding of the feature is correct, this should work right? If so, what should I investigate to solve the issue?

 

Thanks :)

Do we still need to do the changes from Page 1 to get hardlinks working in rc3?

no

 

Thanks Squid,

 

On 6.2.4, it seems I still cannot use hard links. Trying cp -l gives me the cross-device link error, and in CouchPotato, the option to link then fall back to copy will always result in a copy. If my understanding of the feature is correct, this should work right? If so, what should I investigate to solve the issue?

 

Thanks :)

 

What is the command you are using? You cannot hard link across user shares so maybe that is your problem.

Do we still need to do the changes from Page 1 to get hardlinks working in rc3?

no

 

Thanks Squid,

 

On 6.2.4, it seems I still cannot use hard links. Trying cp -l gives me the cross-device link error, and in CouchPotato, the option to link then fall back to copy will always result in a copy. If my understanding of the feature is correct, this should work right? If so, what should I investigate to solve the issue?

 

Thanks :)

 

What is the command you are using? You cannot hard link across user shares so maybe that is your problem.

I would actually further generalize that, since I don't believe you can cross link between mount points.

What is the command you are using? You cannot hard link across user shares so maybe that is your problem.

 

I'm using

cp -l /original/file /dest/file

 

This file is located in a user share which has cache activated, but it is in fact from another user share: Downloads usershare to Plex usershare. I thought that it could work while the file was in the cache, but I understand that this is not possible.

What is the command you are using? You cannot hard link across user shares so maybe that is your problem.

 

I'm using

cp -l /original/file /dest/file

 

This file is located in a user share which has cache activated, but it is in fact from another user share: Downloads usershare to Plex usershare. I thought that it could work while the file was in the cache, but I understand that this is not possible.

Its not the cache thats the problem.  Its that your attempting a link between mount points (user shares) which can't be done.

Its not the cache thats the problem.  Its that your attempting a link between mount points (user shares) which can't be done.

 

Totally understand. So i'll just kill the Downloads usershare and move it to the Plex usershare, then all the links should work (correct me if I'm wrong).

 

Thanks a lot!

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.