dillon at apollo.backplane.com
Mon Jun 30 10:06:49 PDT 2008
:I spoke to soon. I have recompiled the kernel after updating my sources
:and the lock *seems* to be gone. OTOH, the low diskspace error is stil
:present. I am doing a prune-everything/reblock sequence now and see if
:that solves this problem. Here is the df output from before the prune:
:> df -h
:Filesystem Size Used Avail Capacity Mounted on
:/dev/ad0s1a 248M 120M 108M 52% /
:/dev/ad0s1d 248M 139M 89M 61% /var
:/dev/ad0s1e 248M 6.0K 228M 0% /tmp
:/dev/ad0s1f 3.9G 3.0G 593M 84% /usr
:home 14G 4.8G 8.9G 35% /home
:procfs 4.0K 4.0K 0B 100% /proc
:(BTW it would be nice to have a progress indicator for the
:Gergo Szakal MD <bastyaelvtars at gmail.com>
:University Of Szeged, HU
:Faculty Of General Medicine
If it says 35% capacity there's plenty of free space on the disk.
Maybe rtorrent thinks that the filesystem has run out of inodes.
HAMMER has no inode limitations and always reports 0 inodes free.
Maybe I need to change that.
<dillon at backplane.com>
More information about the Users