| To: | Andrew Morton <akpm@xxxxxxxxx> |
|---|---|
| Subject: | Re: xfsdump stuck in io_schedule |
| From: | Chris Wedgwood <cw@xxxxxxxx> |
| Date: | Sat, 16 Nov 2002 01:38:12 -0800 |
| Cc: | zlatko.calusic@xxxxxxxx, Andi Kleen <ak@xxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <3DD57602.857AD62D@xxxxxxxxx> |
| References: | <dnfzu3yw8u.fsf@xxxxxxxxxxxxxxxxx> <20021115135233.A13882@xxxxxxxxxxxxxxxx> <dnlm3v9ebk.fsf@xxxxxxxxxxxxxxxxx> <20021115140635.A31836@xxxxxxxxxxxxx> <dnr8dmj1i1.fsf@xxxxxxxxxxxxxxxxx> <3DD57602.857AD62D@xxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4i |
On Fri, Nov 15, 2002 at 02:32:34PM -0800, Andrew Morton wrote: > Does xfs_dump actually pin 700 megs of memory?? No. > If someone could provide a detailed description of what xfs_dump is > actually doing internally, that may help me shed some light. > xfs_dump is actually using kernel support for coherency reasons, is > that not so? How does it work? It uses bulkstat; I'm not convinced that alone is the problem (I have other applications that use it and never caused the kinds of lockups). --cw |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfs performance on scsi in 2.4.20-rc1, Robert Sander |
|---|---|
| Next by Date: | [Bug 195] New: xfs_fsr results in oops, bugzilla-daemon |
| Previous by Thread: | Re: xfsdump stuck in io_schedule - st driver pinning, Zlatko Calusic |
| Next by Thread: | Re: xfsdump stuck in io_schedule, Zlatko Calusic |
| Indexes: | [Date] [Thread] [Top] [All Lists] |