Zyxel NAS542 - copied files from old NAS are inaccessible (open from NAS share)

Options
2

All Replies

  • adrian3k
    adrian3k Posts: 16  Freshman Member
    Answer ✓
    Options
    tried one more option:
    chown-nobody -hR USER:everyone * from main share/ folder

    have no more idea's on my own :neutral:
  • Mijzelf
    Mijzelf Posts: 2,605  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options
    How about the smb.conf settings from that specific share?
  • adrian3k
    adrian3k Posts: 16  Freshman Member
    edited September 2019
    Options
    How about the smb.conf settings from that specific share?
    I have posted it 3 posts earlier (old smb, new smb for SHARE) and 2 posts earlier (old smb, new smb for GLOBAL)
    </code>zyxel /etc/samba/smb.conf</pre><div></div><pre class="CodeBlock"><code><div>[share]</div><div>&nbsp; &nbsp; &nbsp; &nbsp; path = /i-data/12344321/share</div><div>&nbsp; &nbsp; &nbsp; &nbsp; follow symlinks = yes</div><div>&nbsp; &nbsp; &nbsp; &nbsp; strict allocate = yes</div><div>&nbsp; &nbsp; &nbsp; &nbsp; allocation roundup size = 0</div><div>&nbsp; &nbsp; &nbsp; &nbsp; aio write size = 4096</div><div>&nbsp; &nbsp; &nbsp; &nbsp; comment = "share"</div><div>&nbsp; &nbsp; &nbsp; &nbsp; browseable = yes</div><div>&nbsp; &nbsp; &nbsp; &nbsp; valid users = "admin" "pc-guest" "xxx1" "XXX" "+everyone" "+XXX"</div><div>&nbsp; &nbsp; &nbsp; &nbsp; guest ok = yes</div>

  • Mijzelf
    Mijzelf Posts: 2,605  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Answer ✓
    Options
    Ah sorry, missed that post. Well, after looking at the files, the most probable difference I can find is oplocks. That's a Windows way to lock files, to prevent multiple edit sessions at a time. I can imagine some editors just refuse to work if they can't get exclusive access

    In old file we have
    <div>[global]</div><div><br></div><div>oplocks = yes</div>
    in new file it's
    <div>[global]</div><div><br></div><div><div>kernel oplocks = no</div><div><br></div>level2 oplocks = no</div>
    (I'm very happy that smb.conf always have simple, not confusing options)
    So try to edit the latter to 'yes', and restart samba.
    <div>/etc/init.d/samba.sh restart<br></div>

  • adrian3k
    adrian3k Posts: 16  Freshman Member
    Options
    Thx for help, looks like everything is fine now... hope it will stay that way :wink: not sure if chown-nobody was the solution or changing oplocks :neutral:
  • Mijzelf
    Mijzelf Posts: 2,605  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options
    You will know after the first reboot. The edit in smb.conf won't survive a reboot, nor will it survive any change in samba configuration using the webinterface.
    Basically smb.conf is generated dynamically by the NAS' backend.
  • adrian3k
    adrian3k Posts: 16  Freshman Member
    edited October 2019
    Options
    New problem - old files are accessible, but files created later (totally new files) are inacessible... this is starting to be quite annoying :disappointed:
  • Mijzelf
    Mijzelf Posts: 2,605  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options
    What's the difference in ownership/permission for an old and a new file?
  • adrian3k
    adrian3k Posts: 16  Freshman Member
    Options
    Mijzelf
    What's the difference in ownership/permission for an old and a new file?
    if you are refering to 
    ls -alh
    it is the same as before...
  • Mijzelf
    Mijzelf Posts: 2,605  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options
    Maybe the file is (still) locked? smbstatus can tell.

Categories

Consumer Product Help Center

EnglishTiếng ViệtРусскийไทย中文（台灣）