1 |
covici@××××××××××.com writes: |
2 |
|
3 |
> lee <lee@××××××××.de> wrote: |
4 |
> |
5 |
>> covici@××××××××××.com writes: |
6 |
>> |
7 |
>> > lee <lee@××××××××.de> wrote: |
8 |
>> > |
9 |
>> >> covici@××××××××××.com writes: |
10 |
>> >> |
11 |
>> >> > Hi. I just upgraded from samba 4.1.x to 4.2.7 and in one of my shares, |
12 |
>> >> > I can not access any subfolders of that share. It usually gives me some |
13 |
>> >> > kind of windows permission error, or just location not available. |
14 |
>> >> > Windows tells me I can't even display the advanced security settings for |
15 |
>> >> > any folder. Anyone know what they did and how to fix? There is a hard |
16 |
>> >> > blocker to downgrading, so maybe something is up. |
17 |
>> >> > |
18 |
>> >> > Thanks in advance for any suggestions. |
19 |
>> >> |
20 |
>> >> Do they have a changelog which you looked at? Can you mount these |
21 |
>> >> shares from a Linux client? |
22 |
>> > |
23 |
>> > These are on a Linux server, so there is no problem there. |
24 |
>> |
25 |
>> Can you definitely mount the share from a remote Linux client without |
26 |
>> problems? |
27 |
>> |
28 |
>> > Changelog doesn't say anything but the version number. |
29 |
> |
30 |
> I don't have any remote linux client and this is samba, used so that |
31 |
> windows can access the share. |
32 |
|
33 |
You could make a copy of everything in the inaccessible share, make a |
34 |
new share with settings identical to the settings of the shares that are |
35 |
still accessible when copying has finished, and try to access the new |
36 |
share with a remote client. |
37 |
|
38 |
If you can access the new share, either something with the old one is |
39 |
weird, or you have changed something like permissions or extended |
40 |
attributes by copying. |
41 |
|
42 |
|
43 |
If you cannot access the new share, try a different kernel version (or |
44 |
try a different kernel version first). I've had a case in which a |
45 |
kernel would freeze/panic when the directory contents of a directory |
46 |
that was exported via NFS were displayed with ls on a NFS client. |
47 |
|
48 |
IIRC samba uses kernel support on the server. Perhaps you have a |
49 |
version mismatch between the new samba version and what the kernel |
50 |
supports. |