From: Jean-Luc Coulon <jean-luc.coulon@wanadoo.fr>
To: linux-kernel@vger.kernel.org
Subject: 2.4.16-pre1 : e2fsck, File size limit exceeded (core dumped)
Date: Sun, 25 Nov 2001 14:14:08 +0100 [thread overview]
Message-ID: <3C00EEA0.F43E95AA@wanadoo.fr> (raw)
Hi,
I've two partitions. /dev/hda1 where I can boot 2.2.20 or 2.4.16-pre1,
/dev/hda3
with only 2.4.16-pre1.
When I boot 2.2 one the first one and I try a e2fsck on the second one,
I get :
[root@debian-f5ibh] ~ # e2fsck -f /dev/hda3
e2fsck 1.25 (20-Sep-2001)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/hda3: 79176/250368 files (1.5% non-contiguous), 277317/500023
blocks
Now, if I boot 2.4.16-pre1, I have the following :
e2fsck 1.25 (20-Sep-2001)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/hda3: 79176/250368 files (1.5% non-contiguous), 277317/500023
blocks
File size limit exceeded (core dumped)
I tried a e1fsck -f /dev/hda1 from 2.4.16-pre1, I get :
[root@debian-f5ibh] ~ # e2fsck -f /dev/hda1
e2fsck 1.25 (20-Sep-2001)
Pass 1: Checking inodes, blocks, and sizes
Special (device/socket/fifo) inode 1342156 has non-zero size. Fix<y>?
yes
File size limit exceeded (core dumped)
If I do the e2fsck from 2.2.20, all is right and the sero-sized inod is
fixed.
Does anybody is interested by the core ;-)
---------
Regards
jean-Luc
next reply other threads:[~2001-11-25 13:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-25 13:14 Jean-Luc Coulon [this message]
2001-11-25 22:17 ` 2.4.16-pre1 : e2fsck, File size limit exceeded (core dumped) 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=3C00EEA0.F43E95AA@wanadoo.fr \
--to=jean-luc.coulon@wanadoo.fr \
--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