lkml.org 
[lkml]   [2001]   [Nov]   [25]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
DateSun, 25 Nov 2001 14:14:08 +0100
FromJean-Luc Coulon <>
Subject2.4.16-pre1 : e2fsck, File size limit exceeded (core dumped)
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
-
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/
\
 
 \ /
  Last update: 2005-03-22 12:13    [W:0.153 / U:0.000 seconds]
©2003-2008 Jasper Spaans