Samba issue on Lenny with new kernel 2.6.26.1.486 no read write access ?
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Since the update I can not save files or projects using any KDE aps. I use QUANTA for my web editing, same goes for Kate.
I get the error message
Quote:
Not enough disk space or you dont have permission to write to etc...
( there is over 450 Go free space and permissions are correct on the server)
I do not get this problem with any other Gnome apps such as GEDIT or GIMP OOFICE etc
I checked and have all the correct QT libraries ?
So for now I boot on/use 2.6.25-2-486 just so that I can work, but I would like to use 2.6.26.1.486.
This is specific to this PC as My lap top is running 2.6.26.1.486 and I have no issues there, I can connect to the server and work ok.
It just looks like KDE aps dont have read write acces to samba shares I thought it was a group issue but even when I mount the samba partition as root I get the same problem!!
Has anybody come across this problem I am stumped, I could consider a reinstall but surely there must be some simple reason, which for now I have not found.
Use the cifs filesystem instead of smbfs. The smbfs is obsolete and may not be included in future kernels. Never use it again!
Also consider creating a credentials file in your home directory and using the "credentials=<path/to/file>" option. That way another user won't be able to read your credentials from the /etc/fstab file.
The _netdev option is a good one to use if the network isn't ready for you to mount a samba share. If you use /etc/fstab, you might want to use "noauto" instead so that if you aren't connected to the network, booting won't stall or fail.
You can enter "sudo mount -a -o _netdev" to mount all of the entries in /etc/fstab that have the _netdev option.
Please see the mount.cifs manpage for more options.
Not to sure how to go about that ?
Is it an other network file system
Note that when I close the PC It hangs always with error message
Cifs not found..
grep -i cifs /boot/config-2.6.25.11-0.1-default
CONFIG_CIFS=m
CONFIG_CIFS_STATS=y
CONFIG_CIFS_STATS2=y
CONFIG_CIFS_WEAK_PW_HASH=y
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_EXPERIMENTAL is not set
You might consider creating a new initrd file which includes the cifs module.
Most filesystems have a kernel module that needs to be loaded before using the filesystem. For example, the "xfs" filesystem. Before mounting an xfs filesystem, you need to have the xfs module loaded.
---
Windows may shut down the NIC device when you close the lid. Look into the power saving features and the network configuration. I think it is in the Former. The same thing may happen if you unplug the power adaptor from the laptop.
debian:/home/ppayne# grep -i cifs /boot/config-2.6.26-1-486
CONFIG_CIFS=m
# CONFIG_CIFS_STATS is not set
CONFIG_CIFS_WEAK_PW_HASH=y
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_CIFS_DEBUG2 is not set
CONFIG_CIFS_EXPERIMENTAL=y
CONFIG_CIFS_UPCALL=y
CONFIG_CIFS_DFS_UPCALL=y
I'm not certain which PC you are closing the lid for. It sort of reminds me of the joke where a patient says, "doctor, it hurts when I bend my elbow like this". The doctor responds, "Well don't bend it like that then."
Determine whether the NIC card shuts down when you close the lid. It is probably a power saving feature or the pc may even go into standby mode. Until you found out why, don't close the lid.
You are mounting a share on the server, usually, if you have a samba server with raid, it is what is offering the shares. What computer is on 192.168.0.2? Check who has write permission to the share on the machine offering the share. Check who has write permission on the directory itself.
If you use "security = users", the default, on a machine running a samba server, there are three things you need to configure. The Windows users also need to be Samba users. The credentials need to match. If you don't use LDAP, AD or tdbsam for a password backend, you need to use smbpasswd to enter the users & passwords for the windows users.
Is the user on both the server and the client the same user? Cifs will allow you to use the same permissions and acls as you would for a local drive.
Take a look at the long listing of the mounted share.
I have gone over all this again and have not advanced I am still running on the 2.6.25-2-486 kernel
as on the 2.6.26.1.486 none of my KDE apps have write permission on the samba (cif) share.
What Is really weird is that my lap top running the same set up with 2.6.26.1.486 does not have this issue ??!
It has to be something specific to this PC
Maybe something with cifs not set up correctly or a network problem..
(I checked my host file all the pc's on the network are correctly declared)
The network is on DHCP and the ip addresses are reserved on the router with the mac addresses..
And the PC still hangs on shutdown message :
CIFS SERVER NOT RESPONDING
Thanks for all this info, still haven't figured it out!
I should add to make the point that this issue is only on 1 pc (RUNNING GNOME !) USING KDE APS, Quanta, kate etc..
I have one other PC with deb 4
one lap top with lenny
1 pc with winxp/lenny/ubuntu
They can all run KDE apps with write permissions (excl off course winxp which to my knowledge does not run any kde apps :=)
I can bring a clients PC here for an update / back up his files and I access the server immediately read/write no problem, after entering the smb password/user
I have no issues with those machines, just the current PC I am talking about here
in smb.conf on the server (192.168.0.2) I have security = users I set the passwords with smbpasswd on the server from the start
the user/pwd account on my works station and the server are the same
I can access the server with SSH the PC runs normally until I use the new kernel 2.6.26.1.486
Hope all this is clear, hardest part is explaining problems, gulp...
It shouldn't matter whether you are trying to write using a kde app or from the shell.
Look at the mounted directory with "ls -ld". Do you have write permissions. Try creating a file in the console. E.G.: touch /mnt/share/testfile
Chech the permissions on the server. Does your user have permissions to write to the directory.
Write permissions can be denied on the filesystem, by how it is mounted, or by the samba configuration.
If a remote user doesn't exist as a Linux user on the server, then the "o" write permissions need to be disabled. If a remote user doesn't exist as an smb user (i.e. not in smbpasswd) then that user may be either denied access outright or may be aliased to the "guest" user in Samba/Windows and "nobody" in Linux.
---
I guess that I misunderstand what you mean by "close the pc". You were refering to the laptop, and I though you were closing the lid on the laptop.
Make sure that the laptop is plugged in. The system may power down the NIC device to save power otherwise. This happens on windows XP at least and you need to manually enable the NIC.
Monitor the samba logs on each machine as trying to write to the share. Try to create a file there, or copy a file there in the shell.
Print out the permissions of mounted share and your current /etc/fstab entry. (obfuscate a password= entry, although you should use credentials= instead)
Print out the share definition on the server. Does it use a write list?
Check for differences in the values of the pseudo files in /proc/fs/cifs/ between the two kernels. Also check the debian mailing list for similar problems with this kernel. ( They fork there own versions of openssl, firefox, etc. I wouldn't be surprised if they do the same with samba or the kernel. )
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.