On Tuesday 29 May 2007 14:42, Damon Register wrote: > ... > > > # file -s /dev/hd* > > I tried that and got > linux-gmsj:~ # file -s /dev/hda* > /dev/hda: x86 boot sector; partition 1: ID=0x7, active, starthead 1, > startsector 63, 16386237 sectors; partition 2: ID=0x83, starthead 0, > startsector 16386300, 48195 sectors; partition 3: ID=0xf, starthead > 0, startsector 16434495, 23438835 sectors, code offset 0x48 > /dev/hda1: x86 boot sector, code offset 0x52, OEM-ID "NTFS ", > sectors/cluster 8, reserved sectors 0, Media descriptor 0xf8, heads > 255, hidden sectors 63, dos < 4.0 BootSector (0x80) > /dev/hda2: Linux rev 1.0 ext2 filesystem data (mounted or unclean) > /dev/hda3: x86 boot sector; partition 1: ID=0x82, starthead 1, > startsector 63, 1060227 sectors; partition 2: ID=0x5, starthead 0, > startsector 1060290, 10249470 sectors, extended partition table > /dev/hda5: Linux/i386 swap file (new style) 1 (4K pages) size 132527 > pages /dev/hda6: Linux rev 1.0 ext3 filesystem data (needs journal > recovery) (large files) > /dev/hda7: x86 boot sector, code offset 0x58, OEM-ID "MSWIN4.1", > sectors/cluster 8, reserved sectors 34, Media descriptor 0xf8, heads > 255, hidden sectors 27744318, sectors 12129012 (volumes > 32 MB) , > FAT (32 bit), sectors/FAT 11823, reserved3 0x800000, serial number > 0xc67e28b9, label: "ASUS_D " > linux-gmsj:~ # > > /dev/hda7 is the one I am trying to mount. Attempting to mount gives > > linux-gmsj:~ # mount -t vfat /dev/hda7 /windows/data > mount: /dev/hda7 already mounted or /windows/data busy > linux-gmsj:~ #
Well, based the mount and df output you supplied, it does not appear that /dev/hda7 is mounted, though sometimes /etc/mtab can become out-of-sync with the actual list of mounted devices. You can be certain by looking at /proc/mounts (I should have mentioned this the first time--sorry). The only other possibility I can think of (*) is that the mount point (/windows/data, in this case) is in use, meaning, most likely, it is the current working directory for some process. If it's not immediately obvious which that might be (say, the shell you're using to run these commands), then use the "lsof" command to see if there is a process that is holding a reference of some sort to the mount-point directory. As root: # lsof |egrep /windows/data (Naturally, this produces no output on my system, since I have no such directory.) If it turns out one or more processes is using that directory, shut them down or change their current working directory to some other place. (*) On my 10.0 system, you can mount over a directory that is the current working directory of a process, but perhaps the kernel in 10.2 is more fussy? > I don't know what else to try. You can always give up and reboot... > Damon Register Randall Schulz -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
