Messages in this thread |  | | Date | Fri, 16 Nov 2001 14:52:31 +0000 | From | "Stephen C. Tweedie" <> | Subject | Re: Bug in ext3 |
| |
Hi,
On Thu, Nov 15, 2001 at 04:02:32PM -0500, Ben Collins wrote: > > Seems it does have the field set. I guess the bug is then that if there > is no journal, then it shoudl fail to mount it, so ext2 will take over.
It _did_ fail to mount it, and ext2 _did_ take over: that's why, when ext2 found something else wrong with the filesystem, the errors looked like
EXT2-fs error (device sd(8,20)): ext2_free_blocks: Freeing blocks not in datazone - block = 4294965248, count = 6872
which were marked as ext2 warnings, not ext3 warnings.
Cheers, 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/
|  |