Comment 20 for bug 580952

Ah, well, just to add to the confusion: please ignore my message about the
error not being present
in today's log... it is; very much so (the kernel log had disappeared from
the logbook application, therefore I
couldn't find the error; I found the kernel log just now and well, the
errors still occur).

I must say for a Linux newby these logs are rather daunting. :-(

kernel log:
...
May 17 19:39:37 PC10-135 kernel: [ 4126.710541] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:38 PC10-135 kernel: [ 4127.279318] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:38 PC10-135 kernel: [ 4127.534124] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:38 PC10-135 kernel: [ 4127.703429] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:39 PC10-135 kernel: [ 4128.454169] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:39 PC10-135 kernel: [ 4128.706396] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:40 PC10-135 kernel: [ 4129.408803] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:40 PC10-135 kernel: [ 4129.672433] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:41 PC10-135 kernel: [ 4130.190707] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:42 PC10-135 kernel: [ 4131.170509] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:42 PC10-135 kernel: [ 4131.461512] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:42 PC10-135 kernel: [ 4131.737713] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:42 PC10-135 kernel: [ 4132.128221] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:45 PC10-135 kernel: [ 4134.725135] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:47 PC10-135 kernel: [ 4136.965546] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:49 PC10-135 kernel: [ 4138.218574] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:49 PC10-135 kernel: [ 4138.327014] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:50 PC10-135 kernel: [ 4139.224927] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:50 PC10-135 kernel: [ 4139.892600] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:50 PC10-135 kernel: [ 4140.081040] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:52 PC10-135 kernel: [ 4141.694976] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:53 PC10-135 kernel: [ 4142.826539] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:54 PC10-135 kernel: [ 4143.253972] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:54 PC10-135 kernel: [ 4143.819210] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:56 PC10-135 kernel: [ 4145.247386] CIFS VFS: ignoring corrupt
resume name
May 17 19:39:56 PC10-135 kernel: [ 4145.524050] CIFS VFS: No response for
cmd 162 mid 37860
May 17 19:40:03 PC10-135 kernel: [ 4152.706985] CIFS VFS: ignoring corrupt
resume name
May 17 19:40:03 PC10-135 kernel: [ 4153.130415] CIFS VFS: ignoring corrupt
resume name
May 17 19:40:13 PC10-135 kernel: [ 4162.832340] CIFS VFS: ignoring corrupt
resume name
May 17 19:40:15 PC10-135 kernel: [ 4165.070151] CIFS VFS: ignoring corrupt
resume name
May 17 19:40:19 PC10-135 kernel: [ 4168.213563] CIFS VFS: ignoring corrupt
resume name
May 17 19:40:21 PC10-135 kernel: [ 4170.222788] CIFS VFS: ignoring corrupt
resume name
May 17 19:40:23 PC10-135 kernel: [ 4172.684080] CIFS VFS: ignoring corrupt
resume name
May 17 19:40:25 PC10-135 kernel: [ 4174.377436] CIFS VFS: ignoring corrupt
resume name
May 17 19:40:26 PC10-135 kernel: [ 4176.083694] CIFS VFS: ignoring corrupt
resume name
May 17 19:40:27 PC10-135 kernel: [ 4176.412099] CIFS VFS: ignoring corrupt
resume name
May 17 19:40:27 PC10-135 kernel: [ 4176.744576] CIFS VFS: ignoring corrupt
resume name
May 17 19:40:28 PC10-135 kernel: [ 4178.068807] CIFS VFS: ignoring corrupt
resume name
May 17 19:40:45 PC10-135 kernel: [ 4194.391970] CIFS VFS: ignoring corrupt
resume name
May 17 20:38:15 PC10-135 kernel: [ 7645.149004] CE: hpet increasing
min_delta_ns to 22500 nsec
May 17 21:00:33 PC10-135 kernel: [ 8982.656044] CIFS VFS: ignoring corrupt
resume name
May 17 21:00:37 PC10-135 kernel: [ 8986.813050] CIFS VFS: ignoring corrupt
resume name
May 17 21:00:48 PC10-135 kernel: [ 8997.725858] CIFS VFS: ignoring corrupt
resume name
May 17 21:02:06 PC10-135 kernel: [ 9075.457181] CIFS VFS: ignoring corrupt
resume name
etc etc etc

---------- Forwarded message ----------
From: Willem Hobers <email address hidden>
Date: 2010/5/17
Subject: Fwd: [Bug 580952] Re: Log messages: "CIFS VFS: ignoring corrupt
resume name"
To: Bug 580952 <email address hidden>

Hello Philippe,

I just wonder whether the apport output I just sent you is any good:
the errors are not in today's log; they ARE in yesterday's.
The difference is (that I can think of): today I have a wired connection
with the network drive; yesterday a wireless...

I can't test the wireless connection at the moment, I am afraid: wireless
stopped working for I don't know what reason.
And I can't find a solution to that.... yet.

Sorry about that.

---------- Forwarded message ----------
From: Willem Hobers <email address hidden>
Date: 2010/5/17
Subject: Re: [Bug 580952] Re: Log messages: "CIFS VFS: ignoring corrupt
resume name"
To: Bug 580952 <email address hidden>

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
>