Zyxel NAS542 - copied files from old NAS are inaccessible (open from NAS share)
Options
All Replies
-
tried one more option:
chown-nobody -hR USER:everyone * from main share/ folder
have no more idea's on my own
0 -
How about the smb.conf settings from that specific share?
0 -
I have posted it 3 posts earlier (old smb, new smb for SHARE) and 2 posts earlier (old smb, new smb for GLOBAL)How about the smb.conf settings from that specific share?
</code>zyxel /etc/samba/smb.conf</pre><div></div><pre class="CodeBlock"><code><div>[share]</div><div> path = /i-data/12344321/share</div><div> follow symlinks = yes</div><div> strict allocate = yes</div><div> allocation roundup size = 0</div><div> aio write size = 4096</div><div> comment = "share"</div><div> browseable = yes</div><div> valid users = "admin" "pc-guest" "xxx1" "XXX" "+everyone" "+XXX"</div><div> guest ok = yes</div>
0 -
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 accessIn 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>
1 -
Thx for help, looks like everything is fine now... hope it will stay that way
not sure if chown-nobody was the solution or changing oplocks 0 -
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.0
-
New problem - old files are accessible, but files created later (totally new files) are inacessible... this is starting to be quite annoying
0 -
What's the difference in ownership/permission for an old and a new file?
0 -
MijzelfWhat'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...0 -
Maybe the file is (still) locked? smbstatus can tell.
0
Freshman Member
Guru Member
Categories
- All Categories
- 439 Beta Program
- 2.8K Nebula
- 200 Nebula Ideas
- 126 Nebula Status and Incidents
- 6.3K Security
- 499 USG FLEX H Series
- 323 Security Ideas
- 1.6K Switch
- 84 Switch Ideas
- 1.3K Wireless
- 49 Wireless Ideas
- 6.8K Consumer Product
- 287 Service & License
- 457 News and Release
- 89 Security Advisories
- 31 Education Center
- 10 [Campaign] Zyxel Network Detective
- 4.3K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 85 About Community
- 96 Security Highlight
