Bug#502452: Info received (kernel: UDF written file corrupted by zeros)

2009-08-04 Thread jeanmichel . 123
Selon Debian Bug Tracking System : > > Thank you for the additional information you have supplied regarding > this Bug report. In fact, UDF for those 33 Gbytes cartridge seams to work fine with linux debian both 32 bits and 64 bits, both kernel 2.6.18 (for reading) and 2.6.24, both IDE and USB.

Bug#502452: kernel: UDF written file corrupted by zeros

2009-08-03 Thread jeanmichel . 123
Selon Moritz Muehlenhoff : > On Thu, Oct 16, 2008 at 06:04:53PM +0200, Jean-Michel wrote: > > Package: kernel > > Version: 2.6.24-etchnhalf.1-amd64 > > Severity: important > > > > > > Due to existing bugs I had with UDF in kernel 2.6.18, I use 2.6.24 for 8 > > days. > > With 2.6.18 some file were

Bug#377024: nfs_common: nfs client crash nfs server? ; [TCP CHECKSUM INCORRECT]

2006-07-07 Thread jeanmichel . 123
I just find a relation between the bad checksum and lenth: I have seen: bad checksum: 5a1c , when Len is 120 bad checksum: 5f58 , when Len is 1460 bad checksum: 5e1c , when Len is 1144 bad checksum: 5a28 , when Len is 132 This seams to mean that: checksum= 0x59A4 + Len but why on earth do I ha

Bug#377024: nfs_common: nfs client crash nfs server? ; [TCP CHECKSUM INCORRECT]

2006-07-07 Thread jeanmichel . 123
2 additional information: the checksum is bad: * with NFS and SMB over TCP, but not with telnet. * only in TCP blocks wich size (Len under ethereal) is not null this means checksum is good with both telnet blocks empty TCP blocks. Moreover on another computer, without the upgrade, NFS seams to w