Am 30.11.2011 14:50, schrieb Michael Wood:
On 30 November 2011 14:21, Volker Lendecke<[email protected]> wrote:
On Wed, Nov 30, 2011 at 01:49:28PM +0200, Michael Wood wrote:
On 30 November 2011 11:38, Volker Lendecke<[email protected]> wrote:
[...]
Nov 30 07:00:24 dc smbd[16828]: tdb(/var/lib/samba/locking.tdb): tdb_rec_read
bad magic 0x42424242 at offset=3494648
In the past these problems have often been caused by bad
hardware.
If it's bad hardware, where does the "BBBB" come from? Seems sort of
unlikely (although, of course, not impossible.)
Does tdb ever set things to 0x42424242 somewhere in order to mark it
as "freed" or something? I don't see anything like that from a
cursory glance at the code, though.
Newly allocated file space will be filled with that pattern.
If you have different proof that we have a software bug and
a patch, I would be more than happy to review it.
I'm sure you would :)
This is not a problem that is happening to me (I am not skull), and I
of course do not have any proof that this is a software bug, let alone
a patch. I just found it strange that a hardware problem would cause
"BBBB" to be found where some sort of TDB magic value was expected.
You, of course, have infinitely more experience with this sort of
thing than I have. I just thought I'd ask.
With best regards,
Same here.
i have no idea what you guys are talking about ;)
but i will replace the server ram on friday. i will report if it fixed
the problem or not.
if not: i will start posting error logs again anyway.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
