I have updated to 2.6.30-1 in testing, and can confirm that this bug is squashed; I don't know if this is due to newer smbfs, samba or kernel however (I did all three).