On Fri Oct 15 1999 at 08:14, Tony Nugent wrote:
> > I just tried using tomsrtbt on a box with a brand new redhat 6.1
> > installation on it.
> >
> > $ mount -t ext2 /dev/hda1 /mnt
> > EXT@-fs: 0301: couldn't mount RDRW because of unsupported features
The actual error message is:
EXT2-fs: 0301: couldn't mount RDRW because of unsupported optional features
mount: wrong fs type, bad option, bad superblock on /dev/fd0,
or too many mounted file systems
(I missed out on the word "optional").
On Thu Oct 14 1999 at 09:20, Tom Oehser wrote:
> So, again, please run "fdisk -l" from tomsrtbt and send me the output,
> then try "e2fsck" from tomsrtbt, then we'll talk about using other tools
> to figure it out. Until then:
fdisk -l gives back what is expected... it's not a partition problem.
Strangely enough, e2fsck also reports no problems on any of the
partitions.
So, following up with recent revelations that the newer versions of
mke2fs make "sparse" filesystems by default (and without warning), I
did this (from a tomsrtbt):
# e2fsck /dev/sda4
No problems, reporting a clean filesystem.
# tune2fs -s 0 /dev/sda4
No apparent problems. (This turns off the sparse filesystem flag).
# e2fsck /dev/sda4
e2fsck 1.10 [...blah blah...]
/dev/sda4 contains a filesystem with errors, check forced
Pass 1: [blah blah]
...
Fix summary information(y)?y
............ lots of inode numbers scroll across the screen .........
...
# mount /dev/sda4 /mnt
.... lots of lines ....
.... lots of lines ....
EXT2-fs error (device 08:04): ext2_check_inodes_bitmap: Wrong free inodes count in
group XXXX, stored XXXX, counted XXXX
EXT2-fs error (device 08:04): ext2_check_inodes_bitmap: Wrong free inodes count in
super block, stored XXXX, counted XXXX
.... lots of lines ....
....
....
At this point, I'm wondering if those mount errors are coming from
the (2.0.x) kernel.
# ls -l /mnt
drwxr-xr-x 2 root root 12288 Oct 15 15:36 lost+found
Well, at least I can see what's there now. Using tune2fs and e2fsck
like this sort of works, but I'm really glad that I didn't try this on
a partition that had any real data in it :)
This is all most unfortunate, not good at all. The move to using e2fs
sparse filesystem formats by default was inevitable, but it's really
ugly to have had this sprung on all of us so suddenly and
unexpectedly. The developers certainly didn't think this through very
well at all.
Anyway, I hope this lot helps.
Cheers
Tony
-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-
Tony Nugent <[EMAIL PROTECTED]> Systems Administrator
GrowZone OnLine (a project of) GrowZone Development Network
POBox 475 Toowoomba Oueensland Australia 4350 Ph: 07 4632 8344
-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-
