Over the weekend I upgraded my IRIX servers to 3.0.13 and have found many
strange issues regarding the creation of new folders.
When I attempt to add a new folder through the Windows side I get an immediate
error dialog box stating "You may not be able to access file created in the
folder X:\New Folder."
When I select to continue the folder is created, looking on the IRIX side the
file permissions are good and there is no additional ACL information.
If you go into the folder and create a text file it will create it but it will
not be visible on the Windows side. In fact when you browse through the
directories you can see into any folders except those which were created under
3.0.13. I have reinstalled 3.0.12 and do not see any evidence of these problems
so I was curious if there is any IRIX specific changes that I should look for
that was changed between 3.0.12 and 3.0.13?
I am running IRIX 6.5.20 and 6.5.26, Winodws 2000 and Windows XP.
And configured it with the following options:
./configure --cache-file=/dev/null \
--prefix=/usr/local/samba \
--with-libiconv=/usr/local \
--with-acl-support \
--without-ldap \
--without-ads \
--without-python
Although I have also tried it without the ACL support with the same results.
Any suggestions would be greatly appreciated.
Cale Fairchild
Systems Administrator
Computer Science
Brock University
cale@brocku.ca
Cale Fairchild skrev:> Over the weekend I upgraded my IRIX servers to 3.0.13 and have found > many strange issues regarding the creation of new folders.From what? Haven't used Irix for years, but: Use 3.0.14 (just released). There have been so many bug reports for 3.0.13, and so many impromptu patches, that I've put off my own upgrades from 3.0.11 (works perfectly on my RHAS3 sites) to 3.0.14 - and even then I'm going to wait a week or so for more bug reports. --Tonni -- mail: tonye@billy.demon.nl http://www.billy.demon.nl They love us, don't they, They feed us, won't they ...
> -----Original Message----- > From: Tony Earnshaw [mailto:tonye@billy.demon.nl]> Use 3.0.14 (just released). There have been so many bug reports for > 3.0.13, and so many impromptu > patches, that I've put off my own upgrades from 3.0.11 (works > perfectly > on my RHAS3 sites) to 3.0.14 - and even then I'm going to wait a week > or so for more bug reports.I'm hanging back, too...just too much weirdness going on with 3.0.12/13/14 so far for my taste.
I have looked into this further and need to ammend the reported problems. It seems that on servers which have issues regarding this problem it was introduced with version 3.0.12 not 3.0.13. Interestingly enough I installed it on an IRIX server (same OS version) that has never had Samba installed on it and both 3.0.12 and 3.0.13 work fine. I have used the same smb.conf file on both and have the same directory structure in the shared folder. On the server that demonstrates problems the file listing problem does not seem to be limited to a newly created directory, in fact it seems that the directory count interally in Samba comes back short. I looked at the level 5 logs of the same server running 3.0.11 and then 3.0.12 and here are the only noticable differences 1926c1914 < start_dir dir=./ ---> dptr_create dir=./2090c2078 < dptr_num is 256, mask = *, attr = 16, dirptr=(0x10303758,142) ---> dptr_num is 256, mask = *, attr = 16, dirptr=(0x1048C7F0,2019361245)2210d2197 < get_lanman2_dir_entry found ./.desktophost fname=.desktophost 2213c2200 < SMBtrans2 mask=* directory=./ dirtype=22 numentries=120 ---> SMBtrans2 mask=* directory=./ dirtype=22 numentries=119Is there a possiblity that the second value in 'dirptr=(0x1048C7F0,2019361245)' has overflowed? I also just noticed that dptr_create seems to have replaced start_dir so I will take a look at that code. If anyone else is having this problem it would be good to know. Also any suggestions on where else to look would be appreciated. Thanks. Cale Fairchild Systems Administrator Computer Science Brock University cale@brocku.ca On Tue, 12 Apr 2005, Cale Fairchild wrote:> Over the weekend I upgraded my IRIX servers to 3.0.13 and have found many > strange issues regarding the creation of new folders. > > When I attempt to add a new folder through the Windows side I get an > immediate error dialog box stating "You may not be able to access file > created in the folder X:\New Folder." > > When I select to continue the folder is created, looking on the IRIX side the > file permissions are good and there is no additional ACL information. > > If you go into the folder and create a text file it will create it but it > will not be visible on the Windows side. In fact when you browse through the > directories you can see into any folders except those which were created > under 3.0.13. I have reinstalled 3.0.12 and do not see any evidence of these > problems so I was curious if there is any IRIX specific changes that I should > look for that was changed between 3.0.12 and 3.0.13? > > I am running IRIX 6.5.20 and 6.5.26, Winodws 2000 and Windows XP. > > And configured it with the following options: > > ./configure --cache-file=/dev/null \ > --prefix=/usr/local/samba \ > --with-libiconv=/usr/local \ > --with-acl-support \ > --without-ldap \ > --without-ads \ > --without-python > > Although I have also tried it without the ACL support with the same results. > > Any suggestions would be greatly appreciated. > > Cale Fairchild > Systems Administrator > Computer Science > Brock University > > cale@brocku.ca > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba >
On Wed, Apr 13, 2005 at 02:14:23PM -0400, Cale Fairchild wrote:> I have looked into this further and need to ammend the reported problems. > It seems that on servers which have issues regarding this problem it was > introduced with version 3.0.12 not 3.0.13. > > Interestingly enough I installed it on an IRIX server (same OS version) > that has never had Samba installed on it and both 3.0.12 and 3.0.13 work > fine. I have used the same smb.conf file on both and have the same > directory structure in the shared folder. > > On the server that demonstrates problems the file listing problem does not > seem to be limited to a newly created directory, in fact it seems that the > directory count interally in Samba comes back short. I looked at the level > 5 logs of the same server running 3.0.11 and then 3.0.12 and here are the > only noticable differencesThe code currently in the tree (and being released as 3.0.14) should not have this problem. Get back to me if it does please. Jeremy.
Thanks for another quick response, I have done some poking in the code and found that the cause of the problem for the missing file is that in the function get_lanman2_dir_entry in trans2.c, dname returns false on the last entry of the directory. I also noticed that where changes in the assignment of dname between 11 and 12 < trans2.c.3.0.11> trans2.c.3.0.12--- < prev_dirpos = TellDir(conn->dirptr); < dname = ReadDirName(conn->dirptr); ---> long curr_dirpos = prev_dirpos = dptr_TellDir(conn->dirptr); > dname = dptr_ReadDirName(conn->dirptr,&curr_dirpos,&sbuf);if (!dname) return(False) I am going to try and track it down further but I am wondering if this triggers any thoughts. Another thing that I notice in the code is that I get messages such as: get_lanman2_dir_entry:readdir on dirptr 0x10425968 now at offset -183597246 in the logs, the offset grows through the positive numbers and then it prints negative from high to low (long int overflow) yet the files seem to be shown. However the last entry printed is very close to -1 again (possible overflow of unsigned long?) Sorry to bother you about this again but I don't really know how to approach SGI with this since I don't know how to describe the problem to them so that they understand it and I get differing results with the same OS and the same compilers. Cale Fairchild Systems Administrator Computer Science Brock University cale@brocku.ca On Thu, 14 Apr 2005, Jeremy Allison wrote:> On Thu, Apr 14, 2005 at 03:11:09PM -0400, Cale Fairchild wrote: >> Thanks for the reply, I have just tried out the version in the >> SAMBA_3_0_STABLE branch of the subversion tree, tagged 3.0.14a, and it has >> the same problem. If there is anywhere in particular that I should take a >> look at I would be grateful for suggestions. > > I don't know what to advise. James Peach of SGI can't reproduce your > problem on his versions of IRIX with the same code, and this code works > without problems on all other systems we know of.... Time to get SGI support > heavily involved I think. > > Jeremy. >