12-20-2000
Different UNIX flavor use different file systems. You have to know the filesystem type before you mount. For example, most Linux systems (and your slackware) use the ext2 filesystem. To mount this on another platform you must mount it as an ext2 filesystem.
Quote:
-t vfstype
the file system type. The file system types which
are currently supported are listed in
linux/fs/filesystems.c: adfs, affs, autofs, coda,
coherent, devpts, efs, ext, ext2, hfs, hpfs,
iso9660, minix, msdos, ncpfs, nfs, ntfs, proc,
qnx4, romfs, smbfs, sysv, udf, ufs, umsdos, vfat,
xenix, 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.
The above blurb is from the extensive manpage for mount on linux.
What is the type of filesystem you are trying to mount?
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
I have connected up second hard drive to my Sparcstation5, touched /reconfigure. and now would like to know how to mount the hard drive. I am trying to access /etc/passwd file on second disk to change root passwd but after connecting drive; touching reconfigure. don't know how to go about accessing... (2 Replies)
Discussion started by: FattyLumpkin
2 Replies
2. Shell Programming and Scripting
Hi Engg. ! :mad:
I have a harddisk on which SCO UNIX Open Server was installed. There was some data (in .dbf format) on it. Present condition of HDD is that it is not booting. Now I want to mount this HDD through other HDD on which SCO UNIX Open Server is installed by attaching... (0 Replies)
Discussion started by: Niraj Gopal Sha
0 Replies
3. AIX
hi,
is that possible?
i installed one disk of a old rs/6000 in a linux machine.
the problem seems to be the partition layout.
linux fdisk tells me that aix disklabels are not supported,
so the problem seems to be the partition layout, not the filesystem.
does anybody know a way to access... (1 Reply)
Discussion started by: alex.blackbit
1 Replies
4. Red Hat
Ok. I screwed up. Using dd, I made a bit-for-bit copy of disk /dev/hda, which contains 3 partitions.
dd if=/dev/hda of=olddrive.iso bs=2048k
However, I neglected to make a copy of the partition table. I'd like to mount partition 3, /dev/hda3, which is an xfs filesystem, but obviously I don't... (2 Replies)
Discussion started by: dangral
2 Replies
5. UNIX for Dummies Questions & Answers
Hello all! I just recently inherited a mid-90s gateway full tower system (Original Pentium, SIMM style RAM, etc.). I had always wanted to try an old version of UNIX, and having come across a copy of AT&T System V R4 decided that the time was ripe. There were 30 disks total, and after booting to... (1 Reply)
Discussion started by: Northcott
1 Replies
6. Solaris
Hi once more :p
Yesterday I reinstalled Solaris OS and now I can not mount pcfs HDD
SunOS unknown 5.10 Generic_142901-03 i86pc i386 i86pc
and what has been added in /etc/vfstab is
/dev/dsk/c1t0d0p1:c - /podaci - pcfs - yes rw
But as I said , my disk is... (4 Replies)
Discussion started by: solaris_user
4 Replies
7. Solaris
I am using Solaris 10. I have a raw device attached to my system which is
/dev/md/rdsk/d91
I want to mount this as a disk with file system on a mount point /u05.
Actually this raw device was earlier part of Oracle ASM. Now I have removed this disk from ASM, and want to use it as normal... (3 Replies)
Discussion started by: fahdmirza
3 Replies
8. BSD
I have just installed a second hard disk on a FreeBSD machine v8.0. It is seen as new hardware:
# dmesg | grep ad4
ad4: 953869MB <SAMSUNG HD103UJ 1AA01113> at ata2-master SATA300
ad4: 953869MB <SAMSUNG HD103UJ 1AA01113> at ata2-master SATA300
However it is not listed in fstab where "ad4"... (2 Replies)
Discussion started by: figaro
2 Replies
9. Ubuntu
I wasn't sure where to put this thread but since i use ubuntu for data recovery, I figured this is the best place. So, a friend passed me a 250G Western Digital hard disk the other day and said that his client needs to get her pictures off it. the problem: windows says it wants to reformat the... (13 Replies)
Discussion started by: old noob
13 Replies
10. Linux
Hi All.
I am pretty new when it comes to Linux. My admin left on vacation and has presented 2 new disks to the server but they won't be seen until I can reboot the box this weekend.
Once that happens I need the steps to make it available to my server and mount them as new filesystems. One will... (25 Replies)
Discussion started by: jamie_collins
25 Replies
FSTAB(5) Linux Programmer's Manual FSTAB(5)
NAME
fstab - static information about the filesystems
SYNOPSIS
#include <fstab.h>
DESCRIPTION
The file fstab contains descriptive information about the various file systems. fstab is only read by programs, and not written; it is the
duty of the system administrator to properly create and maintain this file. Each filesystem is described on a separate line; fields on
each line are separated by tabs or spaces. Lines starting with '#' are comments. The order of records in fstab is important because
fsck(8), mount(8), and umount(8) sequentially iterate through fstab doing their thing.
The first field, (fs_spec), describes the block special device or remote filesystem to be mounted.
For ordinary mounts it will hold (a link to) a block special device node (as created by mknod(8)) for the device to be mounted, like
`/dev/cdrom' or `/dev/sdb7'. For NFS mounts one will have <host>:<dir>, e.g., `knuth.aeb.nl:/'. For procfs, use `proc'.
Instead of giving the device explicitly, one may indicate the (ext2 or xfs) filesystem that is to be mounted by its UUID or volume label
(cf. e2label(8) or xfs_admin(8)), writing LABEL=<label> or UUID=<uuid>, e.g., `LABEL=Boot' or `UUID=3e6be9de-8139-11d1-9106-a43f08d823a6'.
This will make the system more robust: adding or removing a SCSI disk changes the disk device name but not the filesystem volume label.
The second field, (fs_file), describes the mount point for the filesystem. For swap partitions, this field should be specified as `none'.
If the name of the mount point contains spaces these can be escaped as ` 40'.
The third field, (fs_vfstype), describes the type of the filesystem. Linux supports lots of filesystem types, such as adfs, affs, autofs,
coda, coherent, cramfs, devpts, efs, ext2, ext3, hfs, hpfs, iso9660, jfs, minix, msdos, ncpfs, nfs, ntfs, proc, qnx4, reiserfs, romfs,
smbfs, sysv, tmpfs, udf, ufs, umsdos, vfat, xenix, xfs, and possibly others. For more details, see mount(8). For the filesystems currently
supported by the running kernel, see /proc/filesystems. An entry swap denotes a file or partition to be used for swapping, cf. swapon(8).
An entry ignore causes the line to be ignored. This is useful to show disk partitions which are currently unused.
The fourth field, (fs_mntops), describes the mount options associated with the filesystem.
It is formatted as a comma separated list of options. It contains at least the type of mount plus any additional options appropriate to
the filesystem type. For documentation on the available options for non-nfs file systems, see mount(8). For documentation on all nfs-spe-
cific options have a look at nfs(5). Common for all types of file system are the options ``noauto'' (do not mount when "mount -a" is
given, e.g., at boot time), ``user'' (allow a user to mount), and ``owner'' (allow device owner to mount), and ``_netdev'' (device requires
network to be available). The ``owner'' and ``_netdev'' options are Linux-specific. For more details, see mount(8).
The fifth field, (fs_freq), is used for these filesystems by the dump(8) command to determine which filesystems need to be dumped. If the
fifth field is not present, a value of zero is returned and dump will assume that the filesystem does not need to be dumped.
The sixth field, (fs_passno), is used by the fsck(8) program to determine the order in which filesystem checks are done at reboot time.
The root filesystem should be specified with a fs_passno of 1, and other filesystems should have a fs_passno of 2. Filesystems within a
drive will be checked sequentially, but filesystems on different drives will be checked at the same time to utilize parallelism available
in the hardware. If the sixth field is not present or zero, a value of zero is returned and fsck will assume that the filesystem does not
need to be checked.
The proper way to read records from fstab is to use the routines getmntent(3).
FILES
/etc/fstab
SEE ALSO
getmntent(3), mount(8), swapon(8), fs(5) nfs(5)
HISTORY
The ancestor of this fstab file format appeared in 4.0BSD.
Linux 2.2 15 June 1999 FSTAB(5)