From: Boaz Harrosh <bharrosh@panasas.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: linux-scsi@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Large amount of scsi-sgpool objects
Date: Tue, 03 Mar 2009 11:31:42 +0200 [thread overview]
Message-ID: <49ACF8FE.2020904@panasas.com> (raw)
In-Reply-To: <alpine.LSU.2.00.0903030220050.2438@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> Hi,
>
>
> I am noticing that there are a lot of objects active after a few tens
> minutes of running xfs_fsr.
>
> $ slabtop
> OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME
> 818616 818616 100% 0.16K 34109 24 136436K sgpool-8
> 253692 253692 100% 0.62K 42282 6 169128K sgpool-32
> 52017 52016 99% 2.50K 17339 3 138712K sgpool-128
> 26220 26219 99% 0.31K 2185 12 8740K sgpool-16
> 8927 8574 96% 0.03K 79 113 316K size-32
>
Looks like a leak, by failing to call scsi_release_buffers()
somehow. (Which was changed recently)
> $ uname -a
> Linux yaguchi 2.6.29-rc6-rt #1 SMP PREEMPT RT 2009-02-19 23:12:33
> +0100 i686 athlon i386 GNU/Linux
>
Did you have a chance to try exact same thing with vanilla 2.6.29-rc6?
try a bisect -- drivers/scsi/scsi_lib.c there should not be more then
a couple of patches
> What could be the problem that there are so many objects around and not
> freed?
Only one reason, failing to call scsi_release_buffers()
There should not be more then .can_queue sg-pool objects in flight
per disk. Which is rarely more then 255
This makes the system pretty much unusable after a while as it
> runs towards a low-memory condition.
>
> $ free
> total used free shared buffers cached
> Mem: 766592 758688 7904 0 0 137184
> -/+ buffers/cache: 621504 145088
> Swap: 795136 32 795104
>
>
> $ cat /proc/meminfo
> MemTotal: 766592 kB
> MemFree: 79388 kB
> Buffers: 0 kB
> Cached: 62120 kB
> SwapCached: 1428 kB
> Active: 74472 kB
> Inactive: 113524 kB
> Active(anon): 58228 kB
> Inactive(anon): 69124 kB
> Active(file): 16244 kB
> Inactive(file): 44400 kB
> Unevictable: 0 kB
> Mlocked: 0 kB
> HighTotal: 0 kB
> HighFree: 0 kB
> LowTotal: 766592 kB
> LowFree: 79388 kB
> SwapTotal: 795136 kB
> SwapFree: 792404 kB
> Dirty: 0 kB
> Writeback: 0 kB
> AnonPages: 124440 kB
> Mapped: 13672 kB
> Slab: 478576 kB
> SReclaimable: 5316 kB
> SUnreclaim: 473260 kB
> PageTables: 1220 kB
> NFS_Unstable: 0 kB
> Bounce: 0 kB
> WritebackTmp: 0 kB
> CommitLimit: 1178432 kB
> Committed_AS: 4294655912 kB
> VmallocTotal: 245816 kB
> VmallocUsed: 27404 kB
> VmallocChunk: 197108 kB
> HugePages_Total: 0
> HugePages_Free: 0
> HugePages_Rsvd: 0
> HugePages_Surp: 0
> Hugepagesize: 4096 kB
> DirectMap4k: 696256 kB
> DirectMap4M: 90112 kB
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Please try some more tests, could it be a race that gets exposed in -rt?
Boaz
next prev parent reply other threads:[~2009-03-03 9:32 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 1:28 Large amount of scsi-sgpool objects Jan Engelhardt
2009-03-03 9:31 ` Boaz Harrosh [this message]
2009-03-03 15:21 ` James Bottomley
2009-03-03 16:08 ` Jan Engelhardt
2009-03-03 16:24 ` Boaz Harrosh
2009-03-03 17:59 ` Alan Stern
2009-03-03 20:56 ` Ingo Molnar
2009-03-03 21:06 ` Alan Stern
2009-03-03 16:25 ` James Bottomley
2009-03-03 17:19 ` Thomas Gleixner
2009-03-03 22:07 ` [BUG] 2.6.29-rc6-2450cf in scsi_lib.c (was: Large amount of scsi-sgpool)objects Thomas Gleixner
2009-03-03 22:22 ` Jan Engelhardt
2009-03-03 23:07 ` Thomas Gleixner
2009-03-03 22:26 ` James Bottomley
2009-03-04 2:01 ` Thomas Gleixner
2009-03-04 18:55 ` James Bottomley
2009-03-04 21:45 ` Thomas Gleixner
2009-03-04 22:56 ` James Bottomley
2009-03-05 0:13 ` James Bottomley
2009-03-05 8:36 ` FUJITA Tomonori
2009-03-05 8:39 ` FUJITA Tomonori
2009-03-05 9:29 ` FUJITA Tomonori
2009-03-05 10:09 ` Jens Axboe
2009-03-05 10:14 ` Jens Axboe
2009-03-05 10:27 ` FUJITA Tomonori
2009-03-05 10:30 ` Jens Axboe
2009-03-05 10:41 ` FUJITA Tomonori
2009-03-05 11:10 ` Jens Axboe
2009-03-05 11:40 ` FUJITA Tomonori
2009-03-05 10:41 ` Ingo Molnar
2009-03-05 11:05 ` Jens Axboe
2009-03-05 11:07 ` Ingo Molnar
2009-03-05 12:09 ` Thomas Gleixner
2009-03-05 23:16 ` Thomas Gleixner
2009-03-05 19:32 ` Ingo Molnar
2009-03-05 10:15 ` Ingo Molnar
2009-03-03 19:22 ` Large amount of scsi-sgpool objects Ingo Molnar
2009-03-03 21:25 ` James Bottomley
2009-03-03 21:44 ` Ingo Molnar
2009-03-03 22:39 ` James Bottomley
2009-03-03 23:03 ` Ingo Molnar
2009-03-03 23:32 ` Stefan Richter
2009-03-03 23:48 ` Ingo Molnar
2009-03-04 6:39 ` Stefan Richter
2009-03-04 7:12 ` Mike Galbraith
2009-03-04 7:50 ` Stefan Richter
2009-03-04 8:00 ` Mike Galbraith
2009-03-04 9:06 ` Thomas Gleixner
2009-03-04 11:12 ` Ingo Molnar
2009-03-04 11:28 ` Stefan Richter
2009-03-04 11:47 ` Ingo Molnar
2009-03-04 12:02 ` Stefan Richter
2009-03-04 11:24 ` Ingo Molnar
2009-03-04 19:11 ` Andrew Morton
2009-03-04 20:09 ` Thomas Gleixner
2009-03-04 0:01 ` James Bottomley
2009-03-04 0:39 ` Ingo Molnar
2009-03-04 0:30 ` Thomas Gleixner
2009-03-04 0:47 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49ACF8FE.2020904@panasas.com \
--to=bharrosh@panasas.com \
--cc=jengelh@medozas.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox