From: Maciej Babinski <maciej@imsa.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.5.46 ext3 errors
Date: Wed, 6 Nov 2002 17:55:42 -0600 [thread overview]
Message-ID: <20021106175542.A8364@imsa.edu> (raw)
In-Reply-To: <20021106075406.GC1137@suse.de>; from axboe@suse.de on Wed, Nov 06, 2002 at 08:54:06AM +0100
I got this same error while running "seq 1000000|xargs touch"
in an otherwise empty directory. It got as far as about 20,000
files before the filesystem was remounted ro.
On Wed, Nov 06, 2002 at 08:54:06AM +0100, Jens Axboe wrote:
> Hi,
>
> Doing a kernel compile, the file system suddenly turned read-only.
> Following messages appeared in log:
>
> EXT3-fs error (device ide1(22,1)): ext3_new_inode: Free inodes count corrupted in group 688 Aborting journal on device ide1(22,1).
> ext3_new_inode: aborting transaction: Journal has aborted in __ext3_journal_get_write_access<2>EXT3-fs error (device ide1(22,1)) in ext3_new_inode: Journal has aborted
> EXT3-fs error (device ide1(22,1)) in ext3_create: Journal has aborted ext3_abort called.
> EXT3-fs abort (device ide1(22,1)): ext3_journal_start: Detected aborted journal
> Remounting filesystem read-only
>
> --
> Jens Axboe
>
> -
> 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/
next prev parent reply other threads:[~2002-11-06 23:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 7:54 2.5.46 ext3 errors Jens Axboe
2002-11-06 8:26 ` Jens Axboe
2002-11-06 12:51 ` Stephen Rothwell
2002-11-06 23:55 ` Maciej Babinski [this message]
2002-11-07 0:24 ` Andrew Morton
2002-11-07 3:12 ` Maciej Babinski
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=20021106175542.A8364@imsa.edu \
--to=maciej@imsa.edu \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.