Transmission downloading the torrent data again after crash

[Sam K. Raju]

Binary package hint: transmission

I was downloading the debian dvd image (4.2 GB) using transmission 1.75 in ubuntu 9.10 (32 bit). The default download location for Transmission is ~/Downloads but I was downloading the data at a different location which is a separate partition of ext4 type. After downloading nearly 50% of the data, I got an error message: "Error:Read only file system". Somehow the filesystem become read only. So I closed Transmission and restarted the laptop and then started Transmission again. But this time Transmission started downloading the data from scratch at the default location i.e. ~/Downloads folder.
I tried to set the location of the torrent data (with 'Local data is already here' option) to previous location where it already downloaded 50% data but when it verified the data, it was only 2.64%. I lost rest of the data.

If any other information is required from my side, please let me know.

[Charles Kerr (charlesk)]

Thank you for taking the time to report this bug and helping to make Ubuntu better

It sounds like the lost data was caused by the filesystem becoming read-only. I don't know what caused that to happen, but it's beyond the scope of Transmission. That might be a question for the ext4 people?

Are you able to reproduce this issue on a stable, writable partition?

[Charles Kerr (charlesk)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Sam K. Raju (samkraju)]

Hi Charles,
Sorry to reply so late.
I don't think that the issue is related to ext4 file system becoming read only as it took almost 10 hours to download 50% data (nearly 2 GB) and during that time I was continuously using my system. If Transmission is writing the data continuously to hard disk, then I should have got a lot more than just 2.64% of the total download. Also, as soon as the file system become read only, I restarted the system.
Another point is why Transmission started to download the file at default location.

[Charles Kerr (charlesk)]

Transmission started to download the file again because it couldn't save the custom location to its resume file when the filesystem was read-only. I don't know what your download speed was during those 10 hours, or how much "corrupt" overhead there would have been listed in the torrent properties dialog.

The questions I have now are:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

[Charles Kerr (charlesk)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Sam K. Raju (samkraju)]

I don't know how exactly it can be reproducible as the filesystem became read only due to some unknown reason.

[Charles Kerr (charlesk)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!