• Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About NLS

  • Rank
    Advanced Member
  • Birthday 03/30/1974


  • Gender
  • URL
  • Location

Recent Profile Visitors

1352 profile views
  1. OK I reverted too. Also added UMASK_SET variable and hope it fixes the wrong security attributes of new torrents. Let's hope it updates properly next time.
  2. Well I'll wait at least for today to see some kind of "official" reaction first. Reverting to previous version also returned your torrents?
  3. Same here - torrents disappeared. Haven't tried to re-add them (one by one over 100 seeds)... Can someone give a step by step process to go back to previous version? Will that return the torrents listed?
  4. Sorry if it has been asked before, but anything downloaded by this docker, has the wrong security attributes (and then I need to change them manually). It is read only for group and others. Any ideas?
  5. Yes sorry... this is not an install since then, is a fresh one (less than a year) data xfs cache btrfs
  6. I think you are missing the point. My problem is not if folder browsing is slow. It is yes, ok, but not a major problem. Again a "demo" of the problem: Editing a pack of let say 400 x 100kb files within a 400 files folder = 150 seconds. Editing a pack of same 400 x 100kb files within a 100000 files folder = 2 hours. (numbers are not real, but they are close to scale) This is the problem. I am using latest non-beta release for unRAID and using the default fs it installs on data disks. Client is Windows 10 x64 with all patches.
  7. I have a seemingly huge issue with my unRAID. Seems the larger the folder in number of files, the slower the file access inside it. And I mean disproportionally. I don't mean that double the files the double the file access. And I am not just referring to listing the contents. I am talking about actual file access, edits etc. A tiny file with a small change that in a small unRAID folder takes non-measurable time after saving, may take... 1 minute (!!!) for the same tiny file if it resides in a huge folder (containing let say 100k files). I have read about case sensitivity and
  8. I am not sure if I post this in the proper place, as I am not sure who generates the pop-ups (stock unRAID or some add-in). So, since a couple of my disks keep going to 46 degrees (I have fans hitting them and don't go over this most of the times), I get a huge number of notifications as they go in and out of that temp. Since I am willing to accept that 46 degrees (in a Greek summer) are ok when disk is working, can I set the alert levels differently somehow?
  9. Any chance for update on VNC Web Browser? Chromium crashes all the time and Firefox keeps popping I need a security update of the browser (that I cannot install). EDIT: Just noticed about EOL. So new question, any news about new container?
  10. Here is what I did in the end. First I set the commands to check for invalid dates. find /mnt/user -type f -mtime 8500 -ls ## Consider before early 1997 that the dates are invalid and usually they are. ## ## Note that Windows and Linux showed some of them DIFFERENTLY ## ## meaning "edge" dates behave differently between the two OS! ## find /mnt/user -type f -newermt today -ls ## I didn't find parameter "today" mentioned anywhere but suspected it works and from my checks, it does. ## Interesting trivia with -mtime 8500 (which is January 29 1997 if run today), is that few file
  11. Haven't found a way to find future timestamps (obviously because of some error). Anybody knows?
  12. Good health to everybody. I have a weird issue, that I am not sure where this came from. It relates to files I sync from USB disks to my array and these days also back to the USB disks. I use DirSyncPro (but not a DirSyncPro issue I think since the files have the issue already). Seems many files have invalid datestamps (like 1969 or the 22nd century)- and the invalid datestamp propagates differently between the NTFS USB disks and unRAID array. Can someone make a simple plugin OR help me with a script to check the whole array (or per share - and if possible also on