similar to: Strange problem with file locking (so it seems)

Hello, all. A while back I posted a question about an issue, but did not get any replies. I understand this might not be something anybody has a definite answer for, and I understand I may not be offering the right information. If that is the case, please let me know what information I can provide, and please don't hesitate to offer any suggestions about what could be causing this problem.

Hi Kris, lsof (http://freshmeat.net/projects/lsof/) available with most distributions might be your friend: > About: > Lsof is a Unix-specific diagnostic tool. Its name stands for LiSt Open > Files, and it does just that. It lists information about any files that > are open by processes currently running on the system. It can also list > communications open by each process. Using

This seems like it should have an obvious answer, but I haven't seen a clear word one way or the other in the man pages or other documentation that I have read - is smbmount's behavior in any way governed by the smb.conf file? The reason I ask is one of the other sysadmins here has been trying to figure out ways to improve smbfs performance, and he came across the speed.txt file in

'lo all Im wondering if anyone is getting the same problem with smbfs as i am with the 2.2.x kernels when i try to smbmount a share i get the following on the screen "SMBFS: need mount version 6" and also on the telnet shell or actual shell "mount error: Invalid argument Please look at smbmount's manual page...." the mans have nothing i revert back to 2.0.x and it

Dear R People: I'm sure that this is a very simple problem, but I have been wresting with it for some time. I have the following file that has the following one line: CRS("+init=epsg:28992") Fair enough. I scan it into R and get the following: > u [1] "CRS(\"+init=epsg:28992\")" > gsub(pattern='\"',replacement='"',x=u) [1]

Hello all. Our system consists of two linux machines, each running Red Hat 7.1 (kernel 2.4.9-34), using SMB to mount multiple shares hosted by a Windows 2000 Advance Server. smbclient from Samba 2.2.5 is used to do the actual mounting. Over the weekend, a number of files on these SMBFS shares were created with incorrect timestamps (modification times). In some cases, the timestamps were off by

Two days ago I got a whole slew of smbfs errors in my system logs, all stemming from an apparent inability to read two files. Here are some samples: Oct 7 14:36:41 server kernel: smb_file_read: cur/1033577524.16219.server.iatdev.com,S=230098@2,T validation failed, error=4294967294 Oct 7 14:36:47 server last message repeated 5984 times Oct 7 14:36:47 server kernel:

Hello, I am trying to work out the file locking mechanism on our Samba server when connecting from Linux clients. I am getting some strange behaviour in a mixed Linux/Windows environment when multiple clients open/lock the same file for writing. Everything seems fine when a Windows client creates the lock, but if a Linux client creates the lock, we get either two or more Linux clients being able

I periodically see smbfs questions get asked on this list, and they usually get one of two responses: 1. smbfs is a kernel module; this list is not the appropriate place to be asking smbfs questions. 2. You should be using cifs instead. (Please let me know if either if these is incorrect.) I was surprised to see, however, that the smbmount / mount.smbfs manpage makes no mention of cifs as being

Hello everyone. I have two linux servers* that each have four directories mounted as SMBFS shares from a Windows 2000 Server. For the most part, this set-up is working great, however, there have been occasional hiccups. Every so often, one of the servers, LINUX-ONE, logs a couple of Samba-related errors. The following is an example: Jun 30 06:30:45 mx-two kernel: smb_trans2_request:

Hi! I am experiencing strange smbmount problems with my 3 computers. I have: janeway, an NT 4.0 SP5 box, torres, a Linux box running kernel 2.0.36 and samba 2.0.5a, q, a Linux box running kernel 2.0.36. Both Linux machines have smbfs compiled as a module and loaded. I can smbmount janeway shares on both torres and q, and I can see torres shares on janeway. Naturally, q can't be seen by

I've been working with smbfs/smbmount the last few weeks to allow my linux log processing server access to the logs on our NT servers. The problem is that after a period of time all the smbfs mounts become invalid with either one of two errors. When you do a 'df -k' to view the mounts you see the following: samba:~# df -k Filesystem 1k-blocks Used Available Use%

Hi! I've got a problem with write access on samba fileshares mounted via fstab on two Debian Sarge servers. These servers are behind firewalls and can only access each other, so security is not an issue. They are configured as follows: I'll use placeholders for IP-adresses, usernames, passwords etc. just out of paranoia, I do know, that these IPs do not make sense ;) the servers are

By the way, the wait-period before the write access is "committed" or whatever is always precisely 30 seconds, so I believe, that there may be some timeout issue before samba is actually doing what it's supposed to do. Has anybody got an idea? > -----Urspr?ngliche Nachricht----- > Von: samba-bounces+markus.wollny=computec.de@lists.samba.org >

Hi! I have some problem with samba. The problem concerns the smbfs kernel module and smbmount. Smbfs makes other processes "hang". The only thing to do is to reboot the computer, not even "Kill -9" works. I use a Linux system with the Redhat 7.2 distribution. It runs on a AMD 500 K6-2 processor with a memory of 192MB. The kernel is an unmodified 2.4.9-31 from Redhat. I have

Mrs.; I have a 16-bits Cobol program running at Novell 5.1. I'm migrating the whole network (around 150 terminais) to Linux + LTS processing DOSEMU into cluster and making a storage server just for data. My surprise last week was that the smbfs client for Linux doesn't support the file locking, after googling, found that a solution would be to use CIFS instead SMB and upgrading the

I'm encountering a nasty file locking problem on my development system. The base system is WinXP SP2 (call it "Alpha"), on which there is a shared directory ("D:\Websites") on NTFS. Running in a M$ Virtual Machine session on Alpha is an Ubuntu Linux (6.06) system, call it "Beta". Most of the website development is done on Alpha, and Beta gets spun up to

I have a similar line in my network script, for the same reason. THIS problem is different. I cannot umount those shares after the windows machine goes down, no matter what commands I try. Joel On Mon, Dec 03, 2001 at 02:49:01PM -0800, Bill Parker wrote: > > Joel, > > I used to have the same problem with smbfs type mounts hanging > until I modified /etc/rc.d/init.d/network to add

Fellow SAMBA lovers: I've been using 'mount -t smbfs blah blah' for over a year to do backup/restore. I recently upgraded SAMBA from 2.2.2 to 2.2.3a and the NT Server I was attaching to from v4 to Win2k. Now 'mount -t smbfs' returns an error. However, smbmount with the same parameters works, so I just changed the scripts to use smbmount. I suspect it's the Windoze server

I know this issue has been beat to death on the newsgroups, but I have not yet found an answer. I will make an attempt to include all the necessary info. Description of Problem: I am having problems trying to access large files (>2GB) on mounted smbfs volumes. To clarify, I am attempting to view large files that exist on an NT server, from my Linux box, and getting erroneous results.