| To: | "'Dave Chinner'" <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | RE: XFS memory allocation deadlock in 2.6.38 |
| From: | Sean Noonan <Sean.Noonan@xxxxxxxxxxxx> |
| Date: | Wed, 23 Mar 2011 18:33:04 -0400 |
| Accept-language: | en-US |
| Acceptlanguage: | en-US |
| Cc: | "'linux-xfs@xxxxxxxxxxx'" <linux-xfs@xxxxxxxxxxx>, Martin Bligh <Martin.Bligh@xxxxxxxxxxxx>, Trammell Hudson <Trammell.Hudson@xxxxxxxxxxxx> |
| In-reply-to: | <20110323220345.GD26611@dastard> |
| References: | <081DDE43F61F3D43929A181B477DCA95639B52E8@xxxxxxxxxxxxxxxxxxxx> <20110322232504.GC15270@dastard> <081DDE43F61F3D43929A181B477DCA95639B532C@xxxxxxxxxxxxxxxxxxxx> <20110323220345.GD26611@dastard> |
| Thread-index: | Acvppjh5mjFB+Va2T1GGTvpxjvayHgAA9vnQ |
| Thread-topic: | XFS memory allocation deadlock in 2.6.38 |
> So why would creating a 16GB file cause and OOM condition if you > have 48GB RAM? That doesn't make a whole lot of sense to me. Is > that memory free, of are other things running and consuming memory? As far as I know this isn't an OOM condition. It is a bug, which is why I sent a patch that fixes this specific case earlier today. Sean |
| Previous by Date: | Re: XFS memory allocation deadlock in 2.6.38, Dave Chinner |
|---|---|
| Next by Date: | Re: xfs: outstanding patches for 2.6.39, Dave Chinner |
| Previous by Thread: | Re: XFS memory allocation deadlock in 2.6.38, Dave Chinner |
| Next by Thread: | RE: XFS memory allocation deadlock in 2.6.38, Sean Noonan |
| Indexes: | [Date] [Thread] [Top] [All Lists] |