[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [linux-lvm] Unmounting file system hangs up...



Here is what is in /etc/fstab.
#
# /etc/fstab
# Created by anaconda on Mon Sep  7 20:25:11 2009
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or vol_id(8) for more info
#
UUID=878c124d-0271-4dd7-95d1-e6c95439220c /                       ext3    defaults        1 1
UUID=3511be5f-909d-44c5-a806-2e1d00d21dc4 /home                   ext3    defaults        1 2
UUID=8ee04c46-a36e-484d-824c-661c07f4c126 /boot                   ext3    defaults        1 2
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
UUID=917a7154-8448-4c94-a230-7bd4be54e571 swap                    swap    defaults        0 0

CentOS-5 is on a hard drive of the same computer. /etc/fstab does not explicitly mount CentOS-5, but Fedora-10 somehow mounts all hard drives including NTFS drives. I must have done something to do this, but I forgot what I did. Do you have any idea what I did and how I remedy this situation?



On Sun, Oct 4, 2009 at 12:11 PM, André Gillibert <rcvxdg gmail com> wrote:
Thinking Outside the Well <rod rook gmail com> wrote:

> I agree you are right on your suggestion that Fedora is trying to umount a
> network file system. I think it actually is trying to umount a CentOS file
> system installed in another hard drive. The reason why I think that way is
> that whenever I log on to CentOS, it complains that something is wrong with
> the file system and checks it
>
Not properly unmounting a network (NFS, CIFS, etc.) mount point shouldn't break the target file system in any way, and shouldn't cause fsck to report errors.
Is CentOS hard drive on another computer?
In that case, what network file system protocol is used, if any?
If it's local hard drive, then, it's probably mounted as local file system (ext3 or other), and, not properly unmounting it, may cause fsck to complain.

The contents of /etc/fstab and /etc/mtab or /proc/mounts may help you.

fstab contains a static list of fs mounted at boot time.
mtab and /proc/mounts contain the list of currently mounted file systems, including ones that might have been automatically mounted by your desktop environment when HAL notified it.

--
André Gillibert



_______________________________________________
linux-lvm mailing list
linux-lvm redhat com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]