| To: | AndyLiebman@xxxxxxx |
|---|---|
| Subject: | Re: Scan after crash |
| From: | Eric Sandeen <sandeen@xxxxxxx> |
| Date: | Fri, 04 Jun 2004 15:23:08 -0500 |
| Cc: | Chris Wedgwood <cw@xxxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <19e.2524f91f.2df23037@xxxxxxx> |
| Organization: | Eric Conspiracy Secret Labs |
| References: | <19e.2524f91f.2df23037@xxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
repair is in xfsprogs, badblocks in e2fsprogs. Reading man pages for each will answer your other questions (although if you find something that magically repairs bad blocks, please let me know) :) And to answer the next question: no, xfs does not have a way to mark & route around bad disk blocks. -Eric On Fri, 2004-06-04 at 15:06, AndyLiebman@xxxxxxx wrote: > Oh, one more thing. What kind of output do you get from xfs_repair and > badblocks? Do either of these automatically repair problems, or just report > on what > needs repair? -- 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: XFS for postgres databases?, Steve Lord |
|---|---|
| Next by Date: | xfsdump optical drive strategy, Jeremy Jackson |
| Previous by Thread: | Re: Scan after crash, AndyLiebman |
| Next by Thread: | Re: Scan after crash, AndyLiebman |
| Indexes: | [Date] [Thread] [Top] [All Lists] |