Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 68858 - Problem with mount loop in kernel 2.6.8 and 2.6.9
Summary: Problem with mount loop in kernel 2.6.8 and 2.6.9
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-25 09:47 UTC by Luke Tanabay
Modified: 2004-10-28 07:47 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luke Tanabay 2004-10-25 09:47:31 UTC
When i try ti mount an dos floopy image i have a problem in kernel versin 2.6.9 and 2.6.9. I have not this problem with 2.6.7

mount -t msdos -o loop /opt/mkcdrec-8.2/tmp/bootflop.img /mnt/cdrom/
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
       or too many mounted file systems
       (could this be the IDE device where you in fact use
       ide-scsi so that sr0 or sda or so is needed?)

I have compiled loop and ms dos in my kernel 

lsmod
Module                  Size  Used by
msdos                   9480  -
fat                    44864  -
loop                   15120  -
tg3                    83436  -

Thanks

Reproducible: Always
Steps to Reproduce:
1.mount -t msdos -o loop /opt/mkcdrec-8.2/tmp/bootflop.img /mnt/cdrom/
2.
3.

Actual Results:  
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
       or too many mounted file systems
       (could this be the IDE device where you in fact use
       ide-scsi so that sr0 or sda or so is needed?)
Comment 1 Jeffrey Forman (RETIRED) gentoo-dev 2004-10-25 09:53:38 UTC
this is not my bug
Comment 2 Nick Dimiduk (RETIRED) gentoo-dev 2004-10-25 12:41:19 UTC
Luke, please attach the output of `emerge --info` so this bug can be properly assigned.
Comment 3 Luke Tanabay 2004-10-26 01:18:31 UTC
HI,

emerge --info

Portage 2.0.51-r2 (default-x86-1.4, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.6.9-gentoo-r1 i686)
=================================================================
System uname: 2.6.9-gentoo-r1 i686 Intel(R) Xeon(TM) CPU 2.40GHz
Gentoo Base System version 1.4.16
Autoconf: sys-devel/autoconf-2.59-r5
Automake: sys-devel/automake-1.8.5-r1
Binutils: sys-devel/binutils-2.14.90.0.8-r1
Headers:  sys-kernel/linux26-headers-2.6.8.1
Libtools: sys-devel/libtool-1.5.2-r5
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -mcpu=i686 -funroll-loops -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -mcpu=i686 -funroll-loops -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache distlocks sandbox"
GENTOO_MIRRORS="http://gentoo.osuosl.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X apache apm arts avi berkdb bindist bitmap-fonts cdr crypt cups encode f77 foomaticdb gd gdbm gif gnome gpm gtk gtk2 imap imlib jpeg kde ldap libg++ libwww mad mikmod mod_php motif mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl php png postfix python qt quicktime readline samba sasl sdl slang spell ssl svga tcpd truetype usb x86 xml2 xmms xprint xv zlib"

Thanks
Comment 4 Daniel Drake (RETIRED) gentoo-dev 2004-10-27 15:59:47 UTC
Do any error messages appear in dmesg after attempting to mount?
Comment 5 Luke Tanabay 2004-10-28 03:45:51 UTC
Hi,

Yes I have a message in dmesg

loop: loaded (max 8 devices)
Unable to load NLS charset cp437
FAT: codepage cp437 not found

In my .config I have :

CONFIG_FAT_DEFAULT_CODEPAGE=437
# CONFIG_NLS_CODEPAGE_437 is not set

Comment 6 Daniel Drake (RETIRED) gentoo-dev 2004-10-28 07:47:34 UTC
Ok, you should either choose a new default or enable that charset in the kernel config. Please reopen if that doesn't help.