Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 31 Aug 2007 23:04:37 +0200
From:      Kenneth Vestergaard Schmidt <kvs@pil.dk>
To:        Pawel Jakub Dawidek <pjd@FreeBSD.org>
Cc:        freebsd-fs@freebsd.org
Subject:   Re: ZFS: 'checksum mismatch' all over the place
Message-ID:  <m13axza00q.fsf@binarysolutions.dk>
In-Reply-To: <m1ps1iz9bi.fsf@binarysolutions.dk> (Kenneth Vestergaard Schmidt's message of "Mon\, 20 Aug 2007 14\:20\:33 %2B0200")
References:  <m1wsvtkviw.fsf@binarysolutions.dk> <20070820112946.GC16977@garage.freebsd.pl> <m1ps1iz9bi.fsf@binarysolutions.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
Kenneth Vestergaard Schmidt <kvs@pil.dk> writes:
>> How do you know it was fine? Did you have something that did
>> checksumming? You could try geli with integrity verification feature
>> turned on, fill the disks with some random data and then read it back,
>> if your controller corrupts the data, geli should tell you this.
>
> I may have to do this. The previous drive was almost filled to the brim
> with data, which rsync looked at each day, and we didn't have a lot of
> re-transfer, but that doesn't necessarily mean anything.

*blush*

This turned out to be a firmware-issue with the Eonstor
RAID-enclosure. After upgrading to v3.47, everything is fine in the
checksum-department.

Now, however, I can't seem to keep the box running. We've rsync'd 1.56
TB data to an 8.18 TB raidz2 pool, and we're getting panics all the
time.

It's an x86 with 4 GB RAM. I've got the following in /boot/loader.conf:

  vfs.zfs.prefetch_disable="1"
  vfs.zfs.arc_max="107772160"
  vm.kmem_size_max="629145600"
  vm.kmem_size_min="629145600"

and kern.maxvnodes is set to 50000. When the machine is finished
booting, 'vmstat -m' says:

         Type InUse MemUse HighUse Requests  Size(s)
      solaris 49972 158199K       -   455307  16,32,64,128,256,512,1024,2048,4096

and after about an hours worth of rsync'ing, we get:

         Type InUse MemUse HighUse Requests  Size(s)
      solaris 198797 449675K       - 404226785  16,32,64,128,256,512,1024,2048,4096
  panic: kmem_malloc(28672): kmem_map too small: 614682624 total allocated

I'm not quite sure what knobs to twiddle with, or what values to watch,
so any help in this department would be much appreciated. I'm sure it'd
be nice to update the Wiki, too, with that info, since the values there
don't make things stable.

-- 
Kenneth Schmidt
pil.dk



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m13axza00q.fsf>