Обсуждение: Can't write lock file
Here are the results of df /tmp/ Filesystem 1k-blocks Used Available Use% Mounted on /dev/hdc6 253840 243504 0 100% / df -i /tmp/ Filesystem Inodes IUsed IFree IUse% Mounted on /dev/hdc6 65792 24415 41377 38% / The above information seems to me contradictory in that df /tmp reports that 100% of my 1k-blocks are used, while df -i /tmp/ reports that only 38% of inodes are used. I don't know what to make of this. Nor am I sure if this is why I can't use postgres. Nor why this problem has occured in the first place. Totally in the dark, Mark
On Mon, Oct 21, 2002 at 02:33:03PM -0400, MT wrote: > Here are the results of > > df /tmp/ > Filesystem 1k-blocks Used Available Use% Mounted on > /dev/hdc6 253840 243504 0 100% / > > df -i /tmp/ > Filesystem Inodes IUsed IFree IUse% Mounted on > /dev/hdc6 65792 24415 41377 38% / Obviously there are still inodes left, but no space. It's a common situation. You'll have to delete some files... make sure there's no process with open files in the filesystem, because that prevents the space these files are using from being actually freed. -- Alvaro Herrera (<alvherre[a]atentus.com>) "Para tener mas hay que desear menos"
On Mon, 21 Oct 2002, MT wrote: > Here are the results of > > df /tmp/ > Filesystem 1k-blocks Used Available Use% Mounted on > /dev/hdc6 253840 243504 0 100% / > > df -i /tmp/ > Filesystem Inodes IUsed IFree IUse% Mounted on > /dev/hdc6 65792 24415 41377 38% / > > The above information seems to me contradictory in that df /tmp reports > that 100% of my 1k-blocks are used, while df -i /tmp/ reports that only > 38% of inodes are used. I don't know what to make of this. Nor am I sure > if this is why I can't use postgres. Nor why this problem has occured in > the first place. Well you must have some large files if there is a disproportionate use of disk space verses inodes. You should try and track down where and what they are. Are your log directories on the same filesystem as /? What about other entries in /tmp? Try using du -sk /* as a starting point. -- Nigel J. Andrews
On Mon, 21 Oct 2002, MT wrote: > Here are the results of > > df /tmp/ > Filesystem 1k-blocks Used Available Use% Mounted on > /dev/hdc6 253840 243504 0 100% / > > df -i /tmp/ > Filesystem Inodes IUsed IFree IUse% Mounted on > /dev/hdc6 65792 24415 41377 38% / > > The above information seems to me contradictory in that df /tmp reports > that 100% of my 1k-blocks are used, while df -i /tmp/ reports that only > 38% of inodes are used. I don't know what to make of this. Nor am I sure > if this is why I can't use postgres. Nor why this problem has occured in > the first place. Having inodes available won't help if your drive is full, since you have to have blocks free to write. note that the drive isn't really completely full, but the space left (1,000 blocks or so) are only available for root to write to. That's so that root can still log in and fix the problem, etc... You either need to free up space on your /tmp drive or make a bigger partition for it.