I have a Sun 7310 storage server. This is
running Solaris 10 but it's self-contained
and I can't login to it or run Samba on it.
I manage it with a web interface.
I have a CentOS 5.3 machine that mounts
a bunch of file systems via NFS from the
Sun server. This works fine. I installed
Samba 3.4.5 on the CentOS machine and
configured it to share some of the directories
that are actually NFS mounts from the Sun
server. I'm able to map these directories
from both Windows XP and Windows 7.
I'm seeing several problems:
1) Accessing the mapped directories from
Windows when running Microsoft Office apps is
extremely slow. I don't have any exact numbers
but let's say the speed is unusable. Ironically,
other programs, such as 'vim' and 'notepad'
don't have this speed problem when accessing
the same shares.
2) Again, using Microsoft Office apps, Windows XP
machines see files as read-only. Windows 7 works
fine on the same files.
The Sun has a non-Samba CIFS implementation
but it's non-intuitive to set up so I haven't
tried it. I'm wondering if what I describe
should work.
Here's the smb.conf configuration for the share:
[bgroup]
valid users = bgroup
path = /home/bgroup
public = no
writeable = yes
browseable = no
create mask = 012
create mode = 0660
directory mode = 0770
Any comments or suggestions?
Cordially,
--
Jon Forrest
Research Computing Support
College of Chemistry
173 Tan Hall
University of California Berkeley
Berkeley, CA
94720-1460
510-643-1032
jlforrest at berkeley.edu
On Fri, Jan 22, 2010 at 04:49:33PM -0800, Jon Forrest wrote:> I have a Sun 7310 storage server. This is > running Solaris 10 but it's self-contained > and I can't login to it or run Samba on it. > I manage it with a web interface. > > I have a CentOS 5.3 machine that mounts > a bunch of file systems via NFS from the > Sun server. This works fine. I installed > Samba 3.4.5 on the CentOS machine and > configured it to share some of the directories > that are actually NFS mounts from the Sun > server. I'm able to map these directories > from both Windows XP and Windows 7. > > I'm seeing several problems: > > 1) Accessing the mapped directories from > Windows when running Microsoft Office apps is > extremely slow. I don't have any exact numbers > but let's say the speed is unusable. Ironically, > other programs, such as 'vim' and 'notepad' > don't have this speed problem when accessing > the same shares. > > 2) Again, using Microsoft Office apps, Windows XP > machines see files as read-only. Windows 7 works > fine on the same files. > > The Sun has a non-Samba CIFS implementation > but it's non-intuitive to set up so I haven't > tried it. I'm wondering if what I describe > should work. > > Here's the smb.conf configuration for the share: > > [bgroup] > > valid users = bgroup > path = /home/bgroup > public = no > writeable = yes > browseable = no > create mask = 012 > create mode = 0660 > directory mode = 0770 > > Any comments or suggestions? > > Cordially,First of all, you really don't want to re-export NFS mounts via Samba. Secondly, if you absolutely must do it, I recommend the following settings: [global] # your other options here... oplocks = No level2 oplocks = No On certain shares, you may want to set: posix locking = No Ray
On Fri, Jan 22, 2010 at 04:49:33PM -0800, Jon Forrest wrote:> I have a Sun 7310 storage server. This is > running Solaris 10 but it's self-contained > and I can't login to it or run Samba on it. > I manage it with a web interface.You need to get over that. Running Samba on NFS imports is a really bad idea. At least every month people report strange lockups, timeouts and other weird things on this list that can be attributed to NFS imports. You should really contact SUN for information how to log into that box and install Samba. Volker -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: <http://lists.samba.org/pipermail/samba/attachments/20100123/4f8ed140/attachment.pgp>
The Sun 7310 is a storage appliance. It is not running Solaris 10 but runs an OS based on Open Solaris with CIFS and Windows style authentication integrated in the kernel. Installing Samba is not an option. You really should be using the integrated CIFs server. It is probably simpler to set up than Samba but is probably not as flexible (has fewer configuration options). There is a simulator you can play with to learn how to set it up. Sun offer courses on setting it up. Sun offer a service to set it up for you. The manual is available on the Internet or from the storage device. There is a forum where these devices are discussed. You almost certainly got a support contract when you bough the device. If you cannot use its CIFS server (ie if you are using a NT 4 style domain or a Samba PDC) perhaps using iSCSI to the Linux box and sharing with Samba is the next best option. See: http://wikis.sun.com/display/FishWorks/Fishworks http://forums.sun.com/forum.jspa?forumID=831 Nick Jon Forrest wrote:> I have a Sun 7310 storage server. This is > running Solaris 10 but it's self-contained > and I can't login to it or run Samba on it. > I manage it with a web interface. > > I have a CentOS 5.3 machine that mounts > a bunch of file systems via NFS from the > Sun server. This works fine. I installed > Samba 3.4.5 on the CentOS machine and > configured it to share some of the directories > that are actually NFS mounts from the Sun > server. I'm able to map these directories > from both Windows XP and Windows 7. > > I'm seeing several problems: > > 1) Accessing the mapped directories from > Windows when running Microsoft Office apps is > extremely slow. I don't have any exact numbers > but let's say the speed is unusable. Ironically, > other programs, such as 'vim' and 'notepad' > don't have this speed problem when accessing > the same shares. > > 2) Again, using Microsoft Office apps, Windows XP > machines see files as read-only. Windows 7 works > fine on the same files. > > The Sun has a non-Samba CIFS implementation > but it's non-intuitive to set up so I haven't > tried it. I'm wondering if what I describe > should work. > > Here's the smb.conf configuration for the share: > > [bgroup] > > valid users = bgroup > path = /home/bgroup > public = no > writeable = yes > browseable = no > create mask = 012 > create mode = 0660 > directory mode = 0770 > > Any comments or suggestions? > > Cordially, >