Log messages: "CIFS VFS: ignoring corrupt resume name"

[Willem Hobers]

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.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: NVidia [HDA NVidia], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: willem 1496 F.... pulseaudio
CRDA: Error: [Errno 2] Bestand of map bestaat niet
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xf2480000 irq 21'
   Mixer name : 'Conexant CX20561 (Hermosa)'
   Components : 'HDA:14f15051,103c30cf,00100000'
   Controls : 11
   Simple ctrls : 6
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=fd67cd7d-03c3-4d21-ae1b-1fb83d52bb7c
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
Lsusb:
 Bus 002 Device 002: ID 03f0:171d Hewlett-Packard Wireless (Bluetooth + WLAN) Interface [Integrated Module]
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 003: ID 04f2:b023 Chicony Electronics Co., Ltd Gateway USB 2.0 Webcam
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP Pavilion dv9700 Notebook PC
NonfreeKernelModules: nvidia wl
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=5ae68070-cf0f-407e-948f-894c1cd677c2 ro splash vga=795 quiet splash
ProcEnviron:
 LANG=nl_NL.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Regression: No
RelatedPackageVersions: linux-firmware 1.34
Reproducible: Yes
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
Tags: lucid filesystem needs-upstream-testing
Uname: Linux 2.6.32-22-generic i686
UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare
dmi.bios.date: 01/11/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.27
dmi.board.name: 30DA
dmi.board.vendor: Quanta
dmi.board.version: 85.24
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.27:bd01/11/2008:svnHewlett-Packard:pnHPPaviliondv9700NotebookPC:pvrRev1:rvnQuanta:rn30DA:rvr85.24:cvnQuanta:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv9700 Notebook PC
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard

[Willem Hobers (whobers)]

Hello Curtis,

I'm a launchpad newby, and as such I am not able to "parse" your message. Sorry.

Am I to understand that the status of this bug is now "invalid"? And if so, what does that mean? Do I perhaps have to report this bug elsewhere? Have I not supplied the right information?

Please bear with me, I'm trying to understand what's going on here.

Willem

Ps. I would have preferred to PM this message, but I have not found a way to do so. Sorry again.

[ooze (zoe-gauthier)]

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!

[Willem Hobers (whobers)]

apport information

[Willem Hobers (whobers)]

apport information

[Willem Hobers (whobers)]

apport information

[Willem Hobers (whobers)]

apport information

[Willem Hobers (whobers)]

apport information

[Willem Hobers (whobers)]

apport information

[Willem Hobers (whobers)]

apport information

[Willem Hobers (whobers)]

apport information

[Willem Hobers (whobers)]

apport information

[Willem Hobers (whobers)]

apport information

[Willem Hobers (whobers)]

apport information

[Willem Hobers (whobers)]

apport information

[Willem Hobers (whobers)]

apport information

[Willem Hobers (whobers)]

apport information

[Willem Hobers (whobers)]

apport information

[Willem Hobers (whobers)]

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 thoug...

[Willem Hobers (whobers)]

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.5330...

[Willem Hobers (whobers)]

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
resum...

[ooze (zoe-gauthier)]

Thanks Willem! The question about the regression is only there to add a tag to the bug report. See [1] for more information about the regression tags. For now, we will assume it always been broken ;)

Since it looks like we have hit a genuine kernel bug and we have the basic information about the current configuration, I am marking this bug as Confirmed, and also adding the "needs-upstream-testing" tag. This means that it would be nice to verify if the bug is still present when using a stock kernel (that is, not customized by Ubuntu.) The complete details are explained here [2]

To install the mainline kernel, you need to download the linux-image package from http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/ corresponding to the architecture of your system (i386). To install it, run the following command in the directory where the package has been downloaded:

sudo dpkg -i *.deb

There should be a new option line in the boot loader after you restart (hold the Shift key to get to the menu.) If the bug is still there, we will send the bug to the upstream kernel developers. Otherwise we will try to track back what change in the Ubuntu kernel causes this problem. Thanks in advance!

[1] https://wiki.ubuntu.com/QATeam/RegressionTracking
[2] https://wiki.ubuntu.com/KernelTeam/MainlineBuilds

[Willem Hobers (whobers)]

Hello Philippe,

I did as you asked. It seems to have resulted in a new kernel being
installed and running:

dpkg.log:
2010-05-18 08:37:49 startup archives install
2010-05-18 08:37:54 install linux-image-2.6.34-999-generic <geen>
2.6.34-999.201005172238
2010-05-18 08:37:54 status half-installed linux-image-2.6.34-999-generic
2.6.34-999.201005172238
2010-05-18 08:38:28 status unpacked linux-image-2.6.34-999-generic
2.6.34-999.201005172238
2010-05-18 08:38:28 status unpacked linux-image-2.6.34-999-generic
2.6.34-999.201005172238
2010-05-18 08:38:28 configure linux-image-2.6.34-999-generic
2.6.34-999.201005172238 2.6.34-999.201005172238
2010-05-18 08:38:28 status unpacked linux-image-2.6.34-999-generic
2.6.34-999.201005172238
2010-05-18 08:38:28 status half-configured linux-image-2.6.34-999-generic
2.6.34-999.201005172238
2010-05-18 08:38:55 status installed linux-image-2.6.34-999-generic
2.6.34-999.201005172238

uname in Console:

willem@PC10-135:~$ uname -r
2.6.34-999-generic

The laptop will now only work in safe mode.

