| To: | Brian Foster <bfoster@xxxxxxxxxx> |
|---|---|
| Subject: | Re: "This is a bug." |
| From: | Tapani Tarvainen <tapani@xxxxxxxxxxxxxxxxxx> |
| Date: | Thu, 10 Sep 2015 20:52:20 +0300 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20150910150525.GD27863@xxxxxxxxxxxxxxx> |
| References: | <20150910091834.GC24937@xxxxxxxxxxxxxxxx> <20150910134828.0bdfcc4c@xxxxxxxxxxxxxxxxxxxx> <20150910115548.GD26847@xxxxxxxxxxxxxxxx> <20150910123030.GG26847@xxxxxxxxxxxxxxxx> <20150910123603.GA27863@xxxxxxxxxxxxxxx> <20150910125441.GA28374@xxxxxxxxxxxxxxxx> <20150910130106.GB27863@xxxxxxxxxxxxxxx> <20150910130530.GB28374@xxxxxxxxxxxxxxxx> <20150910145154.GC27863@xxxxxxxxxxxxxxx> <20150910150525.GD27863@xxxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.23 (2014-03-12) |
On Thu, Sep 10, 2015 at 11:05:25AM -0400, Brian Foster (bfoster@xxxxxxxxxx) wrote: > FWIW, the follow up repair did come up clean so it appears (so far) to > have put the fs back together from a metadata standpoint. Indeed, now I can mount it. Not that I expect to find much useful there. Also, it turns out I have another similar case: another filesystem (in the same RAID set) failed also, even though it'd initially mounted without problems. Now it shows the same symptoms, neither mount nor repair works (have't tried repair -L yet). -- Tapani Tarvainen |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: "This is a bug.", Tapani Tarvainen |
|---|---|
| Next by Date: | Re: "This is a bug.", Brian Foster |
| Previous by Thread: | Re: "This is a bug.", Brian Foster |
| Next by Thread: | Re: "This is a bug.", Tapani Tarvainen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |