Opened 13 years ago

Closed 13 years ago

#1875 closed Bug (invalid)

Transmission 1.50 corrupt Disk Structure

Reported by: bilogic Owned by:
Priority: Highest Milestone: None Set
Component: Transmission Version: 1.50
Severity: Critical Keywords:


Longtime use corrupt disk structure. Using transmission too long corrupt disk, starting with slower performance and end with the only resurrection possible of a completely corrupted disk directory by DiskWarrior? 4.1. Apple Disk Utilitie is unable to repair it. I use system 10.4.11 with latest patches. It happens with internal ATA disk as well as external Firewire Disk.

Change History (4)

comment:1 follow-up: Changed 13 years ago by charles

  • Resolution set to invalid
  • Status changed from new to closed

I'm not seeing any of this. In fact 1.50 plays nicer with the filesystem, since it tells the filesystem ahead of time how much space each file will need so that file fragmentation is reduced on the disk.

It's true that P2P's heavy IO load can exacerbate a filesystem's preexisting problems. My guess is that's what's happening here. But if Transmission were really corrupting users' filesystems, I would expect to hear dozens or hundreds of users screaming about it.

Unless there are more complaints about this or someone can show what part of Transmission's code is corrupting a filesystem, I find this really implausible.

comment:2 in reply to: ↑ 1 Changed 13 years ago by bilogic

  • Resolution invalid deleted
  • Status changed from closed to reopened

I am sorry to say but till Transmission 1.40 (built 7084, Mac OSx version) there is no corruption of disk structure. Transmission versions higher then 1.40 show this strange behaviour. I tested with several disks and all disk shows damaging effect on their disk structure. I only have the ability to test it on PPC computers, so I'm not sure this happens on Intel too. Version 1.51 shows the same problem.

comment:3 Changed 13 years ago by livings124

What damaging effects have you seen?

comment:4 Changed 13 years ago by livings124

  • Resolution set to invalid
  • Status changed from reopened to closed

Please reopen with more information. Right now we have nothing to go on except a single user making substantial claims.

Note: See TracTickets for help on using tickets.