f13: new mount error after boot (/etc/rc5.d/S25netfs)
Dario Lesca
d.lesca at solinos.it
Tue Jun 8 08:22:44 UTC 2010
Hi, after update to F13 I get this annoying error after boot:
> # LANG=C /etc/rc5.d/S25netfs start
> Mounting other filesystems: mount: according to mtab /altro/distro/Centos/CentOS-5.5-x86_64-bin-DVD-1of2.iso is already mounted on /u/c5x86_64 as loop
> mount: according to mtab /altro/distro/Centos/CentOS-5.5-i386-bin-DVD.iso is already mounted on /u/c5i386 as loop
> mount: according to mtab /altro/distro/Fedora13/Fedora-13-x86_64-DVD.iso is already mounted on /u/f13x86_64 as loop
> mount: according to mtab /altro/distro/Fedora13/Fedora-13-i386-DVD.iso is already mounted on /u/f13i386 as loop
> [FAILED]
This is entry in my fstab:
# grep iso /etc/fstab
> /altro/distro/Centos/CentOS-5.5-x86_64-bin-DVD-1of2.iso /u/c5x86_64 iso9660 ro,loop 0 0
> /altro/distro/Centos/CentOS-5.5-i386-bin-DVD.iso /u/c5i386 iso9660 ro,loop 0 0
> /altro/distro/Fedora13/Fedora-13-x86_64-DVD.iso /u/f13x86_64 iso9660 ro,loop 0 0
> /altro/distro/Fedora13/Fedora-13-i386-DVD.iso /u/f13i386 iso9660 ro,loop 0 0
This is the netfs command witch cause the error:
# mount -a -t nonfs,nfs4,cifs,ncpfs,gfs
>From mount man page:
> -t, --types vfstype
> The argument following the -t is used to indicate the filesystem type. The filesystem types
> which are currently supported include: adfs, affs, autofs, cifs, coda, coherent, cramfs,
> debugfs, devpts, efs, ext, ext2, ext3, ext4, hfs, hfsplus, hpfs, iso9660, jfs, minix, msdos,
> ncpfs, nfs, nfs4, ntfs, proc, qnx4, ramfs, reiserfs, romfs, squashfs, smbfs, sysv, tmpfs,
> ubifs, udf, ufs, umsdos, usbfs, vfat, xenix, xfs, xiafs. Note that coherent, sysv and xenix
> are equivalent and that xenix and coherent will be removed at some point in the future — use
> sysv instead. Since kernel version 2.1.21 the types ext and xiafs do not exist anymore. Ear-
> lier, usbfs was known as usbdevfs. Note, the real list of all supported filesystems depends
> on your kernel.
The type 'nonfs' is not a valid type of FS, and anyway the iso9660 is a
FS an is NOT a network file system.
Because it is attempted to mount?
How to avoid this error?
Is this a bug?
Many thanks to all
--
Dario Lesca <d.lesca at solinos.it>
More information about the users
mailing list