how do u identify what uses subj , when it says "device is busy" ?

[anton]

Well,

subj ....


trying to unmount this fat32 patrtion, and it always says "device is busy" even though non of my programs use it :(... other fat32 patritions unmount without a problems ...

thx

[7]

Some program (or you) probably has it as it's working directory, thats why it's "busy".

[anton]

7: nope, I checked few times, nothing has anything even related to it ...

[7]

Are you sure you didn't start any programs while at /mnt/<mount point>? Sure you're not there while trying to unmount?

That's all I've got..

[anton]

yes... 99.9% sure : )

[demian]

Try lsof /dev/hdXn with X and n being whatever suits your partitions. You might want to run this as root to make sure you get all the processes listed.

[anton]

don't have such command "lsof" :(

[Lorithar]

*hmmms*

user or program using the /mount/point directory or something below,
user who's shell has as cwd the /mount/point or below.
Samba. .. if Samba knows about it and is supposed to share it...
NFS ... NFS can be piggish once started ... it will try to track just about any file system in its default configuration.

One point... there are likely dozens of processes out there...
try this..

fuser -n file [name/of/mountpoint]
the data is returned in numeric form, pid followed by the /type/ of access (man fuser for details)

[anton]

fuser -n file /dev/hdg


returned nothing ...

[anton]

and also, maybe this will be useful, after doing only few operations with files on that particular partition, linux made it read-only :mad: ... that's why I want to unmount it and than mount it as read/write ...

[X_console]

Try this, telinit 1. That'll take you to single user mode and will shut down any unecessary programs. Then do a telinit 3 and then cd ~ and then try unmounting the partition again.

[anton]

X_console: u wouldn't believe, but still "device is busy" :confused:

[X_console]

Try to force it to unmount (not sure if this'll have any negative effect by the way) by using the -f option to umount. Have you tried rebooting it also? Try the umount -f in single user mode.

[anton]

after rebooting it's still the same,

here's -f:

umount2: Device or resource busy
umount: /dev/hdg1: not mounted
umount: /mnt/win_j: Illegal seek

[X_console]

So after you reboot, you still can't unmount the device? Is the device mounted automatically on bootup? Can I see the contents of your /etc/fstab and the result when you type mount?

[anton]

yes, it's mounted on boot ...

after a very little time it becomes READ-ONLY after boot up ...

also, this all started to happen when something happened to my CPU and linux froze, and I had to reset the computer ... and at that time one of the programs was writing to that disk ... maybe this is the cause of this ...


fstab:

/dev/hdc6 / ext2 defaults 1 1
none /dev/pts devpts mode=0620 0 0
/dev/cdrom /mnt/cdrom vfat ro,noauto,exec,user,nodev 0 0
/dev/cdrom2 /mnt/cdrom2 vfat ro,noauto,exec,user,nodev 0 0
/dev/cdrom3 /mnt/cdrom3 vfat ro,noauto,exec,user,nodev 0 0
/dev/fd0 /mnt/floppy vfat sync,noauto,user,nodev,unhide 0 0
/dev/hdc1 /mnt/win_c vfat user,exec,umask=0 0 0
/dev/hdd1 /mnt/win_e vfat user,exec,umask=0 0 0
/dev/hdd5 /mnt/win_f vfat user,exec,umask=0 0 0
/dev/hdd6 /mnt/win_g vfat rw,user,exec,fat=32,umask=0 0 0
/dev/hdc7 /mnt/win_i vfat rw,user,exec,umask=0,fat=32 0 0
/dev/hdg1 /mnt/win_j vfat rw,user,exec,fat=32,umask=0 0 0
/dev/hdg2 /mnt/win_l vfat rw,user,exec,fat=32,umask=0 0 0
none /proc proc defaults 0 0
/dev/hdc5 swap swap defaults 0 0



mount:

/dev/hdc6 on / type ext2 (rw)
none on /proc type proc (rw)
none on /dev/pts type devpts (rw,mode=0620)
/dev/hdc1 on /mnt/win_c type vfat (rw,nosuid,nodev,umask=0)
/dev/hdd1 on /mnt/win_e type vfat (rw,nosuid,nodev,umask=0)
/dev/hdd5 on /mnt/win_f type vfat (rw,nosuid,nodev,umask=0)
/dev/hdd6 on /mnt/win_g type vfat (rw,nosuid,nodev,fat=32,umask=0)
/dev/hdc7 on /mnt/win_i type vfat (rw,nosuid,nodev,umask=0,fat=32)
/dev/hdg1 on /mnt/win_j type vfat (rw,nosuid,nodev,fat=32,umask=0)
/dev/hdg2 on /mnt/win_l type vfat (rw,nosuid,nodev,fat=32,umask=0)
/proc/bus/usb on /proc/bus/usb type usbdevfs (rw,devmode=0664,devgid=43)

[X_console]

What happens if you change the options for that device from rw,user,exec,fat=32,umask=0 0 to just defaults and then reboot?

[anton]

still the same ...

the most thing that I don't like that it's read-only :( ... I don't really care if I can unmount it ... I just want to figure out, why did it became read-only :(

[X_console]

If you're using LILO, boot directly to single user mode when you get the LILO prompt:

linux 1

Your Windows partitions should still be mounted but any programs that could be writing to it shouldn't be running. You said it will turn to read-only after a while right? See if it happens now. If it doesn't, can you unmount it now?

Another thing to try is comment out the line in fstab that has it mount during bootup. Reboot and see if you can mount the partition manually. Does it become read-only again after a while? Can you unmount it then?

[anton]

X-Console:

gonna try that now ...

but also , right now I tried and it's still not read-only ... though only root can write there ... I tried to copy files there, and it's still doesn't seem to turn into read-only ...

[X_console]

Ok, well if it doesn't turn read-only in single user mode, then we know some program is trying to write to it. Then you can try to figure out what it is with ps aux and shut it down. Good luck, I gotta get ready for work. :D

[anton]

hmm... it didn't go to a single user mode :(

[X_console]

LILO? What about linux single? You need to type this at the LILO boot prompt, not on the command line.

[anton]

yes, I understand that not at command line ;)

I'll try 'single' :)

[anton]

with 'single' it hangs when starts up "window manager" , but if it's starts up window manager, I guess it's not a single anymore ...

[Matches Malone]

A learned friend of mine suggests that this may be in security access settings, a possible "frag", when Linux bombed on ya...

RTMP :)

[anton]

hmmm .... and how would I go about repairing it? :)

[bdg1983]

I would think that Linux has detected a filesystem problem with that particular fat32 partition and switches to readonly as a precautionary measure to ensure that no further damage is done until the problem can be rectified.

Have you tried booting Windows and running a scandisk or whatever 3rd party disk checking software?

[anton]

Logon Name Gone: yeah , I was thinking about that too ... away from my computer for a weekend, gonna try it on sunday night : )

though it takes quite a time ...

[Linuxcool]

Try entering at the lilo boot prompt ' linux single init=/bin/sh '.