| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 08/12] repair: handle filesystems with the log in allocation group 0 |
| From: | Mark Tinguely <tinguely@xxxxxxx> |
| Date: | Fri, 13 Jan 2012 09:18:41 -0600 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20111202174742.515301323@xxxxxxxxxxxxxxxxxxxxxx> |
| References: | <20111202174619.179530033@xxxxxxxxxxxxxxxxxxxxxx> <20111202174742.515301323@xxxxxxxxxxxxxxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.24) Gecko/20111206 Thunderbird/3.1.16 |
On 01/-10/63 13:59, Christoph Hellwig wrote: Sindre Skogen reported that repair chokes on a very small filesystem created by mkfs.xfs from xfsprogs 2.9.4. It turned out that for some reason this filesystem had the log in allocation group 0 and thus repairs validation of the root inode number was off. Fix this by adding the log blocks if the log is allocated in allocation group 0. Reviewed-by: Mark Tinguely <tinguely@xxxxxxx> |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: working on extent locks for i_mutex, Tao Ma |
|---|---|
| Next by Date: | xfs version and kernels, Emmanuel Florac |
| Previous by Thread: | [PATCH] xfs: show uuid when mount fails due to duplicate uuid, Mitsuo Hayasaka |
| Next by Thread: | xfs version and kernels, Emmanuel Florac |
| Indexes: | [Date] [Thread] [Top] [All Lists] |