lkml.org 
[lkml]   [2005]   [Feb]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: ext3 bug
On Sun, Feb 27, 2005 at 02:06:30PM -0500, Parag Warudkar wrote:
> On Sunday 27 February 2005 02:04 am, Jean-Marc Valin wrote:
> > Hi,
> >
> > Looks like I ran into an ext3 bug (or at least the log says so). I got a
> > bunch of messages like:
> > ext3_free_blocks_sb: aborting transaction: Journal has aborted in
> > __ext3_journal_get_undo_access<2>EXT3-fs error (device sda2) in
> > ext3_free_blocks_sb: Journal has aborted
> > EXT3-fs error (device sda2): ext3_free_blocks: Freeing blocks in system
> > zones -Block = 228, count = 1
> >
> > It happened while I was doing an "rm -rf" on a directory. The "rm" gave
> > a segfault and now I can't unmount the filesystem: unmount says "device
> > is busy", even though lsof reports nothing. The filesystem is on a USB
> > hard disk. The actual dump is in attachment. I'm running Debian unstable
> > with a custom 2.6.10 kernel on a 1.6 GHz Pentium-M.
> >
> > Jean-Marc
>
> Please try stock kernel. 2.6.11-rc3 onwards should be fine. - I saw a similar
> problem while running 2.6.10 kernel from Fedora Core 3. It doesn't happen
> with stock kernels.

Which is very odd considering the only ext3 patches in the Fedora
kernel are in 2.6.11rc.

Dave

-
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 14:10    [W:0.088 / U:0.224 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site