From: David Ford <david@blue-labs.org>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Any known ext2 FS problems in 2.4.7?
Date: Fri, 03 Aug 2001 13:40:53 -0400 [thread overview]
Message-ID: <3B6AE225.9070702@blue-labs.org> (raw)
I'm starting to go through a cycle every 2-3 days where I have to bring
one particular machine down to init l1, kill any processes and remount
RO, then run e2fsck on the e2fs partition. Over that period of time,
disk space is eaten without accouting. 'du' shows about 13 gigs used
when I sum up all the directories. Roughly 4.5 gigs is missing. During
e2fsck, there are many many pages of deleted inodes with zero dtime, ref
count fixups, and free inode count fixups. When I say many, I mean that
this pIII 667 scrolls for about four minutes...
There is nothing special about this partition, it doesn't do it while
running 2.4.5-ac15, but I can't use that kernel either because it OOPSes
as I reported. That OOPS was fixed for 2.4.7, but this disk space issue
is rather frustrating. Fortunately all my other systems are reiserfs
and work fine.
/dev/ide/host0/bus0/target0/lun0/part2 on / type ext2
(rw,usrquota=/usr/local/admin/system-info/quota-home)
I haven't mucked with any /proc settings other than "16384"
>/proc/sys/fs/file-max. It's also worthy to note that this machine
also likes to break and spontaneously reboot about once every day. No
klog, no console, no nothing, just bewm. Again 2.4.5 didn't do this.
There is nothing unusual running on this machine, it's very similar to
several other machines that stay running with much higher loads just fine.
-d
next reply other threads:[~2001-08-03 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-03 17:40 David Ford [this message]
2001-08-03 23:01 ` Any known ext2 FS problems in 2.4.7? Andreas Dilger
2001-08-04 3:35 ` David Ford
2001-08-04 7:14 ` David Ford
2001-08-04 23:32 ` Andreas Dilger
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=3B6AE225.9070702@blue-labs.org \
--to=david@blue-labs.org \
--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 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).