Bug#47490: base: mke2fs makes unmountable filesystems; mount doesn't honor -o nocheck

[Jim Dennis <jimd@starshine.org>]

Package: base
Version: 19991015
Severity: important


	I was wrong.  Earlier I claimed that mount was
	unable to handle a filesystem with a non-default
	inode/block ratio ("couldn't mount RDWR").  However,
	my reasoning was wrong.

	In actuality the new mke2fs is making filesystems that
	the latest mount command will not tolerate.  
	
	I've heard that we need to start using the 
	mount -o nocheck (or check=none) option to mount the 
	newly created filesystems with the "sparse superblock" 
	features.  
	
	However, that option is not honored with my copy of 
	mount (2.9x).  mke2fs version is 1.15.  

	e2fsprogs version 1.15-3




-- System Information
Debian Release: potato
Kernel Version: Linux canopus2 2.0.36 #2 Sun Feb 21 15:55:27 EST 1999 i586 unknown