| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 5/9] xfs: fix split buffer vector log recovery support |
| From: | Mark Tinguely <tinguely@xxxxxxx> |
| Date: | Wed, 29 May 2013 14:21:52 -0500 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <1369636707-15150-6-git-send-email-david@xxxxxxxxxxxxx> |
| References: | <1369636707-15150-1-git-send-email-david@xxxxxxxxxxxxx> <1369636707-15150-6-git-send-email-david@xxxxxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20120122 Thunderbird/9.0 |
On 05/27/13 01:38, Dave Chinner wrote: From: Dave Chinner<dchinner@xxxxxxxxxx> A long time ago in a galaxy far away.... .. the was a commit made to fix some ilinux specific "fragmented buffer" log recovery problem: http://oss.sgi.com/cgi-bin/gitweb.cgi?p=archive/xfs-import.git;a=commitdiff;h=b29c0bece51da72fb3ff3b61391a391ea54e1603 That problem occurred when a contiguous dirty region of a buffer was split across across two pages of an unmapped buffer. It's been a long time since that has been done in XFS, and the changes to log the entire inode buffers for CRC enabled filesystems has re-introduced that corner case. And, of course, it turns out that the above commit didn't actually fix anything - it just ensured that log recovery is guaranteed to fail when this situation occurs. And now for the gory details. ... Thanks for the great walk through of the problem. Reviewed-by: Mark Tinguely <tinguely@xxxxxxx> |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATH 0/9] xfs: fixes for 3.10-rc4, Ben Myers |
|---|---|
| Next by Date: | Re: [PATH 0/9] xfs: fixes for 3.10-rc4, Eric Sandeen |
| Previous by Thread: | [PATCH 5/9] xfs: fix split buffer vector log recovery support, Dave Chinner |
| Next by Thread: | Re: [PATCH 5/9] xfs: fix split buffer vector log recovery support, Ben Myers |
| Indexes: | [Date] [Thread] [Top] [All Lists] |