Messages in this thread |  | | Date | Fri, 16 Nov 2001 18:44:52 +0000 | From | "Stephen C. Tweedie" <> | Subject | Re: Bug in ext3 |
| |
Hi,
On Fri, Nov 16, 2001 at 06:38:37PM +0000, Stephen C. Tweedie wrote: > Looks OK. I've done a slightly better version which catches a couple > of extra cases but it's basically the same solution. I've also added > a tiny patch to prevent a failed journal_wipe() from being followed by > a journal_load() attempt, so we don't get the same error twice.
This definitely fixes that error path: I just get one, clean error now, and no corruption of the file that was masquerading as the journal. It doesn't properly release the journal inode, though, so we oops on a later ext2 mount as we think we already have the (ext3) inode in cache. Fix to follow.
Ben, thanks for this --- this level of corrupt journal is something that hasn't been tested in this way before.
--Stephen - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |