similar to: Possible issue with XFS Quotas and 3.0.22

I wrote into the list a few days ago about XFS Group Quotas not working in Samba 3.0.21c and 3.0.22. I have confirmed that if I uninstall 3.0.22 and reinstall 3.0.13, when I change an XFS group quota on Linux and mount a share that belongs to that group, if I look at the "Properties" for that share in Windows, Windows tells me that the "size" of the share is equal to the

Hi John (and others on the list) Can I suggest that you add some information to the new Samba docs explaining how to make Linux (or I suppose other Unix) group quotas be reflected in My Computer and/or Explorer when a Windows user accesses a share that is supposed to controlled by a quota? Here was my particular situation this past week. I was setting quotas based on Linux groups. Each

Hi all, is any one aware quotas not working in 5,5? I'm using XFS as a file system. My fstab has the appropriate usrquota,grpquota but when I try to run; quotacheck -cug /foo I get; quotacheck: Can't find filesystem to check or filesystem not mounted with quota option. I already have a large amount of data in the mount. Do quotas get implemented on only empty filesystems and

hi all, I hope you can help me with a strange quota/nfs/XFS behavior... I'm using Centos 5.6 on both a nfs server and client. Both are 64-bit, and using a recent kernel: NFS server: Linux fs2.priv 2.6.18-238.12.1.el5 #1 SMP Tue May 31 13:22:04 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux NFS client: Linux nx8.priv 2.6.18-238.12.1.el5 #1 SMP Tue May 31 13:22:04 EDT 2011 x86_64 x86_64 x86_64

Over the past few months, I have seen many postings here about runaway smbd processes with Samba versions 3.0.20 and above. Personally, it never happened to me until today. Also, I have stuck with Samba 3.0.13 on most of my machines because of THIS reported issue and a couple of other issues that I have experienced. However, I have a machine running RIGHT NOW where smbd has gone out of

I have spent most of the past 24 hours reading various samba docs and searching google for help -- but can't find a solution. Suggestions and solutions would be appreciated. I have set up a Linux Box (Samba 3.02) as a PDC with roaming profiles. (I haven't upgraded, because this box is a model for over 100 other boxes in the field). I can add XP users to the domain and their roaming

I have noticed recently that Windows XP seems to stop writing into Linux/Samba shares once there is 2 TB of data in the share. Windows Explorer is happy to report that a share has 4.8 or 8 or 10 TB of space available, but Windows seems to cease writing into the share once there are 2 TB in it. Is this a known limitation of a) Windows or b) Samba or c) both? It certainly isn't a

Hi All, I have this very odd issue where after a migration we have some users who have quotas showing 8192.0EB in use, when in reality on disk there is only a couple hundred megabytes. The host in question is a: * CentOS 6.3 host with mostly latest patches (except latest glibc patches) * running in SELinux Enforcing mode (Permissive doesn't seem to help) * all file systems are on Logical

I haven't had a chance to look at the list very carefully for the past few weeks, so I apologize in advance if I'm asking a question that has recently been discussed. I seem to recall there has been some discussion about a similar situation to the one I am in. My situation is that I am having an issue with READ ONLY files -- and seeing very different behavior with Samba 3.0.20b

Do anyone have any experience using 10 Gigabit Ethernet connections with Samba? Specifically, if you have had such an experience, can you share what sorts of optimizations you made to get the maximum data transfer between server and workstation? I am just experimenting with this kind of setup myself and I see a huge GULF between the raw TCP/IP transfers that I can make between two

Can anybody explain why SOME Windows XP applications have trouble writing files larger than 2 GB (or sometimes larger than 4 GB) to Linux Samba shares, when OTHER Windows applications on the same machine do not have difficulty writing large files to the same Samba share? And when the underlying Linux filesystem supports very large files? I have sometimes even found that a SINGLE Windows

Hi Samba 3.6.3 on Ubuntu. Filesystem is xfs, grpquota and usrquota are enabled. root at host:# repquota /mntpoint displays the correct data (see below). In smb.conf I defined max protocol = SMB2. When running smbcquotas //host/share -L I'm getting displayed a value of 16GB for every user share. This is the value that is displayed on the windows 7 boxes when looking at the network shares in

Apparently there's a new "Inherit Owner" option for smb.conf that allows you to configure Samba to set the owner of a new file or directory based on owner of the parent directory. That seems like a very useful feature! My question is, does "Inherit Owner" also work when you MOVE a file from one directory to another? In other words, if a file called

Hi, I have a weird problem with a Linux Server acting as a PDC with Samba 3.02. If I map a particular Samba share as the "Z" drive -- and I use roaming profiles with a logon.bat script -- the share will NEVER automatically reconnect when logging on again. This happens 100 percent of the time. And now the same thing seems to be happening for any shared mapped as the

Hi All, I have a very strange problem that I'm unable to pinpoint at the moment. For some reason I am simply unable to get xfs_quotas to report correctly on a freshly installed, fully patched CentOS 6 box. I have specified all the same options as on another machine which *is* reporting quota LABEL=TEST /exports/TEST xfs inode64,nobarrier,delaylog,usrquota,grpquota 0 0 xfs_quota -xc

Does somebody know if the Samba Client in MAC OS X (10.3.4 and 10.3.5) has problems looking at Linux-based Samba shares that are larger than 2 TB? I have Samba 3.0.2 running on my Linux box. I have never had any difficulty with the Mac seeing a 2 TB RAID array on the Linux box, but when the Mac looks at the 4 TB array, it can see all the contents and create folders but it can't create

Hi, Is there a simple way to set up Samba so that users ONLY see the shares that belong to them? I'm not talking about the user's HOME directory. But lets say I have 60 shares in my smb.conf file. To make it less confusing for users when they access the Samba server from Windows, I want the users to ONLY see the shares that belong to them. So, I want to set up each share so that

Can somebody tell me how to get samba to ask me for a username and password when I click on my Samba server in Windows XP Explorer? When I click on another computer on the network (Workstation A) from a workstation (Workstation B) where I'm NOT logged in with a username:password that Workstation A recognizes as having an account, I get a dialog box asking me for a username and password.

I have Samba 3.0.0 installed on Mandrake 9.2. I also have Samba 2.8.8a installed per instructions from Mandrake -- but I do NOT start Samba 2.8.8a automatically. In fact, I don't use it at all. Maybe I should uninstall the Samba 2.8.8a rpm??? I will update to 3.0.1 as soon as an rpm is available from Mandrake. Anyway, I have a problem when I try to add a new share to my smb.conf file. I

Hi, I'm setting up a Linux machine to use as a file server for a small group of windows machines. Like many of the folks who write to this list, I'm having all kinds of difficults getting the Windows machines to be able to access the Linux shares. In my case, the most frustrating thing is that all of my Windows machines and users can access the Linux shares SOMETIMES. But