On Wed, Dec 23, 2009 at 15:26, Goffi <email address hidden> wrote:
> I forgot: fsck is OK, and my corrupted files come from network
>
> --
> in-place corruption of large files *without fsck or reboot* reported with
> linux 2.6.31-14.46 on ext4
> https://bugs.launchpad.net/bugs/453579
> You received this bug notification because you are a direct subscriber
> of the bug.
>
Goffi, I think your problem is related to the network part. I have a bug
report about file corruption using samba:
File corruption after copying files via samba from Karmic to Karmic /bugs.launchpad .net/bugs/ 491288
https:/
Maybe your problem is similar?
On Wed, Dec 23, 2009 at 15:26, Goffi <email address hidden> wrote:
> I forgot: fsck is OK, and my corrupted files come from network /bugs.launchpad .net/bugs/ 453579
>
> --
> in-place corruption of large files *without fsck or reboot* reported with
> linux 2.6.31-14.46 on ext4
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>