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