PROBLEM: MO mounting not working w/ 2.2.3+

Christian Reiniger (warewolf@mayn.de)
Wed, 7 Apr 1999 19:28:34 +0100


Possible bug in partition table code of Kernel 2.2.3 / 2.2.4 / 2.2.5
(I sent this already to Remy Card (as the closest match in MAINTAINERS),
but didn't get any answer yet...)

[1.] when using Kernel 2.2.3/2.2.4/2.2.5 I can't mount my 640M MO disks
(sectorsize 2048, 1 primary partition, ext2 formatted) anymore.

[2.] The disks were formatted with 2.1.128 / 2.1.129 / 2.1.131 / 2.2.0 /
2.2.1. It worked like a charm with those kernels. But when I upgraded from
2.2.1 to 2.2.3 mount gave me a "wrong fs type, bad option, ..." error (of
course I used *exactly* the same options as before). Booting 2.2.0 and
mounting them works, so it's no hardware problem.
I did a "dd if=/dev/sdc1 of=sdc1.img bs=2048 count=2048" both under 2.2.3
and 2.2.0 and the results were differing. Under 2.2.0 the partition start
looks like a normal ext2fs (compared with my hdd partitions), under 2.2.3
it seems as if reading starts at a different position - I didn't compare it
exactly, but the 2.2.3 dump seems to start 14k bytes *after* the 2.2.0 one.
fdisk shows no errors.
I haven't tested it yet with other filesystems and 230M disks (blocksize
512).

[3.] ext2fs, scsi, partition table

[4.] Linux version 2.2.4 (root@chrisbig) (gcc version egcs-2.91.60 19981201 (egcs-1.1.1 release)) #11 Fri Mar 26 13:55:25 CET 1999

[5.] No oopses

[6.] mount -t ext2 /dev/sdc1 /mnt/mo

[7.1.]
-- Versions installed: (if some fields are empty or looks
-- unusual then possibly you have very old versions)
Linux chrisbig 2.2.4 #11 Fri Mar 26 13:55:25 CET 1999 i686 unknown
Kernel modules 2.1.55
Gnu C 2.7.2.1
Binutils 2.8.1
Linux C Library 5.4.33
Dynamic linker ldd (GNU libc) 2.0.7
Linux C++ Library 27..
Procps 1.2.7
Mount 2.8a
Net-tools 1.32-alpha
Kbd 0.93
Sh-utils 1.12
Modules Loaded ne2k-pci 8390

NOTES: glibc 2.0.7 and libc 5.4.33 are running parallel (glibc being used
for new compilations); primary C++ lib is libstdc++ 2.9 (from egcs 1.1.1
dist)

[7.2.]
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 6
model name : Celeron (Mendocino)
stepping : 5
cpu MHz : 450.010361
cache size : 128 KB
fdiv_bug : no
hlt_bug : no
sep_bug : no
f00f_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx osfxsr
bogomips : 448.92

[7.3.]
ne2k-pci 3780 1 (autoclean)
8390 6212 0 (autoclean) [ne2k-pci]

[7.4.]
Attached devices:
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: Model: DFRSS2F Rev: 4B4B
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 02 Lun: 00
Vendor: QUANTUM Model: FIREBALL ST6.4S Rev: 0F0C
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 03 Lun: 00
Vendor: FUJITSU Model: M2513A Rev: 1000
Type: Optical Device ANSI SCSI revision: 02

General information:
Chip NCR53C825, device id 0x3, revision id 0x2
IO port address 0xe400, IRQ number 9
Using memory mapped IO at virtual address 0xc6800000
Synchronous period factor 25, max commands per lun 32

NOTES: The m2513A is the MO drive (/dev/sdc)

[7.5.]
Output of /proc/partitions:
-----
major minor #blocks name

8 0 2202244 sda
8 1 1 sda1
8 5 1536633 sda5
8 6 662886 sda6
8 16 6328858 sdb
8 17 514569 sdb1
8 18 5685400 sdb2
8 19 124000 sdb3
8 32 620704 sdc
8 33 2482112 sdc1
3 0 832291 hda
3 1 614848 hda1
3 2 216720 hda2
-----
Shouldn't sdc be larger than sdc1?

fdisk -v
-----
fdisk v2.1a (>4GB)
-----

Update: fdisk in normal mode lists sdc1 with "620528 Blocks", in expert
mode it says "Size 1241056".

Well, that's all info I can find now...

Christian

--

Drive A: not responding...Formatting C: instead

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/