| To: | Chris Murphy <lists@xxxxxxxxxxxxxxxxx>, Robert Tench <robtench@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: Mismatch UUID |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Fri, 14 Nov 2014 17:40:10 -0600 |
| Cc: | "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <6AB68617-0884-486D-8B96-8FD22DBC76D1@xxxxxxxxxxxxxxxxx> |
| References: | <BLU172-W9B4FE524F07D7E6D5592BC48C0@xxxxxxx> <6AB68617-0884-486D-8B96-8FD22DBC76D1@xxxxxxxxxxxxxxxxx> |
On 11/14/14 4:31 PM, Chris Murphy wrote: > It’s very good to ask instead of haphazardly trying things. Trying to > normally mount the file system should be safe; and then use dmesg to > check for kernel messages. The xfs kernel code is responsible for log > replay and making most kinds of repairs, anything it can’t deal with > will be reported as a kernel message. If mount fails, report kernel > xfs related messages, and also the results from xfs_check -n. xfs_repair -n xfs_check is deprecated and has no -n option ;) -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS locking issues in 3.18-rc3+, Dave Chinner |
|---|---|
| Next by Date: | Re: Mismatch UUID, Chris Murphy |
| Previous by Thread: | Re: Mismatch UUID, Chris Murphy |
| Next by Thread: | Re: Mismatch UUID, Chris Murphy |
| Indexes: | [Date] [Thread] [Top] [All Lists] |