Hi!
We have a number of Samba servers installed and they seem to be running
fairly flawlessly. On all our systems, we have installed the Samba code on a
locally attached disk. On a new project I am working on, I would like to
install the Samba executables on a network disk. For some unknown reason, I
can't get the Samba to work when attached to my network disk. I have the
same code installed on the local disk, and Samba works fine. I am getting
the following error message logged in the smbd log file.
tdb(/opt2/samba/private/secrets.tdb): tdb_reopen: failed to obtain active
lock
[2002/01/25 09:21:59, 0, pid=18533, effective(0, 0), real(0, 0)]
tdb/tdbutil.c:tdb_log(342)
And I do allow the Samba server root access on the NFS share. Any ideas on
where the problem may lie or a configuration step that I am leaving out?
Samba 2.2.2
Solaris 2.8
Thanks,
Brett Bartick
Vice President
Corporate Technology
Nomura Securities International
25 Corporate Place South
Piscataway, NJ 08854
bbartick@us.nomura.com
-----This message is for the named person's use only. It may contain
confidential, proprietary or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission. If
you receive this message in error, please delete it and all copies from your
system, destroy any hard copies and notify the sender. You must not,
directly or indirectly, use, disclose, distribute, print, or copy any part
of this message if you are not the intended recipient. Nomura Holding
America Inc., Nomura Securities International, Inc, and their respective
subsidiaries each reserve the right to monitor all e-mail communications
through its networks. Any views expressed in this message are those of the
individual sender, except where the message states otherwise and the sender
is authorized to state the views of such entity. Unless otherwise stated,
any pricing information in this message is indicative only, is subject to
change and does not constitute an offer to deal at any price quoted. Any
reference to the terms of executed transactions should be treated as
preliminary only and subject to our formal written confirmation.
-------------- next part --------------
HTML attachment scrubbed and removed
> "Bartick, Brett" wrote: > We have a number of Samba servers installed and they seem to be > running fairly flawlessly. On all our systems, we have installed the > Samba code on a locally attached disk. On a new project I am working > on, I would like to install the Samba executables on a network disk.You can share date that lives on an nfs-mounted disk (at a performance cost) but please don't try to run samba from one: it needs non-nfs locking on the files in its lock directory.> tdb(/opt2/samba/private/secrets.tdb): tdb_reopen: failed to obtain > active lock > [2002/01/25 09:21:59, 0, pid=18533, effective(0, 0), real(0, 0)] > tdb/tdbutil.c:tdb_log(342)--dave -- David Collier-Brown, | Always do right. This will gratify Performance & Engineering | some people and astonish the rest. Americas Customer Engineering, | -- Mark Twain (905) 415-2849 | davecb@canada.sun.com
On Fri, 25 Jan 2002, Bartick, Brett wrote:> Hi! > > We have a number of Samba servers installed and they seem to be > running fairly flawlessly. On all our systems, we have installed the > Samba code on a locally attached disk. On a new project I am working > on, I would like to install the Samba executables on a network disk. > For some unknown reason, I can't get the Samba to work when attached > to my network disk. I have the same code installed on the local disk, > and Samba works fine. I am getting the following error message logged > in the smbd log file.tdb's make extensive use of mmap() which requires functional, byte range locking. You don't get this over NFS. Define "lock directory" (and the private/) to be a local directory and things should be ok. chau, jerry --------------------------------------------------------------------- Hewlett-Packard http://www.hp.com SAMBA Team http://www.samba.org -- http://www.plainjoe.org "Sam's Teach Yourself Samba in 24 Hours" 2ed. ISBN 0-672-32269-2 --"I never saved anything for the swim back." Ethan Hawk in Gattaca--
Thanks for the extremely quick response! I thought that might be the problem. My idea was to load the executables on our NFS service group under Veritas Cluster 2.0. Thinking, if node 1 failes, I can just bring up node 2 which will see the same executables, configuration information, locks, etc. Guess that is a bad idea. So, what do people suggest to use in keeping 2 or more nodes in sync? Just use Rsync? Brett -----Original Message----- From: David Collier-Brown [mailto:davecb@canada.sun.com] Sent: Friday, January 25, 2002 9:51 AM To: Bartick, Brett Cc: 'samba@lists.samba.org' Subject: Re: Problems running Samba from a NFS filesystem> "Bartick, Brett" wrote: > We have a number of Samba servers installed and they seem to be > running fairly flawlessly. On all our systems, we have installed the > Samba code on a locally attached disk. On a new project I am working > on, I would like to install the Samba executables on a network disk.You can share date that lives on an nfs-mounted disk (at a performance cost) but please don't try to run samba from one: it needs non-nfs locking on the files in its lock directory.> tdb(/opt2/samba/private/secrets.tdb): tdb_reopen: failed to obtain > active lock > [2002/01/25 09:21:59, 0, pid=18533, effective(0, 0), real(0, 0)] > tdb/tdbutil.c:tdb_log(342)--dave -- David Collier-Brown, | Always do right. This will gratify Performance & Engineering | some people and astonish the rest. Americas Customer Engineering, | -- Mark Twain (905) 415-2849 | davecb@canada.sun.com -----This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please delete it and all copies from your system, destroy any hard copies and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Nomura Holding America Inc., Nomura Securities International, Inc, and their respective subsidiaries each reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state the views of such entity. Unless otherwise stated, any pricing information in this message is indicative only, is subject to change and does not constitute an offer to deal at any price quoted. Any reference to the terms of executed transactions should be treated as preliminary only and subject to our formal written confirmation. -------------- next part -------------- HTML attachment scrubbed and removed