| To: | Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Could not allocate buf during xfs_fsr? |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Mon, 27 Mar 2006 07:57:17 +1000 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <Pine.LNX.4.64.0603260919080.17017@p34>; from jpiszcz@xxxxxxxxxxxxxxx on Sun, Mar 26, 2006 at 09:19:54AM -0500 |
| References: | <Pine.LNX.4.64.0603260919080.17017@p34> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Sun, Mar 26, 2006 at 09:19:54AM -0500, Justin Piszcz wrote: > What does this mean? > > Mar 26 08:32:30 p34 fsr[14207]: could not allocate buf: > /d3/.fsr/ag14/tmp14207 > Mar 26 08:32:30 p34 fsr[14207]: could not allocate buf: > /d3/.fsr/ag15/tmp14207 > Mar 26 08:32:30 p34 fsr[14207]: could not allocate buf: > /d3/.fsr/ag0/tmp14207 > Mar 26 08:32:30 p34 fsr[14207]: could not allocate buf: > /d3/.fsr/ag1/tmp14207 > > The FS is 373GB, with 221GB used and 153GB available. Its failing to allocate memory via memalign(2) -- can you run fsr with '-d' and report back? - looks like that will show the size of buffer it attempted to allocate. thanks. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Could not allocate buf during xfs_fsr?, Ralf Hildebrandt |
|---|---|
| Next by Date: | Re: kernel BUG at fs/direct-io.c:916!, Nathan Scott |
| Previous by Thread: | Re: Could not allocate buf during xfs_fsr?, Nathan Scott |
| Next by Thread: | Re: Could not allocate buf during xfs_fsr?, Justin Piszcz |
| Indexes: | [Date] [Thread] [Top] [All Lists] |