| To: | Steffen Knauf <Steffen.Knauf@xxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: xfs_force_shutdown after Raid crash |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Sat, 31 Jan 2009 05:57:12 -0500 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <498376CF.8020806@xxxxxxxxxxxxxx> |
| References: | <498376CF.8020806@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
On Fri, Jan 30, 2009 at 10:53:19PM +0100, Steffen Knauf wrote: > Hello, > > after a raid crash (Raid Controller problem, 3 Disks of the Disk Group > were kicked out oft the diskgroup), 2 of 3 partitions (XFS FS) were > shutdown immediately. > Perhaps somebody has a idea, what's the best solution (xfs_repair?). This looks like you were running with a write back cache enabled on the controller / disks but without barriers. xfs_repair should be able to repair the filesystem. If you're lucky only the freespace-btrees are corrupted (as in the trace below) as xfs_repair can rebuild them from scratch. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] fs: Add new pre-allocation ioctls to vfs for compatibility with legacy xfs ioctls, Arnd Bergmann |
|---|---|
| Next by Date: | unrepairable file system, Georg Lehner |
| Previous by Thread: | xfs_force_shutdown after Raid crash, Steffen Knauf |
| Next by Thread: | XFS Kernel 2.6.27.7 oopses, Ralf Liebenow |
| Indexes: | [Date] [Thread] [Top] [All Lists] |