Hello Philippe,

Thanks for your feedback.

I did as you asked... it seems to have gone all right. Cool.

One question in the process after "apport-collect" sort of confused me:
the process remarked (something along the lines of): a bug is considered
a regression if it did NOT exist in a previous release... would you say that
this
bug is a regression?

The "NOT" rather supprised me. I always thought a regression is something
that DID exist in a previous release... anyway: the options  to rhe question
were "yes" and "no".
I answered "no", but actually I was in dire need of a  "dunno", because I
don't know
whether or not this was a regression (whatever a regression may or may not
be)...

Well, I hope this banter helps you all to improve Linux.
Keep up the good work.

Cheers,

Willem


2010/5/17 Philippe Gauthier <email address hidden>

> Willem: Thank you for your bug report. Don't worry too much about the
> Invalid status for now, it's just marked as such because it was
> initially assigned to a project called NULL which had nothing to do with
> the problem. Also, adding comments to this bug report is perfectly OK.
>
> Because your problem looks like a kernel bug, could you please run the
> following command in the terminal that will attach the necessary
> information to this bug report:
>
> apport-collect -p linux 580952
>
> Thanks in advance!
>
> ** Package changed: ubuntu => linux (Ubuntu)
>
> ** Changed in: linux (Ubuntu)
>       Status: New => Incomplete
>
> --
> Log messages: "CIFS VFS: ignoring corrupt resume name"
> https://bugs.launchpad.net/bugs/580952
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in NULL Project: Invalid
> Status in “linux” package in Ubuntu: Incomplete
>
> Bug description:
> Kernel-log contains numerous messages:
>
> May 14 21:55:23 PC10-135 kernel: [ 3061.200126]  CIFS VFS: ignoring corrupt
> resume name
> May 14 21:55:24 PC10-135 kernel: [ 3062.690731]  CIFS VFS: ignoring corrupt
> resume name
> May 14 21:55:27 PC10-135 kernel: [ 3065.119520]  CIFS VFS: ignoring corrupt
> resume name
> May 14 21:55:27 PC10-135 kernel: [ 3065.375574]  CIFS VFS: ignoring corrupt
> resume name
> May 14 21:55:28 PC10-135 kernel: [ 3066.125056]  CIFS VFS: ignoring corrupt
> resume name
> May 14 21:55:30 PC10-135 kernel: [ 3068.819686]  CIFS VFS: ignoring corrupt
> resume name
> May 14 21:55:31 PC10-135 kernel: [ 3069.075233]  CIFS VFS: ignoring corrupt
> resume name
> May 14 21:55:37 PC10-135 kernel: [ 3075.533021]  CIFS VFS: ignoring corrupt
> resume name
> May 14 21:55:39 PC10-135 kernel: [ 3077.600779]  CIFS VFS: ignoring corrupt
> resume name
> May 14 21:55:44 PC10-135 kernel: [ 3082.421668]  CIFS VFS: ignoring corrupt
> resume name
> May 14 21:55:47 PC10-135 kernel: [ 3085.569055]  CIFS VFS: No response for
> cmd 50 mid 17781
> May 14 21:55:47 PC10-135 kernel: [ 3085.577106]  CIFS VFS: No response for
> cmd 50 mid 23875
>
> I *think* these may be the cause of problems I experience when copying
> files from a local harddisk to a network harddisk: copying files with
> nautilus failes quite often. Sometimes gnome commander also failes (and
> sometimes it does not, even though nautilus does). Using CLI cp is at times
> the only way to get files copied.
>
> Runing Ubuntu 10.04, 32 bits, updated on a 64 bit AMD Turion laptop (HP
> Pavilion dv9000).
>
> The network harddisk is a Freecom 500Gb, which is NTFS-formatted.
>
> fstab:
> //its.ip.num.ber/Thuis  /media/Thuis  cifs
>  user_name=,user_group=,iocharset=iso8859-15,nounix,noserverinfo,file_mode=0777,dir_mode=0777
>  0 0
>
> Please advice.
>
> If you need any more information, please tell me what you need me to
> provide.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/null/+bug/580952/+subscribe
>