Re: filesytem bsize=64k causes libc/db hash crash

2002-09-12 Thread Terry Lambert
No... it was a typo. I was too lazy to make it a manifest constant, because to do that, I would have had to hack db.h to change the 65536 to a 32768, and add another manifest constant in a different header for the hash code to use. Sorry. -- Terry Alexander Kabaev wrote: > > On Thu, 12 Sep 20

Re: filesytem bsize=64k causes libc/db hash crash

2002-09-12 Thread Alexander Kabaev
On Thu, 12 Sep 2002 15:23:21 -0700 Terry Lambert <[EMAIL PROTECTED]> wrote: > + if (b.psize > 32768) > +b.psize = 32868; 32768 vs. 32868 intentional here? -- Alexander Kabaev To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe free

Re: filesytem bsize=64k causes libc/db hash crash

2002-09-12 Thread Terry Lambert
Norikatsu Shigemura wrote: > I found a problem on 4-STABLE(maybe 5-CURRENT, too) with libc/db > (BerkeleyDB 1). It that when block size on fs is 65536 bytes, > many programs which use BerkeleyDB(dev_mkdb, cap_mkdb, etc..) are > crash. Here is a patch; it's ugly, b

filesytem bsize=64k causes libc/db hash crash

2002-09-12 Thread Norikatsu Shigemura
I found a problem on 4-STABLE(maybe 5-CURRENT, too) with libc/db (BerkeleyDB 1). It that when block size on fs is 65536 bytes, many programs which use BerkeleyDB(dev_mkdb, cap_mkdb, etc..) are crash. [REPLICATE THE TEST] # dd if=/dev/zero of=/dev/t