[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 129686] Check for full disk before processing new torrents
From:       Charles Phoenix <phoenixreads () sympatico ! ca>
Date:       2006-06-30 16:45:24
Message-ID: 20060630164524.8997.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=129686         




------- Additional Comments From phoenixreads sympatico ca  2006-06-30 18:45 -------
I assume the allocation is "penciling in" space; it is pending space usage.

What happened:

There were/are file errors reported for the partition in question; rTorrent ran \
without interruption from the initial import; no filesystem checks done. When I \
started rTorrent it did a validation check to pull in partial torrents from KTorrent. \
At this time the partition was at the 98%+ full state. Every thing appeared to work. \
Being paranoid I did a validation check when the imported torrent were finished. The \
corruption was around 80% with a couple of files. I made space on the file system \
(careful to have space left over); restarted the torrents. No corruption.

Note: There were a few complete downloads with no corruption through the above time \
frame. Therefore I conclude it is how the files are allocated ("penciling in") \
causing this problem and somehow two files are writing to the same place without any \
errors occurring. It never gets to the "crapping out" stage for it thinks there is \
still space available.

Note 2: There are errors in the kernel log about swapping at the same time frame so I \
will have to eliminate memory. Sending this now.


[prev in list] [next in list] [prev in thread] [next in thread]