| To: | Drunkard Zhang <gongfan193@xxxxxxxxx> |
|---|---|
| Subject: | Re: bug in xfs: can't recovery metadata log |
| From: | Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx> |
| Date: | Tue, 7 Jun 2011 10:30:59 +0200 |
| Cc: | xfs@xxxxxxxxxxx, Alex Elder <aelder@xxxxxxx>, xfs-masters@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx |
| In-reply-to: | <BANLkTikrmbe9X3Weyb8ikhn1RX_Tn_NuAg@xxxxxxxxxxxxxx> |
| Organization: | it-management http://it-management.at |
| References: | <BANLkTinX_BO94CdQsdmj=atFc-typqr0xg@xxxxxxxxxxxxxx> <201106070943.21004@xxxxxx> <BANLkTikrmbe9X3Weyb8ikhn1RX_Tn_NuAg@xxxxxxxxxxxxxx> |
| User-agent: | KMail/1.13.6 (Linux/2.6.38.6-zmi; KDE/4.6.0; x86_64; ; ) |
On Dienstag, 7. Juni 2011 Drunkard Zhang wrote: > Oops, I already did "xfs_repair -L", successed. It's in production > environment, didn't have too much time to figure out why :-( That was probably the only chance anyway. I'm wondering about the crash. Even if the log is full of shit because of a crash, xfs should not drive to hell but better report the fact and exit. But maybe such strict checking is not worth the effort, as every competent admin does xfs_repair then anyway? -- mit freundlichen Grüssen, Michael Monnerie, Ing. BSc it-management Internet Services: Protéger http://proteger.at [gesprochen: Prot-e-schee] Tel: +43 660 / 415 6531 // Haus zu verkaufen: http://zmi.at/langegg/
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: bug in xfs: can't recovery metadata log, Drunkard Zhang |
|---|---|
| Next by Date: | Re: bug in xfs: can't recovery metadata log, Christoph Hellwig |
| Previous by Thread: | Re: bug in xfs: can't recovery metadata log, Drunkard Zhang |
| Next by Thread: | Re: bug in xfs: can't recovery metadata log, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |