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