| To: | Jan-Frode Myklebust <janfrode@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: bugzilla vs. bugzilla |
| From: | Eric Sandeen <sandeen@xxxxxxx> |
| Date: | Wed, 28 Jul 2004 13:09:32 -0500 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20040728163220.GA28915@ii.uib.no> |
| Organization: | Eric Conspiracy Secret Labs |
| References: | <20040728103708.GA26088@ii.uib.no> <Pine.LNX.4.44.0407281035240.32423-100000@penguin.americas.sgi.com> <20040728163220.GA28915@ii.uib.no> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
On Wed, 2004-07-28 at 11:32, Jan-Frode Myklebust wrote: > > FWIW, it looks like you're getting memory allocation failures > > in some of these cases. > > Meaning xfs problems, other kernel component error, or hw? Well, xfs is not good at failing memory allocations - irix would happily wait forever for memory, rather than failing. Linux 2.6 should now also have this feature (allocations that can wait forever) but for a while (IIRC) there was a problem where memory allocation -could- fail, xfs doesn't check for this, and kablooey. -Eric -- Eric Sandeen [C]XFS for Linux http://oss.sgi.com/projects/xfs sandeen@xxxxxxx SGI, Inc. 651-683-3102 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: bugzilla vs. bugzilla, Jan-Frode Myklebust |
|---|---|
| Next by Date: | Re: XFS: how to NOT null files on fsck?, Nathan Scott |
| Previous by Thread: | Re: bugzilla vs. bugzilla, Jan-Frode Myklebust |
| Next by Thread: | Re: bugzilla vs. bugzilla, Jan-Frode Myklebust |
| Indexes: | [Date] [Thread] [Top] [All Lists] |