| To: | Erik Gulliksson <erik@xxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS corruption on 3ware RAID6-volume |
| From: | Emmanuel Florac <eflorac@xxxxxxxxxxxxxx> |
| Date: | Thu, 24 Feb 2011 13:14:11 +0100 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <AANLkTi=ERpJLUUGWO_0xjecTPV3=w1GmXKBk0-uCch1L@xxxxxxxxxxxxxx> |
| Organization: | Intellique |
| References: | <AANLkTinWByYooMnPL7BryPowDexBeiHJdh3aVh+fdm-a@xxxxxxxxxxxxxx> <20110223154651.54f0a8dc@xxxxxxxxxxxxxxxxxxxx> <AANLkTinsfwr5E7KkffwWOweWJLCmaLnLdtYA4g_m--b0@xxxxxxxxxxxxxx> <alpine.DEB.2.02.1102231022470.15181@xxxxxxxxxxxxxxxx> <AANLkTi=ERpJLUUGWO_0xjecTPV3=w1GmXKBk0-uCch1L@xxxxxxxxxxxxxx> |
Le Thu, 24 Feb 2011 11:35:30 +0100
Erik Gulliksson <erik@xxxxxxxxxxxxxx> écrivait:
> If the journal is corrupt, is there anyway to salvage only that part
> so that the log replay will proceed further (ie "xfs_log_repair")?
Your best bet is to try booting a bleeding-edge kernel with the very
latest xfs version. It could possibly go somewhat further (that is, if
the log is not complete garbage).
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@xxxxxxxxxxxxxx>
| +33 1 78 94 84 02
------------------------------------------------------------------------
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS corruption on 3ware RAID6-volume, Justin Piszcz |
|---|---|
| Next by Date: | [PATCH] xfsdump: prune inventory sessions by session id, Bill Kendall |
| Previous by Thread: | Re: XFS corruption on 3ware RAID6-volume, Justin Piszcz |
| Next by Thread: | Re: XFS corruption on 3ware RAID6-volume, Stan Hoeppner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |