From: David Fries <dfries@mail.win.org>
To: Stephen Tweedie <sct@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: ext3 dies without inodes
Date: Tue, 29 Oct 2002 13:00:29 -0600 [thread overview]
Message-ID: <20021029190029.GA27062@spacedout.fries.net> (raw)
In-Reply-To: <200209261355.g8QDtRg16986@sisko.scot.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 3238 bytes --]
I'm runnig 2.4.19 and Debian (but I compile my own kernel from the
sources). ext3 is forcing the block device to be read only when I run
out of inodes, and the only way out is reboot (that I could tell).
This is wrose than a good deal of kernel panics I've had. Is
2.4.20prewhatever any better with reguard to this error?
My system is running low on inodes (my fault), and back when I was
using ext2 everything was fine, I would run out, the kernel would give
the message about no more space on disk for everything that needed an
inode until I freed up some. With ext3 I get one message saying no
more space on disk and then everything else gives, readonly file
system.
After I hit the problem accidently, I verified running out of inodes
was the problem on purpose. I would hate to think that I had to
reboot everytime I filled up my harddrive, and it is an equally bad
behavior to reboot when I run out of inodes.
Here is some dmesg output.
EXT3-fs error (device ide0(3,2)) in ext3_new_inode: error 28
Aborting journal on device ide0(3,2).
Remounting filesystem read-only
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
ext3_abort called.
EXT3-fs abort (device ide0(3,2)): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs abort (device ide0(3,2)): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs abort (device ide0(3,2)): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs abort (device ide0(3,2)): ext3_remount: Abort forced by user
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 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 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 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 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 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 start_transaction: Journal has aborted
EXT3-fs error (device ide0(3,2)) in start_transaction: Journal has aborted
ext3_abort called.
EXT3-fs abort (device ide0(3,2)): ext3_remount: Abort forced by user
ext3_abort called.
EXT3-fs abort (device ide0(3,2)): ext3_remount: Abort forced by user
SpacedOut:/mnt/david/tuxscreen/buildroot-tux/build$ df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/hda2 362304 361710 594 100% /
/dev/hdb1 1664640 210988 1453652 13% /mnt/hdb1
--
David Fries <dfries@mail.win.org>
http://fries.net/~david/pgpkey.txt
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-10-29 18:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 13:55 [Patch 0/7] 2.4.20-pre4/ext3: ext3 minor improvements Stephen Tweedie
2002-09-27 20:44 ` Marcelo Tosatti
2002-09-27 22:44 ` Andreas Dilger
2002-09-27 21:01 ` Marcelo Tosatti
2002-10-29 19:00 ` David Fries [this message]
2002-10-29 19:14 ` ext3 dies without inodes Andreas Dilger
2002-10-29 20:11 ` Stephen Tweedie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021029190029.GA27062@spacedout.fries.net \
--to=dfries@mail.win.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).