| To: | Fong Vang <sudoyang@xxxxxxxxx> |
|---|---|
| Subject: | Re: xfs_check running out of memory |
| From: | Nathan Scott <nscott@xxxxxxxxxx> |
| Date: | Fri, 04 Apr 2008 10:16:00 +1100 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <4f52331f0804031611u30e706ddk10aa7a4d011df6a2@mail.gmail.com> |
| Organization: | Aconex |
| References: | <4f52331f0804031556n1f00e435g3273c516aacc5d95@mail.gmail.com> <1207263793.21048.150.camel@edge.scott.net.au> <4f52331f0804031611u30e706ddk10aa7a4d011df6a2@mail.gmail.com> |
| Reply-to: | nscott@xxxxxxxxxx |
| Sender: | xfs-bounce@xxxxxxxxxxx |
On Thu, 2008-04-03 at 16:11 -0700, Fong Vang wrote: > > if that's the case then why is it running out of memory? This is a > 6.5TB file systems with millions of files. The system has 24GB of > RAM. It needs to hold everything in memory? xfs_check has 3 per-fs-block arrays that are held all in memory, IIRC. Use xfs_repair -n, which has been revamped to scale a whole lot better than check. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfs_check running out of memory, Fong Vang |
|---|---|
| Next by Date: | Re: xfs_check running out of memory, Nathan Scott |
| Previous by Thread: | Re: xfs_check running out of memory, Fong Vang |
| Next by Thread: | Re: xfs_check running out of memory, Fong Vang |
| Indexes: | [Date] [Thread] [Top] [All Lists] |