Arch Linux

Dinth

Member

From: London

Registered: 2009-03-02

Posts: 238

ext4 + ktorrent - another bad issue

Ive found another issue with ext4.

Ive been using same configuration on x64 Arch without any problems, but after reinstaling to 32bit, problems with Ktorrent started occuring.
When i download any file with it, it works OK, up to next reboot - after reboot file has blank ("0000..") content.

It isnt known issue with modified files going blank after powerfail.
For example i download HD (4,7GB - so it isnt cached anywhere) movie with Ktorrent. I watch it all, and its perfect. So i dont touch this file, computer works 2-3 days without reboot, and after this time i reboot it. After reboot this movie is empty (size is the same, but only zeros inside).

This occures both with downloaded files, and currently downloading, both with files removed from ktorrent after download, and still seeded. This occures after CLEAN reboots. This occures independently of time which passed after last file access or modification. This occures both when in ktorrent options is checked "allocate all space on the beginning of download" or not. It occures even, when i move downloaded file to another place before reboot. It occures with any file type, and with any file size.

But it doesnt occur with files downloaded or made by any other application.

Strange, somebody has some idea, what causes this problem ?

Last edited by Dinth (2009-05-03 08:45:52)

Bogart

Member

From: Madrid, Spain

Registered: 2005-06-22

Posts: 272

Re: ext4 + ktorrent - another bad issue

Ktorrent works for me using ext4, but this is a 64 bit installation.

If the issue is always reproducible, could you test if mounting the filesystem without delayed allocation solves the problem? It seems that most of the ext4 problems are caused by delayed allocation, so it could be worth trying to know if that's what's causing the problem.

you can add the option "nodelalloc" to your /etc/fstab or as a grub kernel line option with "rootflags=nodelalloc".

#EDIT: Also, when you say it also happens when you move file to another location, I guess it's by using mv command or either cut&paste in the filemanager. If you copy the file, I guess then the original file might get zeroed, but the copied one should be ok, right?

Last edited by Bogart (2009-05-03 09:25:53)

Dinth

Member

From: London

Registered: 2009-03-02

Posts: 238

Re: ext4 + ktorrent - another bad issue

Ive always have nodelalloc in my fstab.

On my current installation, this problem is always reproducible

#EDIT: Also, when you say it also happens when you move file to another location, I guess it's by using mv command or either cut&paste in the filemanager. If you copy the file, I guess then the original file might get zeroed, but the copied one should be ok, right?

Yeah, i havent tested copying file, but i think this would be miracle if copied file would also disappear

PS. A few minutes ago i had strange problem - i couldn't write to any file because of lack of free space (but df -h shows 380GB free). Reboot repaired this problem, but i think it can have something in common with my ktorrent problem - for example loosed data of ktorrent downloaded files could exists somewhere, but not linked to file name?

└─[$]> sudo e2fsck -n /dev/md0
e2fsck 1.41.5 (23-Apr-2009)
Uwaga! /dev/md0 jest podmontowany.
/dev/md0 nie był czysto odmontowany, wymuszono sprawdzenie. [/dev/md0 wasnt cleanly unmounted...]
Przebieg 1: Sprawdzanie i-węzłów, bloków i rozmiarów
Przebieg 2: Sprawdzanie struktury katalogów
Wpis 'sessionstore.js' w /dinth/.mozilla/firefox/7312nujk.default (155015) ma usunięty/nie używany i-węzeł 2546099. Wyczyścić? nie

Przebieg 3: Sprawdzanie łączności katalogów
Przebieg 4: Sprawdzanie liczników odwołań
Niedołączony i-węzeł zerowej długości 2546211. Wyczyścić? nie [unlinked i-... with 0 lenght ...]

Niedołączony i-węzeł 2546211 [unlinked i-....]
Dołączyć do /lost+found? nie

Przebieg 5: Sprawdzanie sumarycznych informacji o grupach
Różnice bitmapy bloków:  -(73349433--73349435) -(75281878--75281879) +(75438793--75438798) -(75450645--75450650)  [Differences with block bitmaps?....]
Poprawić? nie    

Błędna liczba wolnych bloków dla grupy #2238 (12519, naliczono 12516). [ Wrong count of free blocks for group....] 
Poprawić? nie

Błędna liczba wolnych bloków dla grupy #2297 (15522, naliczono 15520). [ Wrong count of free blocks for group....] 
Poprawić? nie

Błędna liczba wolnych bloków (111845775, naliczono 111845770). [ Wrong count of free blocks for group....] 
Poprawić? nie


/dev/md0: ********** UWAGA: System plików nadal ma błędy ********** [filesystem still have errors]

/dev/md0: 524714/54239232 plików (3.2% nieciągłych), 105083929/216929704 bloków

Last edited by Dinth (2009-05-03 09:35:30)

Dinth

Member

From: London

Registered: 2009-03-02

Posts: 238

Re: ext4 + ktorrent - another bad issue

Problem still exists. Strangest thing is that rebooting or turning off power, without properly system shutdown preserves downloaded file contents. They disappear only when im shutdown system normally with drives unmount

göteborg-johan

Member

Registered: 2009-02-27

Posts: 36

Re: ext4 + ktorrent - another bad issue

try deluge or transmission instead?

Dinth

Member

From: London

Registered: 2009-03-02

Posts: 238

Re: ext4 + ktorrent - another bad issue

Deluge and transmission are GNOME dependend, and i have KDE4-only system.

Also, changing torrent client isnt really a solution, especially, when the same Ktorrent, on same ext4 partition, on the same hardware, worked good on earlier installation