The trick with pressing shift did not result in me seeing any grub-menu, so
I was not given the possibility to chose the newly installed kernel. Still
it seems that I am running it nonetheless.

The kernel log still shows the messages though they are not as numerous as
before:

May 18 08:53:49 PC10-135 kernel: [ 798.431245] CIFS VFS: ignoring corrupt
resume name
May 18 08:53:53 PC10-135 kernel: [ 801.744130] CIFS VFS: ignoring corrupt
resume name
May 18 08:55:24 PC10-135 kernel: [ 892.502408] CIFS VFS: ignoring corrupt
resume name

Does this help at all?

Willem

Ps. I will now deinstall the 2.6.34-999-kernel.

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

> Thanks Willem! The question about the regression is only there to add a
> tag to the bug report. See [1] for more information about the regression
> tags. For now, we will assume it always been broken ;)
>
> Since it looks like we have hit a genuine kernel bug and we have the
> basic information about the current configuration, I am marking this bug
> as Confirmed, and also adding the "needs-upstream-testing" tag. This
> means that it would be nice to verify if the bug is still present when
> using a stock kernel (that is, not customized by Ubuntu.) The complete
> details are explained here [2]
>
> To install the mainline kernel, you need to download the linux-image
> package from http://kernel.ubuntu.com/~kernel-<http://kernel.ubuntu.com/%7Ekernel->
> ppa/mainline/daily/current/ corresponding to the architecture of your
> system (i386). To install it, run the following command in the directory
> where the package has been downloaded:
>
> sudo dpkg -i *.deb
>
> There should be a new option line in the boot loader after you restart
> (hold the Shift key to get to the menu.) If the bug is still there, we
> will send the bug to the upstream kernel developers. Otherwise we will
> try to track back what change in the Ubuntu kernel causes this problem.
> Thanks in advance!
>
> [1] https://wiki.ubuntu.com/QATeam/RegressionTracking
> [2] https://wiki.ubuntu.com/KernelTeam/MainlineBuilds
>
>
> ** Tags added: needs-upstream-testing
>
> ** Changed in: linux (Ubunt...

[Willem Hobers (whobers)]

Well, bless my baby's bottom: after uninstalling the 2.6.34.999-kernel and rebooting my wifi is working again!

Am now running:

willem@PC10-135:~$ uname -r
2.6.32-22-generic

as before.

[Willem Hobers (whobers)]

Perhaps this may help your analysis.

I've got another PC ( CPU1: Intel(R) Atom(TM) CPU 230 @ 1.60GHz stepping 02) which is running Ubuntu 9.04, with kernel:

2.6.28-18-generic

In the syslog there's also quite a number of the same messages:

CIFS VFS: ignoring corrupt resume name.

Any more information needed?

[penalvch (penalvch)]

WIllem Hobers, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Willem Hobers (whobers)]

Hi Christopher

Thanks for you email.

I am not using 10.04 any more, so I can't test as described below.

Thank you for the good work.

Happy to be using Ubuntu.

op 23-12-13 14:56, Christopher M. Penalver schreef:
> WIllem Hobers, this bug was reported a while ago and there hasn't been
> any activity in it recently. We were wondering if this is still an
> issue? If so, could you please test for this with the latest development
> release of Ubuntu? ISO images are available from
> http://cdimage.ubuntu.com/daily-live/current/ .
>
> If it remains an issue, could you please run the following command in
> the development release from a Terminal
> (Applications->Accessories->Terminal), as it will automatically gather
> and attach updated debug information to this report:
>
> apport-collect -p linux <replace-with-bug-number>
>
> Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
> kernel-fixed-upstream
> kernel-fixed-upstream-VERSION-NUMBER
>
> where VERSION-NUMBER is the version number of the kernel you tested. For example:
> kernel-fixed-upstream-v3.13-rc5
>
> This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
> needs-upstream-testing
>
> If the mainline kernel does not fix this bug, please add the following tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-VERSION-NUMBER
>
> As well, please remove the tag:
> needs-upstream-testing
>
> Once testing of the upstream kernel is complete, please mark this bug's
> Status as Confirmed. Please let us know your results. Thank you for your
> understanding.
>
> ** Tags added: lucid needs-full-computer-model needs-upstream-testing
>
> ** Tags added: jaunty
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>

[penalvch (penalvch)]

Willem Hobers, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/580952/comments/26 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[Arnie (arnie-1)]

Came here through Google. Very likely the cause of these error messages is a faulty SMB implementation in the proprietary OS of the Freecom Network drive. This is not a bug in Ubuntu.

In the original post, Willem mentions: "The network harddisk is a Freecom 500Gb, which is NTFS-formatted." These devices are built around a "RDC Landisk" chipset, usually the 2891 or 2882 which contain 186 or 486 compatible RISC CPUs.

Their firmware is based on the RTOS Micrium uC/OS-II, so it's not Linux. A bunch of RDC programmers wrote an SMB server on top of that and apparently only tested it against Windows XP and later OS X 10.5. Hence these devices are well known to cause trouble when using them with other operating systems. Unfortunately the complete source code is not available and made for a proprietary compiler (Paradigm 6, devtools.com).

Hope this information helps anyone trying to figure out the same error. The RDC chipsets were not only used in the Freecom Network Drive but also in Conceptronic CHD3NET, Fantec LD-H35NSU2, Packard Bell Netstore 3500, Sitecom MD-250, etc. I expect all these devices to cause these problems.

Best regards,

Arnoud Onnink