xfs
[Top] [All Lists]

Re: [PATCH 00/30] xfsprogs: Initial CRC support

To: Jeff Liu <jeff.liu@xxxxxxxxxx>
Subject: Re: [PATCH 00/30] xfsprogs: Initial CRC support
From: "Michael L. Semon" <mlsemon35@xxxxxxxxx>
Date: Sat, 18 May 2013 02:27:19 -0400
Cc: Dave Chinner <david@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=2tiaisr5Uq+cH6EnUykXVnAaYPWYLBXWyIbe1+x/JAQ=; b=YefzCAXA3URfld4E99kIYCNXDPzWFMl+Fg8Q6KK6V/rZ+bwoIyWEo+s6bCvtE5/6dQ R/0G6M/BJttZhFBn4N9qjbMdqSZxQbd4VJ1kaCs8uW0vF/ES93dYcvXhSz7L41YHPI7X +1grxEDwfSXtZmO+TDsWBG/u0VpaR0yzTSxqbCufPdsJy7jbj1jgquomIFzqYTnk/dv+ FH/s4C4VRlJaIkPuwsKP2szjC/x5sdNFI4PCaeALCQoG1IrReunBcQhVYnwOA6tPrE70 Hx4PyB2UfRQH/vMMR9Buq6w1R4hVnlYBQpL2x1FVu6PZg9N7yRO5b9yqS37jcuYgDvM7 ZE8g==
In-reply-to: <51970C90.5050005@xxxxxxxxxx>
References: <1368789205-19969-1-git-send-email-david@xxxxxxxxxxxxx> <51969917.2080209@xxxxxxxxx> <20130518032507.GA6495@dastard> <51970C90.5050005@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
On 05/18/2013 01:07 AM, Jeff Liu wrote:

Looks our test for 32-bit system is insufficient.  There has another bug
reports regarding 32-bit yesterday:
http://oss.sgi.com/archives/xfs/2013-05/msg00494.html

I read this and did not chime in because I don't know about the "no space left on device" error.

The first issue the customer had, though, was one I had on a 2.8GHz Pentium 4. The idea of using a tunable to increase vmalloc space made me think, "What, am I using FreeBSD or something? Why didn't Linux auto-tune this?" so I dug deeper. [Disclaimer: I use FreeBSD and find value in it, but it requires at least some sysctl tuning for things that Linux will tune automatically.]

Basically, I had vmalloc space to have an environment set up perfectly in 768 MB of RAM. Then I added another 512 MB, and Linux saw only 896 MB for lack of highmem support. At that point I enabled highmem support, Linux decided to auto-tune my vmalloc space down to 128 MB, which was not enough to handle an xfsdump of a 30 GB device-mapper crypt partition. The PC, when left alone, could develop those same oops-y messages while doing incremental xfsdumps overnight, and if left alone for days, even simple cp commands could cause issues. My resolution was to use the CONFIG_VMSPLIT_2G kernel option and reduce the things reported by /proc/vmallocinfo that are vmalloc items. Some ioremap items in /proc/vmallocinfo were removed where convenient. Despite warnings on the Internet like "this breaks ELF" and "this breaks binary modules," I've had no issues with it in the nine months in which the kernel has operated this way. [Note: I don't use binary modules. For that matter, only that PC uses modules at all.] Ultimately, I got rid of the crypts as well, but not before verifying that the above setup did indeed solve the problem at hand.

It's only my two cents, one person trying to balance Internet research against what actually works in testing on one PC. If the solution is sane sane to you, feel free to forward this story to your customer to see if anything in it will help.

So I'm going to setup a 32-bit test environment for such tests together
with Michael.

Excellent! Let me know a little about your test environment and whether it's a VM or bare metal.

Michael

<Prev in Thread] Current Thread [Next in Thread>