search for: tuckerd

I have 2 machines in a cluster using GFS, that many client mount up via nfs. We use quotas extensively here, is there a way from a client machine to check a users quota? Standard quota command on client machines do not work like they do when checking a non-gfs nfs mounted file system. The quotas do work however, when a user exceeds quota and tries to write a file, it tell them that quota has

This is the 2nd time this has happened to me. There was a kernel release over the weekend to .67.0.15, yet, they did not release the updated GFS to go along with it, so when the machine rebooted, there was no gfs file system in the new running kernel which in turn wreaked havoc on my cluster. I truly wish they would not do that :). I guess I shall have to not allow automatic yum updates from

Hello group, this issue is driving me crazy, there just has to be a simple way to do this that I am missing! I have a share, SOP. The file system maps to /dir/dir/sop. If I have a set of users that need write access to this directory, but only want to allow another set of users read only access, how can I accomplish this? From the man pages, it looks like I can set the share to read only, and

I have a 2 node cluster that has been running for a year, and is still up and working fine. However, a yum update at some point broke system-config-cluster and it cannot load the management tab anymore, because it *thinks* the node is not part of a cluster, yet, all of the definions are there and I can modify them and save, but cannot publish the changes to the cluster using the tool. Has anyone

I'm going to post a question to the group that I'm sure has been answered before, but all the googling in the world isn't helping me. Is there a searchable archive of this mailing list somewhere?

Greetings! I have my samba server joined to an ADS 2003 server, and authentication is working fine for all XP clients. However when Win2k clients try to map a share, they get the error: System error 1311, no authentication servers are available. How do I correct this?

We are have a very serious issue we cannot seem to solve. I cannot duplicate the problem by trying, but sometimes when clients are logging out, the smb processes are not closing upon their exit, and leaving the processes running indefinitely, and often times with locked files that they cannot then access when they log back in. Doing a kill or even a kill -9 on the process id often times will not

All, I've exhausted myself on this issue. Our samba server has been up and running for ages without any issues. About 6 weeks ago quite suddenly we began having intermittent clients hangs network wide and I'm at a loss to find the issue. The users have so named them the windows explorer status bar of death. It has been extremely disruptive when it happens. Looking at the logs at

I'm getting this frequently in our logs but I cannot replicate the problem when I try. I have a user successfully map his home directory: 2007/09/05 09:13:14, 2] auth/auth.c:check_ntlm_password(305) check_ntlm_password: authentication for user [lmerrill] -> [lmerrill] -> [lmerrill] succeeded [2007/09/05 09:13:14, 3] libsmb/ntlmssp_sign.c:ntlmssp_sign_init(319) NTLMSSP Sign/Seal -

I have a cluster that has been operational for some time and functioning flawlessly until a recent yum update. The last unflawed working kernel was 2.6.9-55.0.12.ELsmp. The current kernel is 2.6.9-67ELsmp. The problem appears to be some type of infinite recovery loop of sorts. It runs find for a few minutes, then the service restarts itself. What I am seeing in /var/log/messages is: Jan 3

All, I sent a message for help a couple of weeks ago about a samba migration issue. With further testing, we have isolated the issue to Microsoft Outlook (versions 2007 and 2010). All other applications have no issues when they mount the new samba server reading, writing, etc. But, in Outlook, when you try to open an archive (pst file) on the new samba server, it pops up an error "the

I have 2 samba servers. One with centos5+samba 3.033 that has been in service for a few years now. I have installed a centos6+samba 3.6.9. I followed the how-to I did with the first one, copied over the krb5.conf and smb.conf from the working server and all seemed to go well. It is a member server of a window AD. We have 2 DC's that are part of the same forest: SEAS and SEAS-S. I

Very odd issue. Transitioning over to a new samba 3.6.9 (from 3.0.33) server. Majority of the users are ok, but a handful of users cannot map their home directories from windows7 clients. Logged into XP their homes map fine. They pass authentication: (log snippet) [2014/03/24 17:20:43.277337, 3] auth/auth.c:219(check_ntlm_password) check_ntlm_password: Checking password for unmapped

I recently joined a samba 3.0.22 server to AD. When I did the kinit, the AD gave me a 24 hour ticket with a 1 week renewal. Setting -r and -l to 365d did not change anything, the ticket still came back the same. However, my question is in reguard to whether this is really even needed? First, I deleted the ticket, and everything seemed to continue to work perfectly. Now, I let the ticket expire