Jeremy Allison wrote:
On Mon, Nov 10, 2008 at 08:51:46AM +0100, Marco van Putten wrote:
Corrupt tdb file. Are you storing the tdb files on reiserfs?
If yes, move them to something more robust like ext3. If
you're not using reiserfs, this sounds like flaky hardware
somewhere.
Volker
Thanks
On Mon, Nov 10, 2008 at 08:51:46AM +0100, Marco van Putten wrote:
Corrupt tdb file. Are you storing the tdb files on reiserfs?
If yes, move them to something more robust like ext3. If
you're not using reiserfs, this sounds like flaky hardware
somewhere.
Volker
Thanks Volker.
The tdb
On Sun, Nov 09, 2008 at 06:46:26PM +0100, Marco van Putten wrote:
Thanks for your reply Jeremy.
These are the outputs I got from gdb and strace. It looks like there is
not very much going on... Hopefully it makes some sense to you.
# gdb smbd 32717
(gdb) bt
#0 0x2b55a75a9ddf in
Corrupt tdb file. Are you storing the tdb files on reiserfs?
If yes, move them to something more robust like ext3. If
you're not using reiserfs, this sounds like flaky hardware
somewhere.
Volker
Thanks Volker.
The tdb file is on a ext3 filesystem. The disks themselves are 2 80GB
SATA disks
Jeremy Allison wrote:
On Sat, Nov 08, 2008 at 06:28:42PM +0100, Marco van Putten wrote:
Hi,
We're running Samba (3.0.28-1.el5_2.1) on a Redhat (5.2) server using
winbind to authenticate against a Windows AD.
This all worked fine for a while. But now we have the problem that
(some)
Hi,
We're running Samba (3.0.28-1.el5_2.1) on a Redhat (5.2) server using
winbind to authenticate against a Windows AD.
This all worked fine for a while. But now we have the problem that
(some) users coming from Linux clients cause an excessive amount of smbd
processes. We had 1 user who
On Sat, Nov 08, 2008 at 06:28:42PM +0100, Marco van Putten wrote:
Hi,
We're running Samba (3.0.28-1.el5_2.1) on a Redhat (5.2) server using
winbind to authenticate against a Windows AD.
This all worked fine for a while. But now we have the problem that
(some) users coming from Linux
