lkml.org 
[lkml]   [2002]   [May]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: ext3 assertion failure and oops, 2.4.18
From
On Tue, 21 May 2002, Antti Salmela wrote:
> I can reliably reproduce an assertion failure and oops in ext3 by simply
> restarting cyrus21, if directories used by cyrus have +j flag set with
> chattr. Filesystem was mounted with default journalling mode data=orderded,
> kernels tested were 2.4.18 and 2.4.19-pre3-ac4. Recent -pre or -ac kernels
> wouldn't compile with my .config.

I can atest to this, too. 2.4.18 stock, if I use the +j flag, the kernel
will oops with the exact same assertion failure. The access pattern is that
of Sleepycat DB3 doing a database snapshot in a subdirectory of the
directory with the +j attribute set.

--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
-
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/

\
 
 \ /
  Last update: 2005-03-22 13:26    [W:0.055 / U:0.332 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site