Operating Systems > Linux and UNIX
disk full up!!! why???
Nobber:
I don't have a sensible answer, but I can sympathise with you! My other half uses Mandrake 8.2 on a pretty standard 3-year-old desktop machine, and she kept having problems copying stuff to floppies from within Konqueror. The machine would completely lock up just as you described. Turning off supermount for the floppy drive appears to have solved the problem, but of course that means you have to be careful to unmount a floppy disk after using it, which can be a bit irksome.
How's your experience with Mandy 9.0 been?
Calum:
very good, but no major innovations over 8.2. I can't complain, it cost me
DC:
quote:Originally posted by Ex Eleven / b0b:
I guess you could put sync in your /etc/crontab...
--- End quote ---
Sure... but useless. The disk is synchronized once in a while anyway - sync and unmount just forces it at *that* moment. So you don't need to automated - it does it for you! (wow, technology these days...)
Zombie: the system doesn't crash when you don't unmount, the FS gets destroyed if you're unlucky (which isn't that bad on floppies usually).
And Linux can format disks in whatever format you want - even 1.7MB (if the disk supports that - mine does for example).
Centurion, all disks are remounted at shutdown, even disks. And, due to the nature of mounts, there is no way in hell it 'saves' mounts, so it will not see a ghost-mounted floppy. Your endless loop is also bogus - if it can't sync the changes to disk it simply doesn't do that.
Worst case: you mount a floppy, change stuff, eject it (without unmount), insert another floppy, and unmount it - changes to the *first* disk is written to the second disk, trashing the first or both disks. At NO point is memory, the system in general, or other filesystems affected in ANY WAY.
voidmain:
You are correct that the kernel will sync the disks periodically during low activity. Also the "umount" command will cause an automatic sync prior to the actual unmount.
But there is mount cache that keeps track of what file systems are currently mounted. It's /etc/mtab. If you eject a floppy or CD without unmounting it the entry will still be in /etc/mtab and the system will expect there to be a file system under that mount point. If there isn't then you most certainly will get at minimum I/O errors, a sync will certainly not be able to flush the cached writes, etc.
But you are correct that it will not cause a problem with other file systems. Maybe the leftover entry in /etc/mtab is what he was referring to as a "ghost". Usually manually removing that entry from /etc/mtab. For instance when you type "mount" to see what file systems are currently mounted, it gets it's info from /etc/mtab.
[ November 12, 2002: Message edited by: void main ]
DC:
quote:Originally posted by void main:
If you eject a floppy or CD without unmounting it the entry will still be in /etc/mtab and the system will expect there to be a file system under that mount point. If there isn't then you most certainly will get at minimum I/O errors, a sync will certainly not be able to flush the cached writes, etc.
But you are correct that it will not cause a problem with other file systems. Maybe the leftover entry in /etc/mtab is what he was referring to as a "ghost". Usually manually removing that entry from /etc/mtab. For instance when you type "mount" to see what file systems are currently mounted, it gets it's info from /etc/mtab.
[ November 12, 2002: Message edited by: void main ]
--- End quote ---
Well yes - that happens in the worst case scenario I presented. But that effects very little, at most one other disk in the same device. And mtab isn't used during a reboot, that was the ghost he was talking about.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version