| To: | Fong Vang <sudoyang@xxxxxxxxx> |
|---|---|
| Subject: | Re: xfs_check running out of memory |
| From: | Nathan Scott <nscott@xxxxxxxxxx> |
| Date: | Fri, 04 Apr 2008 10:33:38 +1100 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <4f52331f0804031623hc880b03i90f1eed342e97f3c@mail.gmail.com> |
| Organization: | Aconex |
| References: | <4f52331f0804031556n1f00e435g3273c516aacc5d95@mail.gmail.com> <1207263793.21048.150.camel@edge.scott.net.au> <4f52331f0804031611u30e706ddk10aa7a4d011df6a2@mail.gmail.com> <1207264560.21048.153.camel@edge.scott.net.au> <4f52331f0804031623hc880b03i90f1eed342e97f3c@mail.gmail.com> |
| Reply-to: | nscott@xxxxxxxxxx |
| Sender: | xfs-bounce@xxxxxxxxxxx |
On Thu, 2008-04-03 at 16:23 -0700, Fong Vang wrote: > > > > > good to know. Doesn't xfs_check also repair? with xfs_repair -n, No, it doesn't. > this doesn't do any repair. SO the right approach on big volumes > would be to run xfs_repair -n first to detect problem then xfs_repair > to fix? Sure - whatever floats your boat. > thank you for the info. much appreciated. just, curious. where did > you get this info? >From the source. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 2/7] XFS: ASCII case-insensitive support, Nathan Scott |
|---|---|
| Next by Date: | Re: [PATCH 5/7] XFS: Unicode case-insensitive lookup implementation, Christoph Hellwig |
| Previous by Thread: | Re: xfs_check running out of memory, Fong Vang |
| Next by Thread: | Re: [PATCH] do not test return value of xfs_bmap_*_count_leaves, Ruben Porras |
| Indexes: | [Date] [Thread] [Top] [All Lists] |