cov...@ccs.covici.com writes: > lee <l...@yagibdah.de> wrote: > >> cov...@ccs.covici.com writes: >> >> > lee <l...@yagibdah.de> wrote: >> > >> >> cov...@ccs.covici.com writes: >> >> >> >> > Hi. I just upgraded from samba 4.1.x to 4.2.7 and in one of my shares, >> >> > I can not access any subfolders of that share. It usually gives me some >> >> > kind of windows permission error, or just location not available. >> >> > Windows tells me I can't even display the advanced security settings for >> >> > any folder. Anyone know what they did and how to fix? There is a hard >> >> > blocker to downgrading, so maybe something is up. >> >> > >> >> > Thanks in advance for any suggestions. >> >> >> >> Do they have a changelog which you looked at? Can you mount these >> >> shares from a Linux client? >> > >> > These are on a Linux server, so there is no problem there. >> >> Can you definitely mount the share from a remote Linux client without >> problems? >> >> > Changelog doesn't say anything but the version number. > > I don't have any remote linux client and this is samba, used so that > windows can access the share.
You could make a copy of everything in the inaccessible share, make a new share with settings identical to the settings of the shares that are still accessible when copying has finished, and try to access the new share with a remote client. If you can access the new share, either something with the old one is weird, or you have changed something like permissions or extended attributes by copying. If you cannot access the new share, try a different kernel version (or try a different kernel version first). I've had a case in which a kernel would freeze/panic when the directory contents of a directory that was exported via NFS were displayed with ls on a NFS client. IIRC samba uses kernel support on the server. Perhaps you have a version mismatch between the new samba version and what the kernel supports.
