| To: | Sean Caron <scaron@xxxxxxxxx> |
|---|---|
| Subject: | Re: What to do when... xfs_repair hangs? |
| From: | Emmanuel Florac <eflorac@xxxxxxxxxxxxxx> |
| Date: | Sun, 1 Jun 2014 22:40:24 +0200 |
| Cc: | Dave Chinner <david@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <CAA43vkUBF3q-F6XYTPTVx43KXg_3_COgaK8wtHxRynshOT9smg@xxxxxxxxxxxxxx> |
| Organization: | Intellique |
| References: | <CAA43vkVzWRTqNQh2VSi5yvFLtstmVOKRJUnYw_ZSkYJGsex8Uw@xxxxxxxxxxxxxx> <20140531000117.GM6677@dastard> <CAA43vkUBF3q-F6XYTPTVx43KXg_3_COgaK8wtHxRynshOT9smg@xxxxxxxxxxxxxx> |
Le Sun, 1 Jun 2014 12:21:55 -0400 vous Ãcriviez: > Since Dave is saying it's OK to try re-running xfs_repair; it'll just > pick up where it left off; let me give it another pass and see if it > manages to complete, or if it segfaults out again. I guess it it > poops out a second time, maybe we'll just want to consider rebuilding > the filesystem and restoring from our copies? You should definitely try a more up-to-date version of xfs_repair first. In case you're not afraid of running a binary from an unkown source, please find a 3.1.11 binary here: http://update.intellique.com/pub/xfsrepair.tar.gz -- ------------------------------------------------------------------------ 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: [RFC 11/32] xfs: convert to struct inode_time, H. Peter Anvin |
|---|---|
| Next by Date: | Re: [PATCH v2 2/7] xfs: add support FALLOC_FL_COLLAPSE_RANGE for fallocate, Dave Chinner |
| Previous by Thread: | Re: What to do when... xfs_repair hangs?, Sean Caron |
| Next by Thread: | Re: What to do when... xfs_repair hangs?, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |