From: gaxt <gaxt@rogers.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test5-mm3 VFAT File system problem
Date: Mon, 22 Sep 2003 08:27:15 -0400 [thread overview]
Message-ID: <3F6EEAA3.5000809@rogers.com> (raw)
In-Reply-To: <20030920215152.5e5b318c.rddunlap@osdl.org>
Randy.Dunlap wrote:
> On Sat, 20 Sep 2003 09:21:01 -0400 gaxt <gaxt@rogers.com> wrote:
>
> | Upon moving from -mm2 to -mm3, my vfat filesystems did not automatically
> | bount at bootup as per the fstab and could not be accessed by
> | applications in Gnome ie. my mount point showed no subdirectories or files.
> |
> | I could manually mount (not by mount /mnt/win_c but by the full mount -t
> | vfat /dev/hda1 /mnt/win_c) and I could explore using ls in terminals but
> | programs in Gnome could not open the filesystem.
> |
> | Upon rebooting into -mm2 everything was fine again.
>
> Please post your /etc/fstab file.
>
> Thanks,
> --
> ~Randy
>
# /etc/fstab: static file system information.
# $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/fstab,v 1.10
2002/11/18 19:39:22 azarah Exp $
#
# noatime turns of atimes for increased performance (atimes normally aren't
# needed; notail increases performance of ReiserFS (at the expense of
storage
# efficiency). It's safe to drop the noatime options if you want and to
# switch between notail and tail freely.
# <fs> <mountpoint> <type> <opts>
<dump/pass>
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/hdb2 /boot ext2 noauto,noatime
1 1
/dev/hdb4 / reiserfs noatime,notail
0 0
/dev/hda2 /home reiserfs noatime,notail
0 0
/dev/hdb3 none swap sw
0 0
/dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro
0 0
/dev/cdroms/cdrom1 /mnt/cdrom1 iso9660 noauto,ro
0 0
#/dev/sr0 /mnt/cdrom iso9660 noauto,ro
0 0
#/dev/sr1 /mnt/cdrom1 iso9660 noauto,ro
0 0
#proc /proc proc defaults
0 0
none /proc proc defaults
0 0
/dev/fd0 /mnt/floppy msdos
noauto,users,umask=000 0 0
# Windows Drives
/dev/hda1 /mnt/win_c vfat
noauto,users,umask=000 0 0
/dev/hdb1 /mnt/win_d vfat
auto,users,umask=000 0 0
# Flash Card Readers
/dev/sda /mnt/flash1 vfat
noauto,users,umask=000 0 0
/dev/sdb1 /mnt/flash2 vfat
noauto,users,umask=000 0 0
/dev/sdb /mnt/flash3 vfat
noauto,users,umask=000 0 0
# NFS Drives on MOOMOO
192.168.1.101:/mnt/zip /mnt/moozip nfs
noauto,rw,hard,intr,users 0 0
192.168.1.101:/mnt/win_c /mnt/mooc nfs
noauto,rw,hard,intr,users 0 0
192.168.1.101:/home/moo_share /mnt/moo_share nfs
noauto,rw,hard,intr,users 0 0
# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink). Adding the following
# line to /etc/fstab should take care of this:
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will use
almost no
# memory if not populated with files)
#tmpfs /dev/shm tmpfs defaults
0 0
none /dev/shm tmpfs defaults
0 0
#/dev/sdc2 /mnt/ipod vfat defaults,uid=500,gid=500,user,noauto 0 0
/dev/sdc2 /mnt/ipod vfat defaults,user,noauto 0 0
next prev parent reply other threads:[~2003-09-22 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-20 13:21 2.6.0-test5-mm3 VFAT File system problem gaxt
2003-09-21 4:51 ` Randy.Dunlap
2003-09-22 12:27 ` gaxt [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-20 18:07 Benjamin Weber
2003-09-20 18:56 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F6EEAA3.5000809@rogers.com \
--to=gaxt@rogers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox