Using the attached patch I linked to in bugzilla, it did NOT solve our problem, we patched against an
Ubuntu Hardy 2.6.24-24 kernel. It may or may not have helped the original way of reproducing this error (which I could not ever reproduce on the Hardy kernel), but it does not aid our way of reproducing the problem (with tar)
Anybody have any thoughts? This seems like a pretty serious problem.
Using the attached patch I linked to in bugzilla, it did NOT solve our problem, we patched against an
Ubuntu Hardy 2.6.24-24 kernel. It may or may not have helped the original way of reproducing this error (which I could not ever reproduce on the Hardy kernel), but it does not aid our way of reproducing the problem (with tar)
Anybody have any thoughts? This seems like a pretty serious problem.