Re: ext3 behaviour when no space on disk

["Stephen C. Tweedie" <sct redhat com>]

Hi,

On Mon, Jun 03, 2002 at 10:59:42PM +0200, Duncan Sands wrote:
> While compiling two kernels and untarring a third, my root fs was remounted r/w
> and I got the following in dmesg (kernel 2.4.19-pre9):
> 
> EXT3-fs error (device ide0(3,2)) in ext3_new_inode: error 28

Known problem, fixed in ext3 CVS and in -ac.  If you run out of free
inodes (not free disk blocks), ext3 erroneously considers it to be an
IO error...

> Aborting journal on device ide0(3,2).
> ext3_abort called
> EXT3-fs abort (device ide0(3,2)): ext3_journal_start: Detected aborted journal.
> Remounting filesystem read-only
> Remounting filesystem read-only
> EXT3-fs error (device ide0(3,2)) in start_transaction: Journal has aborted
> EXT3-fs error (device ide0(3,2)) in start_transaction: Journal has aborted
> EXT3-fs error (device ide0(3,2)) in ext3_create: IO failure
> EXT3-fs error (device ide0(3,2)) in start_transaction: Journal has aborted
> EXT3-fs error (device ide0(3,2)) in start_transaction: Journal has aborted

...and if you set the filesystem's on-error behaviour to be
remount-readonly, this is what happens.

--Stephen