Good morning Richard, On 12/5/18 10:05 AM, Richard Alloway wrote: > Hi Neil! > > I got this email address from the Contact page of your neil.brown.name website and hope that you can point me in the right direction. In case it isn't obvious, this is the public mailing list for generic Linux Software Raid and related topics, not Neil's personal address. And though he still contributes, he gave up maintainership a few years ago. Participants here are generally volunteers with varied experience and platforms, fwiw. Speaking of platforms: > ================================================ > Dec 4 16:44:26 localhost kernel: TRACE raid6-md0 alloc 0xffff8e6ed57b7480 inuse=17 fp=0x (null) > Dec 4 16:44:26 localhost kernel: CPU: 3 PID: 443 Comm: md0_raid6 Not tainted 3.10.0-862.3.3.el7.x86_64.debug #1 > Dec 4 16:44:26 localhost kernel: Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 When I first saw this, I thought "Hmmm. a job for RedHat support, not the linux-raid ML". > ================================================ > # uname -r > 4.19.5-1.el7.elrepo.x86_64 So some readers may have missed your testing on a fairly current kernel. However, it may still be a RedHat question, as very old commercial software is in the mix (Vbox). > Do you have any suggestions on how I can troubleshoot this further? Consider setting up a test environment on bare metal with a vanilla kernel and repeating your testing. Reply to this thread to keep it together. Or set up an EL7 environment with their latest kernel on bare metal and retest. If still occurring, open a ticket with RedHat and report both there and here (we'll still be interested). I haven't seen anything in recent kernels that would explain your memory leak, other than a driver losing track of an I/O request. (FWIW, I'm not a kernel developer -- just a power user -- though I do have substantial non-kernel C experience.) Phil
