[Bug 1160551] [NEW] compiz using almost all CPU on system, even when nothing going on
Public bug reported: On Ubuntu 12.10, updates applied - top shows compiz using between 300 and 500% CPU (it is an 8 core AMD processor), and the system runs slower than it should. 8GB RAM. It is a fairly recent nvidia card (default nouveau drivers). lspci shows NVIDIA Corporation Device 0fc6 (rev a1) $ lsb_release -rd Description:Ubuntu 12.10 Release:12.10 $ apt-cache policy compiz compiz: Installed: 1:0.9.8.4-0ubuntu2 I don't care much about the desktop, I work on the kernel - but I really would like to have compiz not use most of the CPU on the system. How do I fix or turn off compiz? ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: symap_custom_3.5.0_17_generic_x86_64 symev_custom_3.5.0_17_generic_x86_64 .tmp.unity.support.test.1: ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Tue Mar 26 14:29:11 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: openclient-savap-config, 1.0.14, 3.5.0-17-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:0fc6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:8a96] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Gigabyte Technology Co., Ltd. GA-970A-DS3 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.5.0-17-generic root=UUID=6485c2b1-0d0b-49a4-a855-c357c9942608 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/30/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-970A-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd03/30/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.8.4-0ubuntu2 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 performance quantal running-unity ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1160551 Title: compiz using almost all CPU on system, even when nothing going on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1160551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 406466] Re: 2.6.31 - Can't see files in CIFS-mounted directories
I can imagine why mounting with serverino could made a difference. If the server has broken support for returning serverinode numbers (or at least for the specific findfirst level that returns search information + server inode numbers) then things like resume keys could get messed up which would make it hard to parse the response, or could cause us to not find the next entry in the search response if the directory has more than a certain number of files (perhaps 50). To help the tracing it may be helpful to uncomment the tracing call (in fs/cifs/readdir.c) /* cFYI(1, (filldir on %s,pqst-name)); */ or to add a debug entry before the call to filldir (in the same file fs/cifs/readdir.c) Obviously if we decide that the findfirst or findnext response from the server is messed up, then the next question is how to detect this in the client - and if we can detect it in the client, then we turn off serverinode numbers on the fly (after logging something about the broken server) - but first would be good to get wireshark to decode this level or decode some of it by hand. -- 2.6.31 - Can't see files in CIFS-mounted directories https://bugs.launchpad.net/bugs/406466 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 406466] Re: 2.6.31 - Can't see files in CIFS-mounted directories
I can imagine why mounting with serverino could made a difference. If the server has broken support for returning serverinode numbers (or at least for the specific findfirst level that returns search information + server inode numbers) then things like resume keys could get messed up which would make it hard to parse the response, or could cause us to not find the next entry in the search response if the directory has more than a certain number of files (perhaps 50). To help the tracing it may be helpful to uncomment the tracing call (in fs/cifs/readdir.c) /* cFYI(1, (filldir on %s,pqst-name)); */ or to add a debug entry before the call to filldir (in the same file fs/cifs/readdir.c) Obviously if we decide that the findfirst or findnext response from the server is messed up, then the next question is how to detect this in the client - and if we can detect it in the client, then we turn off serverinode numbers on the fly (after logging something about the broken server) - but first would be good to get wireshark to decode this level or decode some of it by hand. -- 2.6.31 - Can't see files in CIFS-mounted directories https://bugs.launchpad.net/bugs/406466 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 293548] Re: can't save file in samba share
*** This bug is a duplicate of bug 286828 *** https://bugs.launchpad.net/bugs/286828 If nodfs mount option works around the problem then this is a duplicate issue, as suggested, and long since addressed. Remember, there is a clear SERVER bug which has been fixed for quite a while, but only clients which support BOTH unix extensions and dfs would see it (which is why the two suggested workarounds - nodfs or nounix on mount could work around it). Remember that the user who had permission issues could have a different problem (e.g. uids that don't match on clients and server - perhaps they should override the default uid and gid and/or turn off perm checking on the client (noperm) mount option. -- can't save file in samba share https://bugs.launchpad.net/bugs/293548 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu (via bug 286828). -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 293548] Re: can't save file in samba share
*** This bug is a duplicate of bug 286828 *** https://bugs.launchpad.net/bugs/286828 If nodfs mount option works around the problem then this is a duplicate issue, as suggested, and long since addressed. Remember, there is a clear SERVER bug which has been fixed for quite a while, but only clients which support BOTH unix extensions and dfs would see it (which is why the two suggested workarounds - nodfs or nounix on mount could work around it). Remember that the user who had permission issues could have a different problem (e.g. uids that don't match on clients and server - perhaps they should override the default uid and gid and/or turn off perm checking on the client (noperm) mount option. -- can't save file in samba share https://bugs.launchpad.net/bugs/293548 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286828] Re: Access to samba 3.0.24-3.0.25 shares using CIFS is broken on 8.10
Simplifying: 1) older smbfs/smbmount had a bug: they didn't support DFS (which Windows clients do, and Linux cifs client does) which is a critical feature of the protocol in multiple server environments 2) Windows does not support Unix Extensions Samba server introduced a bug (long since fixed) which affects clients which support BOTH Asking the kernel cifs client to always disable DFS support (ie without a mount option) to work around a bug in one server version would make things even worse because that would hurt accessing all of the servers that have working DFS support. -- Access to samba 3.0.24-3.0.25 shares using CIFS is broken on 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 286828] Re: Access to samba 3.0.24-3.0.25 shares using CIFS is broken on 8.10
Simplifying: 1) older smbfs/smbmount had a bug: they didn't support DFS (which Windows clients do, and Linux cifs client does) which is a critical feature of the protocol in multiple server environments 2) Windows does not support Unix Extensions Samba server introduced a bug (long since fixed) which affects clients which support BOTH Asking the kernel cifs client to always disable DFS support (ie without a mount option) to work around a bug in one server version would make things even worse because that would hurt accessing all of the servers that have working DFS support. -- Access to samba 3.0.24-3.0.25 shares using CIFS is broken on 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211631] Re: CIFS/SMBFS shares not unmounted before network is shut down
OK ... doing a little more investigation it gets interesting to see what crazy things gnome does (you can also try clearing the dmesg log and then doing echo 7 /proc/fs/cifs/cifsFYI before you logoff/umount and see what cifs operations are in dmesg) What I see is that the slow operations are repeated calls (presumably by gnome) to querypathinfo (stat) on .Trash-1000 ... see below fs/cifs/inode.c: Getting info on //localhost/stevef/.Trash-1000 fs/cifs/cifssmb.c: In QPathInfo (Unix) the path //localhost/stevef/.Trash-1000 cifs has no way of knowing that this is useless and that we should ignore gnome's request In addition, running with umount.cifs (/sbin/umount.cifs is not needed in most cases unless you are doing user mounts/umount) you get a call to statfs (umount.cifs has to verify that this is a cifs mount and AFAIK there is no cheap way to do this in Ubuntu - and so we are stuck calling statfs to check the fs type field to make sure that we are in fact unmount a cifs file system - but statfs also unfortunately returns other information that requires sending a request over the network ... it would be very helpful if there were a way to query ... just ... the file system's type and not the other dynamic information that requires going to the server). If you move umount.cifs out of sbin that should help, but the big problem seems to be the desktop querying for things it doesn't need to be doing during umount -- CIFS/SMBFS shares not unmounted before network is shut down https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 211631] Re: CIFS/SMBFS shares not unmounted before network is shut down
running without umount.cifs (which is not needed unless you are doing user mounts), the unmount finishes quickly, and with no visible errors (the tree disconnection request times out fairly fast, and the rest of umount proceeds fast after that) -- CIFS/SMBFS shares not unmounted before network is shut down https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 211631] Re: CIFS/SMBFS shares not unmounted before network is shut down
The easiest way to test this is to always do umount -i mnt-point rather than umount mnt-point unless you are doing an umount as a regular user of a user mount (-i prevents the unneeded helper program from being called) -- CIFS/SMBFS shares not unmounted before network is shut down https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 211631] Re: CIFS/SMBFS shares not unmounted before network is shut down
OK ... doing a little more investigation it gets interesting to see what crazy things gnome does (you can also try clearing the dmesg log and then doing echo 7 /proc/fs/cifs/cifsFYI before you logoff/umount and see what cifs operations are in dmesg) What I see is that the slow operations are repeated calls (presumably by gnome) to querypathinfo (stat) on .Trash-1000 ... see below fs/cifs/inode.c: Getting info on //localhost/stevef/.Trash-1000 fs/cifs/cifssmb.c: In QPathInfo (Unix) the path //localhost/stevef/.Trash-1000 cifs has no way of knowing that this is useless and that we should ignore gnome's request In addition, running with umount.cifs (/sbin/umount.cifs is not needed in most cases unless you are doing user mounts/umount) you get a call to statfs (umount.cifs has to verify that this is a cifs mount and AFAIK there is no cheap way to do this in Ubuntu - and so we are stuck calling statfs to check the fs type field to make sure that we are in fact unmount a cifs file system - but statfs also unfortunately returns other information that requires sending a request over the network ... it would be very helpful if there were a way to query ... just ... the file system's type and not the other dynamic information that requires going to the server). If you move umount.cifs out of sbin that should help, but the big problem seems to be the desktop querying for things it doesn't need to be doing during umount -- CIFS/SMBFS shares not unmounted before network is shut down https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211631] Re: CIFS/SMBFS shares not unmounted before network is shut down
running without umount.cifs (which is not needed unless you are doing user mounts), the unmount finishes quickly, and with no visible errors (the tree disconnection request times out fairly fast, and the rest of umount proceeds fast after that) -- CIFS/SMBFS shares not unmounted before network is shut down https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211631] Re: CIFS/SMBFS shares not unmounted before network is shut down
The easiest way to test this is to always do umount -i mnt-point rather than umount mnt-point unless you are doing an umount as a regular user of a user mount (-i prevents the unneeded helper program from being called) -- CIFS/SMBFS shares not unmounted before network is shut down https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211631] Re: CIFS/SMBFS shares not unmounted before network is shut down
A couple clarifications: 1) We really want the network file systems to be unmounted (or at least synced) before the network goes away. You do not want to risk losing file system data which has been cached by the Linux memory management layer. 2) If there is cached write data, we do want the file system to try as hard as reasonably possible (perhaps forever in the case of mounting with the hard mount option rather than the default soft mount) before giving up - the network which is down for a few seconds, may recover in most cases (where exactly we are in shutdown of the system may be hard to detect in this path in the kernel) 3) CIFS already does do the obvious - it does not attempt to send network requests in umount (SMB tree disconnect followed by SMB ulogoff) if the session is already dead (the server implicitly closes tids and smb uids when the socket crashes). Write requests just prior to the umount getting to the kernel would cause attempts at reconnect, but simply from the kernel cifs driver perspective umounting should not cause network traffic if the session is already dead e.g. see this code excerpt from CIFSSMBTDis /* * No need to return error on this operation if tid invalidated and * closed on server already e.g. due to tcp session crashing. Also, * the tcon is no longer on the list, so no need to take lock before * checking this. */ if (tcon-need_reconnect) return 0; and similarly in CIFSSMBLogoff: if (ses-need_reconnect) goto session_already_dead; /* no need to send SMBlogoff if uid already closed due to reconnect */ -- CIFS/SMBFS shares not unmounted before network is shut down https://bugs.launchpad.net/bugs/211631 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 286828] Re: Access to samba 3.0.24-3.0.25 shares using CIFS is broken on 8.10
I agree that a distinct problem should be opened for the automount issue. The two problems are distinct and the problem with automount is likely due to changes in network driver initialization or packaging. On Wed, Dec 24, 2008 at 2:43 AM, Thierry Carrez thierry.car...@ubuntu.com wrote: Jim/Tom: As Steve said, this is very likely to be a separate issue (my guess would be the network-manager changes in 8.10 that expose wireless connections very late in the boot/login process), could one of you please file a separate bug ? I don't want to delay publication of this fix because of disconnected problems. As far as this bug is concerned, if booting 2.6.27-11 and (manually) mounting the CIFS share with nodfs allows the mount to succeed, then it's ok. So far vide, mipper and Tom confirmed that fix... -- Access to samba 3.0.24-3.0.25 shares using CIFS is broken on 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a direct subscriber of the bug. -- Thanks, Steve -- Access to samba 3.0.24-3.0.25 shares using CIFS is broken on 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 286828] Re: Access to samba 3.0.24-3.0.25 shares using CIFS is broken on 8.10
On Tue, Dec 23, 2008 at 5:54 AM, Tom ttw...@gmail.com wrote: After adding nodfs to my kernel at boot time did NOT change anything. My MS Windows shares that use to mount automatically under 8.04 still do not mount automatically after adding that option. Yet, after boot, I can issue sudo mount /shares/windows_f and the share is mounted without incident or error messages. I performed an upgrade from 8.04, not a new, clean install. Relevant line from syslog: Dec 23 06:27:43 tom-nb kernel: [0.00] Kernel command line: root=UUID=9810c849-9967-45c4-9a82-415e2ddcb81c ro quiet splash nodfs Output from uname -a: Linux tom-nb 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux Relevant lines from fstab: //192.168.4.10/NetworkShare /shares/windows_f cifs auto,rw,credentials=/root/.creds,uid=ttwaro,gid=ttwaro 0 0 //192.168.4.10/NetworkShare2 /shares/windows_o cifs auto,rw,credentials=/root/.creds,uid=ttwaro,gid=ttwaro 0 0 I doubt that that problem was related to the problem with write which was originally reported. Since cifs has very few dependencies on userspace (the upcall for Kerberos ie sec=krb5, and the upcall for dfs hostname resolution), it is not obvious why automount should differ from mount after boot, unless there is a problem getting to /sbin/mount.cifs -- Thanks, Steve -- Access to samba 3.0.24-3.0.25 shares using CIFS is broken on 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 286828] Re: Access to samba 3.0.24-3.0.25 shares using CIFS is broken on 8.10
On Tue, Dec 23, 2008 at 5:54 AM, Tom ttw...@gmail.com wrote: After adding nodfs to my kernel at boot time did NOT change anything. My MS Windows shares that use to mount automatically under 8.04 still do not mount automatically after adding that option. Yet, after boot, I can issue sudo mount /shares/windows_f and the share is mounted without incident or error messages. I performed an upgrade from 8.04, not a new, clean install. Relevant line from syslog: Dec 23 06:27:43 tom-nb kernel: [0.00] Kernel command line: root=UUID=9810c849-9967-45c4-9a82-415e2ddcb81c ro quiet splash nodfs Output from uname -a: Linux tom-nb 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux Relevant lines from fstab: //192.168.4.10/NetworkShare /shares/windows_f cifs auto,rw,credentials=/root/.creds,uid=ttwaro,gid=ttwaro 0 0 //192.168.4.10/NetworkShare2 /shares/windows_o cifs auto,rw,credentials=/root/.creds,uid=ttwaro,gid=ttwaro 0 0 I doubt that that problem was related to the problem with write which was originally reported. Since cifs has very few dependencies on userspace (the upcall for Kerberos ie sec=krb5, and the upcall for dfs hostname resolution), it is not obvious why automount should differ from mount after boot, unless there is a problem getting to /sbin/mount.cifs -- Thanks, Steve -- Access to samba 3.0.24-3.0.25 shares using CIFS is broken on 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 286828] Re: Access to samba 3.0.24-3.0.25 shares using CIFS is broken on 8.10
Just to summarize again: 1) A few versions of Samba server had a bug parsing DFS paths (fixed in Samba server 3.0.26). You can see which version of server you have mounted to by doing cat /proc/fs/cifs/Debug Data on the client). When the Linux CIFS client added support for DFS last year, those few (relatively old) versions of Samba servers (when configured for DFS) exhibited problems with certain path based calls (setting the file size was one) which can break some common applications. 2) Although disabling the cifs unix extensions (mount option nounix) may help in some cases, the best solution is to upgrade the Samba server to any of the more recent versions of the server. If that is not possible, disabling DFS support (see comment 50) in the server is another possibility (on future kernels, 2.6.28 includes this e.g., you will be able to specify nodfs as a mount option on the client to workaround the problems on these two versions of Samba). On Sat, Nov 29, 2008 at 11:30 AM, truxntrax [EMAIL PROTECTED] wrote: Waiting for a fix here too. Confusingly this issue has ony affected one of my pc's after the ibex upgrade. My laptop still see my nas box and popcorn hour but my desktop I have to manually nount drives after boot (sudo mount -a). Happy to help with any investigations if more information is required. -- Thanks, Steve -- Access to samba 3.0.24-3.0.25 shares using CIFS is broken on 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 286828] Re: Access to samba 3.0.24-3.0.25 shares using CIFS is broken on 8.10
Just to summarize again: 1) A few versions of Samba server had a bug parsing DFS paths (fixed in Samba server 3.0.26). You can see which version of server you have mounted to by doing cat /proc/fs/cifs/Debug Data on the client). When the Linux CIFS client added support for DFS last year, those few (relatively old) versions of Samba servers (when configured for DFS) exhibited problems with certain path based calls (setting the file size was one) which can break some common applications. 2) Although disabling the cifs unix extensions (mount option nounix) may help in some cases, the best solution is to upgrade the Samba server to any of the more recent versions of the server. If that is not possible, disabling DFS support (see comment 50) in the server is another possibility (on future kernels, 2.6.28 includes this e.g., you will be able to specify nodfs as a mount option on the client to workaround the problems on these two versions of Samba). On Sat, Nov 29, 2008 at 11:30 AM, truxntrax [EMAIL PROTECTED] wrote: Waiting for a fix here too. Confusingly this issue has ony affected one of my pc's after the ibex upgrade. My laptop still see my nas box and popcorn hour but my desktop I have to manually nount drives after boot (sudo mount -a). Happy to help with any investigations if more information is required. -- Thanks, Steve -- Access to samba 3.0.24-3.0.25 shares using CIFS is broken on 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286828] Re: Access to samba3.0.26 shares using CIFS is broken on 8.10
Since the Samba servers 3.0.24 through 3.0.25a which exhibited this problem may have had problems with parsing a DFS path (in this case for a path based call to set the file server), could someone check if the write problems go away if the mount is done with the nodfs mount option (would require fairly recent cifs client, perhaps even 2.6.27 kernel, to use that mount option) - that changes how the client sends paths from \\server\share\dir\file to \dir\file and may work around the problem if the server bug was caused by the processing of dfs paths -- Access to samba3.0.26 shares using CIFS is broken on 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 286828] Re: Access to samba3.0.26 shares using CIFS is broken on 8.10
The nodfs option was added by this patch: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=2c1b861539c15491593625920058e06452cd3747 which went in right after 2.6.27 came out so will be in 2.6.28. The patch is small and could be added to this 2.6.27 distro kernel easily enough. Apparently most distros did not ship the two problematic Samba versions on their server, or have done a mandatory upgrade, which is why we don't see this problem (server parsing of dfs paths) more often. On Wed, Nov 19, 2008 at 3:39 PM, Martien Verbruggen [EMAIL PROTECTED] wrote: # uname -r 2.6.27-7-generic # mount -t cifs -o rw,user=xxx,password=xxx,nodfs //dns-323/Shared /mnt/dummy # tail -1 /var/log/messages Nov 20 08:34:24 mgjv kernel: [ 1670.862969] CIFS: Unknown mount option nodfs Looks like that needs an ever newer kernel. I am having this problem with a DNS-323 NAS, so I don't easily have the option of upgrading the Samba version on that, and would like to see some resolution to this bug. happy to provide more information. BTW, the nounix option changes behaviour, but does not fix it. If wanted, I can provide test and wiretap dumps later today. -- Access to samba3.0.26 shares using CIFS is broken on 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a direct subscriber of the bug. -- Thanks, Steve -- Access to samba3.0.26 shares using CIFS is broken on 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 286828] Re: Access to samba3.0.26 shares using CIFS is broken on 8.10
Since the Samba servers 3.0.24 through 3.0.25a which exhibited this problem may have had problems with parsing a DFS path (in this case for a path based call to set the file server), could someone check if the write problems go away if the mount is done with the nodfs mount option (would require fairly recent cifs client, perhaps even 2.6.27 kernel, to use that mount option) - that changes how the client sends paths from \\server\share\dir\file to \dir\file and may work around the problem if the server bug was caused by the processing of dfs paths -- Access to samba3.0.26 shares using CIFS is broken on 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 286828] Re: Access to samba3.0.26 shares using CIFS is broken on 8.10
The nodfs option was added by this patch: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=2c1b861539c15491593625920058e06452cd3747 which went in right after 2.6.27 came out so will be in 2.6.28. The patch is small and could be added to this 2.6.27 distro kernel easily enough. Apparently most distros did not ship the two problematic Samba versions on their server, or have done a mandatory upgrade, which is why we don't see this problem (server parsing of dfs paths) more often. On Wed, Nov 19, 2008 at 3:39 PM, Martien Verbruggen [EMAIL PROTECTED] wrote: # uname -r 2.6.27-7-generic # mount -t cifs -o rw,user=xxx,password=xxx,nodfs //dns-323/Shared /mnt/dummy # tail -1 /var/log/messages Nov 20 08:34:24 mgjv kernel: [ 1670.862969] CIFS: Unknown mount option nodfs Looks like that needs an ever newer kernel. I am having this problem with a DNS-323 NAS, so I don't easily have the option of upgrading the Samba version on that, and would like to see some resolution to this bug. happy to provide more information. BTW, the nounix option changes behaviour, but does not fix it. If wanted, I can provide test and wiretap dumps later today. -- Access to samba3.0.26 shares using CIFS is broken on 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a direct subscriber of the bug. -- Thanks, Steve -- Access to samba3.0.26 shares using CIFS is broken on 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286828] Re: CIFS share broken after upgrade from 8.04 - 8.10
I looked at the wireshark trace in post #25 (by Alexey) and I see what looks like a server bug in this old version of Samba (Samba 3.0.25). Note that Samba 3.2.4 is current, and Samba 3.0.32 contains various highly recommended fixes (Released in August Samba 3.0.32 is the latest bug fix release for Samba 3.0 and is the version recommended for all production Samba servers running this release series) In frame 8 the client opens a file (imagehost.pl) which succeeds In frame 10 the client requests information on the same file which succeeds In frame 14 the client tries to set the file size on the same file and the server (incorrectly) returns STATUS_OBJECT_PATH_NOT_FOUND ... obviously that can't be correct because the server just gave the client info on the same file in the previous request and there is no delete in between. -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 286828] Re: CIFS share broken after upgrade from 8.04 - 8.10
On Tue, Nov 18, 2008 at 9:55 AM, rylleman [EMAIL PROTECTED] wrote: I can also confirm this bug. One thing that might be of interest is the error message I get from KeypassX; File could not be saved. The file could not be resized. Can it be that there is nothing wrong with save itself but that the sizes of the files cannot be changed? The trace of the write failure in post 25 shows the server incorrectly rejecting an attempt to set the file size, so it is plausible that writes would work (also since writes are handle based not path based) but that the setting of file size explicitly would fail. Is this bug persistent through later versions of Samba as well or would an upgrade fix it? If the version of the server in your case is also Samba 3.0.25a (see /proc/fs/cifs/DebugData on the client to display session information including the server version) then I think it plausible that a server upgrade would fix it. -- Thanks, Steve -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 286828] Re: CIFS share broken after upgrade from 8.04 - 8.10
I looked at the wireshark trace in post #25 (by Alexey) and I see what looks like a server bug in this old version of Samba (Samba 3.0.25). Note that Samba 3.2.4 is current, and Samba 3.0.32 contains various highly recommended fixes (Released in August Samba 3.0.32 is the latest bug fix release for Samba 3.0 and is the version recommended for all production Samba servers running this release series) In frame 8 the client opens a file (imagehost.pl) which succeeds In frame 10 the client requests information on the same file which succeeds In frame 14 the client tries to set the file size on the same file and the server (incorrectly) returns STATUS_OBJECT_PATH_NOT_FOUND ... obviously that can't be correct because the server just gave the client info on the same file in the previous request and there is no delete in between. -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 286828] Re: CIFS share broken after upgrade from 8.04 - 8.10
On Tue, Nov 18, 2008 at 9:55 AM, rylleman [EMAIL PROTECTED] wrote: I can also confirm this bug. One thing that might be of interest is the error message I get from KeypassX; File could not be saved. The file could not be resized. Can it be that there is nothing wrong with save itself but that the sizes of the files cannot be changed? The trace of the write failure in post 25 shows the server incorrectly rejecting an attempt to set the file size, so it is plausible that writes would work (also since writes are handle based not path based) but that the setting of file size explicitly would fail. Is this bug persistent through later versions of Samba as well or would an upgrade fix it? If the version of the server in your case is also Samba 3.0.25a (see /proc/fs/cifs/DebugData on the client to display session information including the server version) then I think it plausible that a server upgrade would fix it. -- Thanks, Steve -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 286828] Re: CIFS share broken after upgrade from 8.04 - 8.10
Sounds like a long shot but here are the fixes http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=0752f1522a9120f731232919f7ad904e9e22b8ce and http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=a364bc0b37f14ffd66c1f982af42990a9d77fa43 commit a364bc0b37f14ffd66c1f982af42990a9d77fa43 Author: Jeff Layton [EMAIL PROTECTED] Date: Tue Oct 21 14:42:13 2008 + [CIFS] fix saving of resume key before CIFSFindNext We recently fixed the cifs readdir code so that it saves the resume key before calling CIFSFindNext. Unfortunately, this assumes that we have just done a CIFSFindFirst (or FindNext) and have resume info to save. This isn't necessarily the case. Fix the code to save resume info if we had to reinitiate the search, and after a FindNext. This fixes connectathon basic test6 against NetApp filers. Signed-off-by: Jeff Layton [EMAIL PROTECTED] CC: Stable [EMAIL PROTECTED] Signed-off-by: Steve French [EMAIL PROTECTED] commit 0752f1522a9120f731232919f7ad904e9e22b8ce Author: Steve French [EMAIL PROTECTED] Date: Tue Oct 7 20:03:33 2008 + [CIFS] make sure we have the right resume info before calling CIFSFindNext When we do a seekdir() or equivalent, we usually end up doing a FindFirst call and then call FindNext until we get to the offset that we want. The problem is that when we call FindNext, the code usually doesn't have the proper info (mostly, the filename of the entry from the last search) to resume the search. Add a last_entry field to the cifs_search_info that points to the last entry in the search. We calculate this pointer by using the LastNameOffset field from the search parms that are returned. We then use that info to do a cifs_save_resume_key before we call CIFSFindNext. This patch allows CIFS to reliably pass the telldir connectathon test. Signed-off-by: Jeff Layton [EMAIL PROTECTED] CC: Stable [EMAIL PROTECTED] Signed-off-by: Steve French [EMAIL PROTECTED] On Wed, Nov 5, 2008 at 1:53 PM, Eric Krieger [EMAIL PROTECTED] wrote: capturing the any information post lockup will not be possible. the entire system freezes and requires a power cycle to recover. The issue is defiantly a client issue. I've tested rolling my kernel back to 2.6.24-19 from 2.6.27-7 and everything works fine. Could you point me to the pair of fixes to cifs in 2.6.27? Thanks! -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a direct subscriber of the bug. -- Thanks, Steve -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 286828] Re: CIFS share broken after upgrade from 8.04 - 8.10
Sounds like a long shot but here are the fixes http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=0752f1522a9120f731232919f7ad904e9e22b8ce and http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=a364bc0b37f14ffd66c1f982af42990a9d77fa43 commit a364bc0b37f14ffd66c1f982af42990a9d77fa43 Author: Jeff Layton [EMAIL PROTECTED] Date: Tue Oct 21 14:42:13 2008 + [CIFS] fix saving of resume key before CIFSFindNext We recently fixed the cifs readdir code so that it saves the resume key before calling CIFSFindNext. Unfortunately, this assumes that we have just done a CIFSFindFirst (or FindNext) and have resume info to save. This isn't necessarily the case. Fix the code to save resume info if we had to reinitiate the search, and after a FindNext. This fixes connectathon basic test6 against NetApp filers. Signed-off-by: Jeff Layton [EMAIL PROTECTED] CC: Stable [EMAIL PROTECTED] Signed-off-by: Steve French [EMAIL PROTECTED] commit 0752f1522a9120f731232919f7ad904e9e22b8ce Author: Steve French [EMAIL PROTECTED] Date: Tue Oct 7 20:03:33 2008 + [CIFS] make sure we have the right resume info before calling CIFSFindNext When we do a seekdir() or equivalent, we usually end up doing a FindFirst call and then call FindNext until we get to the offset that we want. The problem is that when we call FindNext, the code usually doesn't have the proper info (mostly, the filename of the entry from the last search) to resume the search. Add a last_entry field to the cifs_search_info that points to the last entry in the search. We calculate this pointer by using the LastNameOffset field from the search parms that are returned. We then use that info to do a cifs_save_resume_key before we call CIFSFindNext. This patch allows CIFS to reliably pass the telldir connectathon test. Signed-off-by: Jeff Layton [EMAIL PROTECTED] CC: Stable [EMAIL PROTECTED] Signed-off-by: Steve French [EMAIL PROTECTED] On Wed, Nov 5, 2008 at 1:53 PM, Eric Krieger [EMAIL PROTECTED] wrote: capturing the any information post lockup will not be possible. the entire system freezes and requires a power cycle to recover. The issue is defiantly a client issue. I've tested rolling my kernel back to 2.6.24-19 from 2.6.27-7 and everything works fine. Could you point me to the pair of fixes to cifs in 2.6.27? Thanks! -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a direct subscriber of the bug. -- Thanks, Steve -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286828] Re: CIFS share broken after upgrade from 8.04 - 8.10
To make progress, we need data ... Could someone please provide a wireshark (or tcpdump) trace of the problem. See http://wiki.samba.org/index.php/Capture_Packets for step-by-step description (it is really not hard ... but without this, we have no data) -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 286828] Re: CIFS share broken after upgrade from 8.04 - 8.10
Probably not related - if you can get stack traces that would help (e.g. echo t /proc/sysrq-trigger) at the time of a process hang that would help to see what it is blocked on. On the other question there are a pair of fixes to cifs in 2.6.27 which addressed a problem with directory searches to some servers. On the original problem, I would like to see network traces (wireshark, tcpdump or netmon) to isolate whether this is a server or client bug On Mon, Nov 3, 2008 at 10:55 AM, Eric Krieger [EMAIL PROTECTED] wrote: Not sure if this is related but I'm also having issues with CIFS. I can mount the storage just fine but sometimes if I try accessing the mounted CIFS share my system locks. Also when I am able to access the CIFS share in question I'm only able to see directories up to the letter S anything after is not listed even though it is there. -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a direct subscriber of the bug. -- Thanks, Steve -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 286828] Re: CIFS share broken after upgrade from 8.04 - 8.10
The file save problem you mention is different than the automount problem described earlier. In looking at the network trace of the automount problem, I see that no traffic is sent on the network in the failing case, which may simply be a configuration problem, or problem locating mount.cifs during this early phase of boot. On Sun, Nov 2, 2008 at 10:42 PM, Aron Schatz [EMAIL PROTECTED] wrote: I can also confirm this bug on Kubuntu 8.10. Using the same mount options in 8.04 worked fine. In 8.10, files can be created, renamed, or deleted, but are NOT able to edit. IE: Using Kate, I can open a file but can't save it. It is able to create its backup files. Eclipse fails to save files as well on the mount. Hopefully it gets fixed soon. The LinuxExtensions suggestion did not help the problem as I never used them on this mount. I can confirm that older clients (8.04, 7.10) can read/write/save on the same mount with the same options just fine. Seems like a regression in Samba. -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a direct subscriber of the bug. -- Thanks, Steve -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 286828] Re: CIFS share broken after upgrade from 8.04 - 8.10
Probably not related - if you can get stack traces that would help (e.g. echo t /proc/sysrq-trigger) at the time of a process hang that would help to see what it is blocked on. On the other question there are a pair of fixes to cifs in 2.6.27 which addressed a problem with directory searches to some servers. On the original problem, I would like to see network traces (wireshark, tcpdump or netmon) to isolate whether this is a server or client bug On Mon, Nov 3, 2008 at 10:55 AM, Eric Krieger [EMAIL PROTECTED] wrote: Not sure if this is related but I'm also having issues with CIFS. I can mount the storage just fine but sometimes if I try accessing the mounted CIFS share my system locks. Also when I am able to access the CIFS share in question I'm only able to see directories up to the letter S anything after is not listed even though it is there. -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a direct subscriber of the bug. -- Thanks, Steve -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286828] Re: CIFS share broken after upgrade from 8.04 - 8.10
To make progress, we need data ... Could someone please provide a wireshark (or tcpdump) trace of the problem. See http://wiki.samba.org/index.php/Capture_Packets for step-by-step description (it is really not hard ... but without this, we have no data) -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 286828] Re: CIFS share broken after upgrade from 8.04 - 8.10
The file save problem you mention is different than the automount problem described earlier. In looking at the network trace of the automount problem, I see that no traffic is sent on the network in the failing case, which may simply be a configuration problem, or problem locating mount.cifs during this early phase of boot. On Sun, Nov 2, 2008 at 10:42 PM, Aron Schatz [EMAIL PROTECTED] wrote: I can also confirm this bug on Kubuntu 8.10. Using the same mount options in 8.04 worked fine. In 8.10, files can be created, renamed, or deleted, but are NOT able to edit. IE: Using Kate, I can open a file but can't save it. It is able to create its backup files. Eclipse fails to save files as well on the mount. Hopefully it gets fixed soon. The LinuxExtensions suggestion did not help the problem as I never used them on this mount. I can confirm that older clients (8.04, 7.10) can read/write/save on the same mount with the same options just fine. Seems like a regression in Samba. -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a direct subscriber of the bug. -- Thanks, Steve -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 286828] Re: CIFS share broken after upgrade from 8.04 - 8.10
Unlike smbfs, Linux cifs client requires very little user space intereraction unless you mount with Kerberos (sec=unix) or if the server share is a DFS redirection to another server. The only user space interaction other than that is translating host names to ip address On Sat, Nov 1, 2008 at 8:21 AM, Jim Lehmer [EMAIL PROTECTED] wrote: I am having the same problem after an upgrade to 8.10. Note that I changed the three entries in fstab to include the nounix option to no avail - here's a sample [specific names and addresses changed to protect the innocent]: //xyzzy/Sources$ /usr/local/Sources cifs dir_mode=0777,file_mode=0644,iocharset=utf8,credentials=/root/.mountpw,rw,ip=10.0.0.162,domain=foo,netbiosname=bar,uid=snafu,gid=samba,nounix 0 0 However, when I use the same settings for a manual mount command, it works: sudo mount -t cifs -o dir_mode=0777,file_mode=0644,iocharset=utf8,credentials=/root/.mountpw,rw,ip=10.0.0.162,domain=foo,netbiosname=bar,uid=snafu,gid=samba,nounix //xyzzy/Sources$ /usr/local/Sources So, that leads me to wonder if it is a timing issue on boot and the mounts in fstab are trying to happen before samba client support is fully initialized? Client info: uname -a Linux bar 2.6.27-7-generic #1 SMP Thu Oct 30 04:18:38 UTC 2008 i686 GNU/Linux smbclient -V Version 3.2.3 cat /etc/issue Ubuntu 8.10 \n \l Server info: uname -a Linux xyzzy 2.6.24-21-generic #1 SMP Tue Oct 21 23:09:30 UTC 2008 x86_64 GNU/Linux smbd -i -V Version 3.0.28a cat /etc/issue Ubuntu 8.04.1 \n \l -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a direct subscriber of the bug. -- Thanks, Steve -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 286828] Re: CIFS share broken after upgrade from 8.04 - 8.10
Unlike smbfs, Linux cifs client requires very little user space intereraction unless you mount with Kerberos (sec=unix) or if the server share is a DFS redirection to another server. The only user space interaction other than that is translating host names to ip address On Sat, Nov 1, 2008 at 8:21 AM, Jim Lehmer [EMAIL PROTECTED] wrote: I am having the same problem after an upgrade to 8.10. Note that I changed the three entries in fstab to include the nounix option to no avail - here's a sample [specific names and addresses changed to protect the innocent]: //xyzzy/Sources$ /usr/local/Sources cifs dir_mode=0777,file_mode=0644,iocharset=utf8,credentials=/root/.mountpw,rw,ip=10.0.0.162,domain=foo,netbiosname=bar,uid=snafu,gid=samba,nounix 0 0 However, when I use the same settings for a manual mount command, it works: sudo mount -t cifs -o dir_mode=0777,file_mode=0644,iocharset=utf8,credentials=/root/.mountpw,rw,ip=10.0.0.162,domain=foo,netbiosname=bar,uid=snafu,gid=samba,nounix //xyzzy/Sources$ /usr/local/Sources So, that leads me to wonder if it is a timing issue on boot and the mounts in fstab are trying to happen before samba client support is fully initialized? Client info: uname -a Linux bar 2.6.27-7-generic #1 SMP Thu Oct 30 04:18:38 UTC 2008 i686 GNU/Linux smbclient -V Version 3.2.3 cat /etc/issue Ubuntu 8.10 \n \l Server info: uname -a Linux xyzzy 2.6.24-21-generic #1 SMP Tue Oct 21 23:09:30 UTC 2008 x86_64 GNU/Linux smbd -i -V Version 3.0.28a cat /etc/issue Ubuntu 8.04.1 \n \l -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a direct subscriber of the bug. -- Thanks, Steve -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 286828] [NEW] CIFS share broken after upgrade from 8.04 - 8.10
cat /proc/fs/cifs/Stats to see if there were any reconnections and cat /proc/fs/cifs/DebugData to list the version information that the server reports for this mount If you can save a wireshark (or tcpdump) trace of the failure that would be ideal and would allow diagnosing the problem quickly. See http://wiki.samba.org/index.php/Capture_Packets for more details on how to do that. On Fri, Oct 31, 2008 at 10:03 AM, Launchpad Bug Tracker [EMAIL PROTECTED] wrote: You have been subscribed to a public bug by Dustin Kirkland (kirkland): Binary package hint: smbfs System info: smbfs: Installed: 2:3.2.3-1ubuntu3 Candidate: 2:3.2.3-1ubuntu3 Description:Ubuntu 8.10 Release:8.10 [0 [EMAIL PROTECTED] ~]$ uname -a Linux firefly 2.6.27-7-generic #1 SMP Fri Oct 17 22:24:30 UTC 2008 x86_64 GNU/Linux Expected results: CIFS mounts keeps working after upgrade. Results: After upgrading from 8.04 to 8.10 (roughly one week ago, on the 23rd of Oct 08) using update-manager -d my CIFS mounts stopped working properly. I did not change any settings between them, and I have another machine on this network that is still running 8.04 and that doesn't have any problems. They mount fine, and I can, with some effort, copy and read files from it (though I have to do it manually, as many programs will whine). As an example (here /mnt/diverse is my cifs mountpoint, mounted from a MyBook network drive): [0 [EMAIL PROTECTED] ~]$ ls -l /mnt/diverse/test ls: cannot access /mnt/diverse/test: No such file or directory [2 [EMAIL PROTECTED] ~]$ touch /mnt/diverse/test touch: setting times of `/mnt/diverse/test': Not a directory [1 [EMAIL PROTECTED] ~]$ ls -l /mnt/diverse/test -rwxr--r-- 1 zerodogg zerodogg 0 Oct 21 08:39 /mnt/diverse/test [0 [EMAIL PROTECTED] ~]$ ls -l /mnt/diverse/test2 ls: cannot access /mnt/diverse/test2: No such file or directory [2 [EMAIL PROTECTED] ~]$ touch test2 [0 [EMAIL PROTECTED] ~]$ mv test2 /mnt/diverse/ `test2' - `/mnt/diverse/test2' mv: preserving times for `/mnt/diverse/test2': Not a directory mv: setting permissions for `/mnt/diverse/test2': Not a directory removed `test2' [0 [EMAIL PROTECTED] ~]$ chmod 644 /mnt/diverse/test2 chmod: changing permissions of `/mnt/diverse/test2': Not a directory [0 [EMAIL PROTECTED] ~]$ rsync -avzh --progress --partial test3 /mnt/diverse/ sending incremental file list test3 0 100%0.00kB/s0:00:00 (xfer#1, to-check=0/1) rsync: mkstemp /mnt/diverse/.test3.mllG7b failed: Not a directory (20) sent 87 bytes received 31 bytes 236.00 bytes/sec total size is 0 speedup is 0.00 rsync error: some files could not be transferred (code 23) at main.c(1058) [sender=3.0.3] The same commands, on the same mount on the 8.04 machine works perfectly fine. It also worked fine on this (8.10) machine before the upgrade. The relevant fstab entry (I have tried with and without dir_mode,file_mode,nounix): //zdmybook/DIVERSE /mnt/diverse cifs username=USERNAME,password=PASSWORD,uid=1000,gid=1000,dir_mode=0750,file_mode=0640,noauto,user,exec 0 0 [0 [EMAIL PROTECTED] ~]$ mount |grep div //zdmybook/DIVERSE on /mnt/diverse type cifs (rw,mand,nosuid,nodev) The fstab entry on the 8.04 box: //zdmybook/DIVERSE /mnt/Diverse smbfs username=USER,password=PASSWORd,uid=1000,gid=1001,noauto,user,noatime 0 0 And as an example, this time from the 8.04: [0 [EMAIL PROTECTED] ~]$ touch /mnt/diverse/123 [0 [EMAIL PROTECTED] ~]$ ls -l /mnt/diverse/123 -rwxr--r-- 1 lisbeth zerodogg 0 2008-10-21 08:53 /mnt/diverse/123 [0 [EMAIL PROTECTED] ~]$ mount|\grep div //zdmybook/DIVERSE on /mnt/diverse type cifs (rw,mand,noexec,nosuid,nodev) [0 [EMAIL PROTECTED] ~]$ LC_ALL=C apt-cache policy smbfs smbfs: Installed: 3.0.28a-1ubuntu4.5 Candidate: 3.0.28a-1ubuntu4.5 [0 [EMAIL PROTECTED] ~]$ lsb_release -rd Description:Ubuntu 8.04.1 Release:8.04 [0 [EMAIL PROTECTED] ~]$ uname -a Linux lisbeth 2.6.24-21-generic #1 SMP Mon Aug 25 16:57:51 UTC 2008 x86_64 GNU/Linux ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.edge.launchpad.net/bugs/286828 You received this bug notification because you are a direct subscriber of the bug. -- Thanks, Steve -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 286828] Re: CIFS share broken after upgrade from 8.04 - 8.10
If disabling LinuxExtensions works as described above, there may be a problem with the support for the Unix/Linux/POSIX cifs protcol extensions on the device you are mounting (which is why it is important to note the version information of the server as it is reported over the network). Not that you can also disable Unix extensions on reasonably recent Linux kernels by specifying nounix as a command line option. Specifying nounix on mount forces the client to treat Samba servers (and others which would otherwise support the cifs unix extensions) like Windows (and just use the more limited set of protocol operations). -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 286828] Re: CIFS share broken after upgrade from 8.04 - 8.10
Typo in the above (Not-Note) Note that you can also disable Unix extensions on reasonably recent Linux kernels by specifying nounix (as a cifs mount option) Also note that you would normally not need to specify the default uid, gid, and mode on the mount if the server and clients have the same uids (as they could if they are both using winbind to logon users). -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 286828] [NEW] CIFS share broken after upgrade from 8.04 - 8.10
cat /proc/fs/cifs/Stats to see if there were any reconnections and cat /proc/fs/cifs/DebugData to list the version information that the server reports for this mount If you can save a wireshark (or tcpdump) trace of the failure that would be ideal and would allow diagnosing the problem quickly. See http://wiki.samba.org/index.php/Capture_Packets for more details on how to do that. On Fri, Oct 31, 2008 at 10:03 AM, Launchpad Bug Tracker [EMAIL PROTECTED] wrote: You have been subscribed to a public bug by Dustin Kirkland (kirkland): Binary package hint: smbfs System info: smbfs: Installed: 2:3.2.3-1ubuntu3 Candidate: 2:3.2.3-1ubuntu3 Description:Ubuntu 8.10 Release:8.10 [0 [EMAIL PROTECTED] ~]$ uname -a Linux firefly 2.6.27-7-generic #1 SMP Fri Oct 17 22:24:30 UTC 2008 x86_64 GNU/Linux Expected results: CIFS mounts keeps working after upgrade. Results: After upgrading from 8.04 to 8.10 (roughly one week ago, on the 23rd of Oct 08) using update-manager -d my CIFS mounts stopped working properly. I did not change any settings between them, and I have another machine on this network that is still running 8.04 and that doesn't have any problems. They mount fine, and I can, with some effort, copy and read files from it (though I have to do it manually, as many programs will whine). As an example (here /mnt/diverse is my cifs mountpoint, mounted from a MyBook network drive): [0 [EMAIL PROTECTED] ~]$ ls -l /mnt/diverse/test ls: cannot access /mnt/diverse/test: No such file or directory [2 [EMAIL PROTECTED] ~]$ touch /mnt/diverse/test touch: setting times of `/mnt/diverse/test': Not a directory [1 [EMAIL PROTECTED] ~]$ ls -l /mnt/diverse/test -rwxr--r-- 1 zerodogg zerodogg 0 Oct 21 08:39 /mnt/diverse/test [0 [EMAIL PROTECTED] ~]$ ls -l /mnt/diverse/test2 ls: cannot access /mnt/diverse/test2: No such file or directory [2 [EMAIL PROTECTED] ~]$ touch test2 [0 [EMAIL PROTECTED] ~]$ mv test2 /mnt/diverse/ `test2' - `/mnt/diverse/test2' mv: preserving times for `/mnt/diverse/test2': Not a directory mv: setting permissions for `/mnt/diverse/test2': Not a directory removed `test2' [0 [EMAIL PROTECTED] ~]$ chmod 644 /mnt/diverse/test2 chmod: changing permissions of `/mnt/diverse/test2': Not a directory [0 [EMAIL PROTECTED] ~]$ rsync -avzh --progress --partial test3 /mnt/diverse/ sending incremental file list test3 0 100%0.00kB/s0:00:00 (xfer#1, to-check=0/1) rsync: mkstemp /mnt/diverse/.test3.mllG7b failed: Not a directory (20) sent 87 bytes received 31 bytes 236.00 bytes/sec total size is 0 speedup is 0.00 rsync error: some files could not be transferred (code 23) at main.c(1058) [sender=3.0.3] The same commands, on the same mount on the 8.04 machine works perfectly fine. It also worked fine on this (8.10) machine before the upgrade. The relevant fstab entry (I have tried with and without dir_mode,file_mode,nounix): //zdmybook/DIVERSE /mnt/diverse cifs username=USERNAME,password=PASSWORD,uid=1000,gid=1000,dir_mode=0750,file_mode=0640,noauto,user,exec 0 0 [0 [EMAIL PROTECTED] ~]$ mount |grep div //zdmybook/DIVERSE on /mnt/diverse type cifs (rw,mand,nosuid,nodev) The fstab entry on the 8.04 box: //zdmybook/DIVERSE /mnt/Diverse smbfs username=USER,password=PASSWORd,uid=1000,gid=1001,noauto,user,noatime 0 0 And as an example, this time from the 8.04: [0 [EMAIL PROTECTED] ~]$ touch /mnt/diverse/123 [0 [EMAIL PROTECTED] ~]$ ls -l /mnt/diverse/123 -rwxr--r-- 1 lisbeth zerodogg 0 2008-10-21 08:53 /mnt/diverse/123 [0 [EMAIL PROTECTED] ~]$ mount|\grep div //zdmybook/DIVERSE on /mnt/diverse type cifs (rw,mand,noexec,nosuid,nodev) [0 [EMAIL PROTECTED] ~]$ LC_ALL=C apt-cache policy smbfs smbfs: Installed: 3.0.28a-1ubuntu4.5 Candidate: 3.0.28a-1ubuntu4.5 [0 [EMAIL PROTECTED] ~]$ lsb_release -rd Description:Ubuntu 8.04.1 Release:8.04 [0 [EMAIL PROTECTED] ~]$ uname -a Linux lisbeth 2.6.24-21-generic #1 SMP Mon Aug 25 16:57:51 UTC 2008 x86_64 GNU/Linux ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.edge.launchpad.net/bugs/286828 You received this bug notification because you are a direct subscriber of the bug. -- Thanks, Steve -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286828] Re: CIFS share broken after upgrade from 8.04 - 8.10
If disabling LinuxExtensions works as described above, there may be a problem with the support for the Unix/Linux/POSIX cifs protcol extensions on the device you are mounting (which is why it is important to note the version information of the server as it is reported over the network). Not that you can also disable Unix extensions on reasonably recent Linux kernels by specifying nounix as a command line option. Specifying nounix on mount forces the client to treat Samba servers (and others which would otherwise support the cifs unix extensions) like Windows (and just use the more limited set of protocol operations). -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286828] Re: CIFS share broken after upgrade from 8.04 - 8.10
Typo in the above (Not-Note) Note that you can also disable Unix extensions on reasonably recent Linux kernels by specifying nounix (as a cifs mount option) Also note that you would normally not need to specify the default uid, gid, and mode on the mount if the server and clients have the same uids (as they could if they are both using winbind to logon users). -- CIFS share broken after upgrade from 8.04 - 8.10 https://bugs.launchpad.net/bugs/286828 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134716] Re: Mount with smbfs treats symlinks invalid
Because misconfigured symlinks can be a security exposure, discussing symlinks requires a little background: If the client is Linux client, Samba server by default reports a symlink as a symlink not as a directory. The Linux client can get information on the symlink and follow it. Symlinks from within a network export (share) to paths outside of the share, especially absolute paths (e.g. like /etc/passwd) are usually a bad idea, but there are cases where they may be useful. If you want to follow symlinks on the server, rather than have the client follow symlinks. You can turn off the Unix Extensions any of three ways: 1) unix extensions = no in the server smb.conf file or 2) turning them off on the client before mount echo 0 /proc/fs/cifs/LinuxExtensionsEnabled or 3) turning them off on the mount (cifs 1.50 or later, probably not in your kernel) mount -t cifs //server/share /mnt -o nounix Also note that symlink following on the server can be disabled by follow symlinks = no in the server's smb.conf (rarely needed) I don't think behavior on the client side has changed in a while here (other than the new mount option nounix) -- Mount with smbfs treats symlinks invalid https://bugs.launchpad.net/bugs/134716 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134716] Re: Mount with smbfs treats symlinks invalid
Note that smbfs symlink support may have problems. The cifs module has replaced smbfs (mount -t cifs //server/share /mnt instead of mount -t smbfs //server/share /mnt -- Mount with smbfs treats symlinks invalid https://bugs.launchpad.net/bugs/134716 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
