linux-kernel - Re: ext3 __log_wait_for

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.SOC.4.64.0810302133040.6084@math.ut.ee>
Date:	Thu, 30 Oct 2008 22:43:25 +0200 (EET)
From:	Meelis Roos <mroos@...ux.ee>
To:	Theodore Tso <tytso@....edu>
cc:	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: ext3 __log_wait_for_space: no transactions

> > __log_wait_for_space: no transactions
> > Aborting journal on device sda3.
> > ext3_abort called.
> > EXT3-fs error (device sda3): ext3_journal_start_sb: Detected aborted journal
> > Remounting filesystem read-only
> 
> How big is your journal?   What does this report?
> 
>     dumpe2fs -h /dev/sda3| grep Journal

dumpe2fs 1.41.3 (12-Oct-2008)
Journal inode:            8
Journal backup:           inode blocks
Journal size:             32M

> The other thing that would be useful would be to replace the call to
> journal_abort() in __log_wait_for_space() in fs/jbd/checkpoint.c with
> a BUG(), so we can get a stack backtrace and see what filesystem
> operation was calling start_this_handle() (which in turn was calling
> __log_wait_for_space) that is triggering this bug.

Will try.

-- 
Meelis Roos (mroos@...ux.ee)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/