пн, 18 февр. 2019 г. в 22:16, L A Walsh <cifs@xxxxxxxxx>: > > > In my Windows root directory I have several links. This is how > they look on the Windows machine's "root". Several months ago I > sent an email to this list complimenting you on how they looked. > (without user+group) > > > ll |grep -- '->' > lrwxrwxrwx 1 17 Jun 13 2016 Documents -> //Bliss/Documents/ > lrwxrwxrwx 1 6 Jul 13 2009 Documents and Settings -> /Users/ > lrwxrwxrwx 1 16 Jun 5 2015 FolderChanger -> /m/FolderChanger/ > lrwxrwxrwx 1 5 May 13 2017 Home -> Users/ > lrwxrwxrwx 1 20 Nov 6 2014 Prog -> /Program Files (x86)/ > lrwxrwxrwx 1 13 Apr 21 2013 Prog64 -> Program Files/ > lrwxrwxrwx 1 12 Aug 9 2015 ProgD -> /ProgramData/ > lrwxrwxrwx 1 2 Apr 17 2017 Share -> /s/ > lrwxrwxrwx 1 22 Aug 22 16:08 Symbols -> //Bliss/Share/Symbols// > lrwxrwxrwx 1 7 Mar 1 2018 WINNT -> Windows/ > lrwxrwxrwx 1 3 May 13 2017 lib64 -> lib/ > lrwxrwxrwx 1 3 Jan 12 2014 temp -> tmp/ > > Now, I'm getting flakiresults -- with them not resolving 1 time, > then resolving, then not again...etc. By flakey I mean > output like random can't access messages, followed by question > marks in all fields of links. > > # ll|more > ls: cannot access 'D': Operation not supported > ls: cannot access 'Documents': Operation not supported > ls: cannot access 'FolderChanger': Operation not supported > ls: cannot access 'Home': Operation not supported > ls: cannot access 'lib64': Operation not supported > ls: cannot access 'M': Operation not supported > ls: cannot access 'P': Operation not supported > ls: cannot access 'pagefile.sys': Device or resource busy > ls: cannot access 'Prog64': Operation not supported > ls: cannot access 'Share': Operation not supported > ls: cannot access 'temp': Operation not supported > ls: cannot access 'WINNT': Operation not supported > d????????? ? ? ? D/ > d????????? ? ? ? Documents/ > d????????? ? ? ? FolderChanger/ > d????????? ? ? ? Home/ > d????????? ? ? ? M/ > d????????? ? ? ? P/ > d????????? ? ? ? Prog64/ > d????????? ? ? ? Share/ > d????????? ? ? ? WINNT/ > d????????? ? ? ? lib64/ > d????????? ? ? ? temp/ > > Depending on timing, Sometimes I will get most or all of > them appearing the same as they would on windows. > > If I can't resolve them more quickly, is there a know > or two to increase cache size and item lifetime? > > Thanks > Which kernel version shows symlinks right and which - wrong? -- Best regards, Pavel Shilovsky
