~
~
~
~
~
rss:/etc # 358C written
rss:/etc # man mount
Reformatting mount(8), please wait...
MOUNT(8) Linux Programmer's Manual MOUNT(8)
NAME
mount - mount a file system
SYNOPSIS
mount [-lhV]
mount -a [-fFnrsvw] [-t vfstype]
mount [-fnrsvw] [-o options [,...]] device | dir
mount [-fnrsvw] [-t vfstype] [-o options] device dir
DESCRIPTION
All files accessible in a Unix system are arranged in one
big tree, the file hierarchy, rooted at /. These files
can be spread out over several devices. The mount command
serves to attach the file system found on some device to
the big file tree. Conversely, the umount(8) command will
detach it again.
The standard form of the mount command, is
mount -t type device dir
This tells the kernel to attach the file system found on
device (which is of type type) at the directory dir. The
previous contents (if any) and owner and mode of dir
become invisible, and as long as this file system remains
mounted, the pathname dir refers to the root of the file
system on device.
Three forms of invocation do not actually mount anything:
mount -h
prints a help message;
mount -V
prints a version string; and just
mount [-l] [-t type]
lists all mounted file systems (of type type). The option
-l adds the (ext2, ext3 and XFS) labels in this listing.
See below.
Since Linux 2.4.0 it is possible to remount part of the
file hierarchy somewhere else. The call is
mount --bind olddir newdir
The proc file system is not associated with a special
device, and when mounting it, an arbitrary keyword, such
as proc can be used instead of a device specification.
(The customary choice none is less fortunate: the error
message `none busy' from umount can be confusing.)
Most devices are indicated by a file name (of a block spe=AD
cial device), like /dev/sda1, but there are other possi=AD
bilities. For example, in the case of an NFS mount, device
may look like knuth.cwi.nl:/dir. It is possible to indi=AD
cate a block special device using its volume label or UUID
(see the -L and -U options below).
The file /etc/fstab (see fstab(5)), may contain lines
describing what devices are usually mounted where, using
which options. This file is used in three ways:
(i) The command
mount -a [-t type]
(usually given in a bootscript) causes all file systems
mentioned in fstab (of the proper type) to be mounted as
indicated, except for those whose line contains the noauto
keyword. Adding the -F option will make mount fork, so
that the filesystems are mounted simultaneously.
(ii) When mounting a file system mentioned in fstab, it
suffices to give only the device, or only the mount point.
(iii) Normally, only the superuser can mount file systems.
However, when fstab contains the user option on a line,
then anybody can mount the corresponding system.
Thus, given a line
/dev/cdrom /cd iso9660 ro,user,noauto,unhide
any user can mount the iso9660 file system found on his
CDROM using the command
mount /dev/cdrom
or
mount /cd
For more details, see fstab(5). Only the user that
mounted a filesystem can unmount it again. If any user
should be able to unmount, then use users instead of user
in the fstab line. The owner option is similar to the
user option, with the restriction that the user must be
the owner of the special file. This may be useful e.g. for
/dev/fd if a login script makes the console user owner of
this device.
The programs mount and umount maintain a list of currently
mounted file systems in the file /etc/mtab. If no argu=AD
ments are given to mount, this list is printed. When the
proc filesystem is mounted (say at /proc), the files
/etc/mtab and /proc/mounts have very similar contents. The
former has somewhat more information, such as the mount
options used, but is not necessarily up-to-date (cf. the
-n option below). It is possible to replace /etc/mtab by a
symbolic link to /proc/mounts, but some information is
lost that way, and in particular working with the loop
device will be less convenient.
OPTIONS
The full set of options used by an invocation of mount is
determined by first extracting the options for the file
system from the fstab table, then applying any options
specified by the -o argument, and finally applying a -r or
-w option, when present.
Options available for the mount command:
-V Output version.
-h Print a help message.
-v Verbose mode.
-a Mount all filesystems (of the given types) men=AD
tioned in fstab.
-F (Used in conjunction with -a.) Fork off a new
incarnation of mount for each device. This will do
the mounts on different devices or different NFS
servers in parallel. This has the advantage that
it is faster; also NFS timeouts go in parallel. A
disadvantage is that the mounts are done in unde=AD
fined order. Thus, you cannot use this option if
you want to mount both /usr and /usr/spool.
-f Causes everything to be done except for the actual
system call; if it's not obvious, this ``fakes''
mounting the file system. This option is useful in
conjunction with the -v flag to determine what the
mount command is trying to do. It can also be used
to add entries for devices that were mounted ear=AD
lier with the -n option.
-l Add the ext2, ext3 and XFS labels in the mount out=AD
put. Mount must have permission to read the disk
device (e.g. be suid root) for this to work. One
can set such a label for ext2 or ext3 using the
e2label(8) utility, or for XFS using xfs_admin(8).
-n Mount without writing in /etc/mtab. This is neces=AD
sary for example when /etc is on a read-only file
system.
-s Tolerate sloppy mount options rather than failing.
This will ignore mount options not supported by a
filesystem type. Not all filesystems support this
option. This option exists for support of the Linux
autofs-based automounter.
-r Mount the file system read-only. A synonym is -o
ro.
-w Mount the file system read/write. This is the
default. A synonym is -o rw.
-L label
Mount the partition that has the specified label.
-U uuid
Mount the partition that has the specified uuid.
These two options require the file /proc/partitions
(present since Linux 2.1.116) to exist.
-t vfstype
The argument following the -t is used to indicate
the file system type. The file system types which
are currently supported are: adfs, affs, autofs,
coda, coherent, cramfs, devpts, efs, ext, ext2,
ext3, hfs, hpfs, iso9660, minix, msdos, ncpfs, nfs,
ntfs, proc, qnx4, reiserfs, romfs, smbfs, sysv,
udf, ufs, umsdos, vfat, xenix, xfs, xiafs. Note
/dev/hda2 swap swap defaults 0 0
/dev/hda3 / ext2 defaults 1 1
/dev/lv00/publv /pub reiserfs defaults 1 2
/dev/lv00/homelv /home reiserfs defaults 1 2
/dev/hda1 /boot ext2 defaults 1 2
/dev/hda2 swap swap defaults 0 0
/dev/hda3 / ext2 defaults 1 1
/dev/lv00/publv /pub reiserfs defaults 1 2
/dev/lv00/homelv /home reiserfs defaults 1 2
/dev/hda1 /boot ext3 defaults 1 2
~
~
rss:/etc # 358C written
rss:/etc # man mount
Reformatting mount(8), please wait...
MOUNT(8) Linux Programmer's Manual MOUNT(8)
NAME
mount - mount a file system
SYNOPSIS
mount [-lhV]
mount -a [-fFnrsvw] [-t vfstype]
mount [-fnrsvw] [-o options [,...]] device | dir
mount [-fnrsvw] [-t vfstype] [-o options] device dir
DESCRIPTION
All files accessible in a Unix system are arranged in one
big tree, the file hierarchy, rooted at /. These files
can be spread out over several devices. The mount command
serves to attach the file system found on some device to
the big file tree. Conversely, the umount(8) command will
detach it again.
The standard form of the mount command, is
mount -t type device dir
This tells the kernel to attach the file system found on
device (which is of type type) at the directory dir. The
previous contents (if any) and owner and mode of dir
become invisible, and as long as this file system remains
mounted, the pathname dir refers to the root of the file
system on device.
Three forms of invocation do not actually mount anything:
mount -h
prints a help message;
mount -V
prints a version string; and just
mount [-l] [-t type]
lists all mounted file systems (of type type). The option
-l adds the (ext2, ext3 and XFS) labels in this listing.
See below.
Since Linux 2.4.0 it is possible to remount part of the
file hierarchy somewhere else. The call is
mount --bind olddir newdir
The proc file system is not associated with a special
device, and when mounting it, an arbitrary keyword, such
as proc can be used instead of a device specification.
(The customary choice none is less fortunate: the error
message `none busy' from umount can be confusing.)
Most devices are indicated by a file name (of a block spe=AD
cial device), like /dev/sda1, but there are other possi=AD
bilities. For example, in the case of an NFS mount, device
may look like knuth.cwi.nl:/dir. It is possible to indi=AD
cate a block special device using its volume label or UUID
(see the -L and -U options below).
The file /etc/fstab (see fstab(5)), may contain lines
describing what devices are usually mounted where, using
which options. This file is used in three ways:
(i) The command
mount -a [-t type]
(usually given in a bootscript) causes all file systems
mentioned in fstab (of the proper type) to be mounted as
indicated, except for those whose line contains the noauto
keyword. Adding the -F option will make mount fork, so
that the filesystems are mounted simultaneously.
(ii) When mounting a file system mentioned in fstab, it
suffices to give only the device, or only the mount point.
(iii) Normally, only the superuser can mount file systems.
However, when fstab contains the user option on a line,
then anybody can mount the corresponding system.
Thus, given a line
/dev/cdrom /cd iso9660 ro,user,noauto,unhide
any user can mount the iso9660 file system found on his
CDROM using the command
mount /dev/cdrom
or
mount /cd
For more details, see fstab(5). Only the user that
mounted a filesystem can unmount it again. If any user
should be able to unmount, then use users instead of user
in the fstab line. The owner option is similar to the
user option, with the restriction that the user must be
the owner of the special file. This may be useful e.g. for
/dev/fd if a login script makes the console user owner of
this device.
The programs mount and umount maintain a list of currently
mounted file systems in the file /etc/mtab. If no argu=AD
ments are given to mount, this list is printed. When the
proc filesystem is mounted (say at /proc), the files
/etc/mtab and /proc/mounts have very similar contents. The
former has somewhat more information, such as the mount
options used, but is not necessarily up-to-date (cf. the
-n option below). It is possible to replace /etc/mtab by a
symbolic link to /proc/mounts, but some information is
lost that way, and in particular working with the loop
device will be less convenient.
OPTIONS
The full set of options used by an invocation of mount is
determined by first extracting the options for the file
system from the fstab table, then applying any options
specified by the -o argument, and finally applying a -r or
-w option, when present.
Options available for the mount command:
-V Output version.
-h Print a help message.
-v Verbose mode.
-a Mount all filesystems (of the given types) men=AD
tioned in fstab.
-F (Used in conjunction with -a.) Fork off a new
incarnation of mount for each device. This will do
the mounts on different devices or different NFS
servers in parallel. This has the advantage that
it is faster; also NFS timeouts go in parallel. A
disadvantage is that the mounts are done in unde=AD
fined order. Thus, you cannot use this option if
you want to mount both /usr and /usr/spool.
-f Causes everything to be done except for the actual
system call; if it's not obvious, this ``fakes''
mounting the file system. This option is useful in
conjunction with the -v flag to determine what the
mount command is trying to do. It can also be used
to add entries for devices that were mounted ear=AD
lier with the -n option.
-l Add the ext2, ext3 and XFS labels in the mount out=AD
put. Mount must have permission to read the disk
device (e.g. be suid root) for this to work. One
can set such a label for ext2 or ext3 using the
e2label(8) utility, or for XFS using xfs_admin(8).
-n Mount without writing in /etc/mtab. This is neces=AD
sary for example when /etc is on a read-only file
system.
-s Tolerate sloppy mount options rather than failing.
This will ignore mount options not supported by a
filesystem type. Not all filesystems support this
option. This option exists for support of the Linux
autofs-based automounter.
-r Mount the file system read-only. A synonym is -o
ro.
-w Mount the file system read/write. This is the
default. A synonym is -o rw.
-L label
Mount the partition that has the specified label.
-U uuid
Mount the partition that has the specified uuid.
These two options require the file /proc/partitions
(present since Linux 2.1.116) to exist.
-t vfstype
Hi there!
I have a PI 133 machnie with SuSE 7.3.
There are a few file systems. / and /boot were ext2 filesystems os I want=
ed to convert them to ext3.
I've issued the command:
tune2fs -j /dev/hda1
It was successful.
Then I umounted /boot
Modified /etc/fstab according to the change.
And tried to mount the filesystem as ext3. See below:
rss:/etc # mount -t ext3 /dev/hda1 /boot
mount: wrong fs type, bad option, bad superblock on /dev/hda1,
or too many mounted file systems
rss:/etc #
Could you pls help?
Thanks.
Bal.
