>>> On 3/19/2009 at 3:47 PM, Mark D Vandale <[email protected]> wrote: > I just received some additional information that I hadn't realized. Our > Sles10 server is mounting this area from a SMB server on zOS, and it's that > SMB that doesn't support the type "cifs", that's why I can't use it.
Makes sense. > Using the mount in fstab with type of smbfs, it works at boot up time. At > some point later and I'm not sure how much later, the mount point gets > hung up and stops responding, "Device busy". If I try to umount it I also > get Device busy. > > What could be causing this ? Is it better to issue a "smbmount", is > there any difference between mounting in fstab with type smbfs or issuing a > straight smbmount cmd ? No clue, really, what that would be happening. There is no difference between the two methods. In fact, if you look at /sbin/mount.smbfs (what the mount command would invoke for an smbfs mount type), it is a symbolic link to /usr/sbin/smbmount. So either way, you're going to the same code. I have to wonder why you're using an SMB share on z/OS rather than NFS. The SMB server was created to allow Windows users to connect, since most Windows systems didn't have an NFS client. Everyone else was expected to use NFS, not least because it's an open standard that developers can actually get access to read. Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
