Tag Archives: NFS

Linux

/var getting fill frequently

Leave a comment

By solaris_1977

I have Red hat Linux server. There are 14 NFS shares which are coming from NAS. There are so many messages filling /var/log/messages, which seems like some NFS logging is enables somewhere, but I am not able to figure it out. Every few minutes, it will filll my /var (which is part of root) to 100%

Code:
Jul 23 16:15:26 vmvctppd09 kernel: NFS: read done (0:11/165604 4096@2499461120)
Jul 23 16:15:26 vmvctppd09 kernel: NFS: read done (0:11/165604 4096@2499465216)
Jul 23 16:15:26 vmvctppd09 kernel: NFS: read done (0:11/165604 4096@2499469312)
Jul 23 16:15:26 vmvctppd09 kernel: NFS: read done (0:11/165604 4096@2499473408)
Jul 23 16:15:26 vmvctppd09 kernel: NFS: nfs_readpage_result: 10753, (status 32768)
Jul 23 16:15:26 vmvctppd09 kernel: NFS: nfs_update_inode(0:11/165604 ct=1 info=0x7e7f)
Jul 23 16:15:26 vmvctppd09 kernel: NFS: read done (0:11/165604 4096@2499706880)
Jul 23 16:15:26 vmvctppd09 kernel: NFS: read done (0:11/165604 4096@2499710976)
Jul 23 16:15:26 vmvctppd09 kernel: NFS: read done (0:11/165604 4096@2499715072)
Jul 23 16:15:26 vmvctppd09 kernel: NFS: read done (0:11/165604 4096@2499719168)
Jul 23 16:15:26 vmvctppd09 kernel: NFS: read done (0:11/165604 4096@2499723264)
Jul 23 16:15:26 vmvctppd09 kernel: NFS: read done (0:11/165604 4096@2499727360)
Jul 23 16:15:26 vmvctppd09 kernel: NFS: read done (0:11/165604 4096@2499731456)
Jul 23 16:15:26 vmvctppd09 kernel: NFS: read done (0:11/165604 4096@2499735552)
Jul 23 16:15:26 vmvctppd09 kernel: NFS: read(logs/access_log, 219024@2499428879)
Jul 23 16:15:26 vmvctppd09 kernel: NFS: nfs_readpage_result: 10754, (status 32768)
Jul 23 16:15:26 vmvctppd09 kernel: NFS: nfs_update_inode(0:11/165604 ct=1 info=0x7e7f)
Jul 23 16:15:26 vmvctppd09 kernel: NFS: read done (0:11/165604 4096@2499739648)
Jul 23 16:15:26 vmvctppd09 kernel: NFS: read done (0:11/165604 4096@2499743744)
Jul 23 16:15:26 vmvctppd09 kernel: NFS: read done (0:11/165604 4096@2499747840)
Jul 23 16:15:26 vmvctppd09 kernel: NFS: read done (0:11/165604 4096@2499751936)
Jul 23 16:15:26 vmvctppd09 kernel: NFS: read done (0:11/165604 4096@2499756032)
Jul 23 16:15:26 vmvctppd09 kernel: NFS: read done (0:11/165604 4096@2499760128)
Jul 23 16:15:26 vmvctppd09 kernel: NFS: read done (0:11/165604 4096@2499764224)

Can somebody suggest me, where to look and stop these logging messages ?
———————————————————————————–
I got the fix. Somebody has put nfs pid in /proc/sys/sunrpc/nfs_debug and that was reading that pid continuosly and throwing messages. Thanks

…read more

Source: FULL ARTICLE at The UNIX and Linux Forums

Linux

NIM on firewalled environment

Leave a comment

By depam

Currently setting up NIM on a firewalled environment and multiple gateways. By following the ports need to be opened on the below link:

IBM NIM Communication within a Firewall Environment – United States

I have asked network team to open up firewall but omitted the 32,768 to 65,535 port as our security won’t be able to open this big port ranges.

It seems that NFS by using mountd can be specified a specific port but TFTP specifically needs this high port:

tftp:
Client UDP Master UDP 69
Client UDP Master UDP (random port between 32768 and 65535)

Here the client communicates via UDP to the master’s port 69. The port that the client uses cannot be predicted.
Then, the master responds from port 69 back to the same port that made the request.
I used the bidirectional arrow to represent this.
Then random UDP ports are chosen on both the master and the client to affect the transfer of data. Again bidirectional.

Does this mean that nim mksysb might work but OS restore wont?

…read more

Source: FULL ARTICLE at The UNIX and Linux Forums

Linux

NFS RFS3_LOOKUP alerts

Leave a comment

By batas

Hi Guys,

Would anyone know how to fix this message appearing on the server logs.

“Failed to decode arguments for NFS version 3 procedure RFS3_LOOKUP client”

NFS server is set to use ver3 for client/server and on the NFS clients all mounted FS are using ver3.

but we are still getting the message above from a client that has no mounted FS from the NFS server.

From: http://www.unix.com/unix-linux-applications/221787-nfs-rfs3_lookup-alerts.html

Video Gaming

Criterion Boss: "Time to Make Something New"

Leave a comment

Acclaimed British developer Criterion, best known for making Burnout and Need for Speed: Hot Pursuit and Most Wanted, is going to stop making racing games. At least for a while, anyway. The studio chief Alex Ward announced the news in a series of tweets, which you can read below:

— Alex Ward (@AlexanderJWard) April 15, 2013

Continue reading…

From: http://www.ign.com/articles/2013/04/16/criterion-moving-away-from-making-racing-games

Linux

Can't chgrp. Error – chgrp: changing group of `<file>': Invalid argument

Leave a comment

By venmx

I found that I cannot chgrp for some reason with error:

chgrp: changing group of `’: Invalid argument

This happens on all NFS mounted disks on client machines.

We use AD (not my call) for authentication and it also provides groups.

We have a NFS server running Scientific Linux 6.3 which mounts SAN devices on FC connect. These are then exported via NFS. Clients are all CentOS 6.4.

The clients hard mounts the user’s home disk with intr,sync and various tuning options. The other disks use autofs.

AD is configured so that each user has a matching UID and GID, essentially making them the exclusive member of their own group. Not useful for sharing files unless you don’t mind making all your files accessibly by world, o+.

We need groups so that we can add members who are then able to chgrp what ever files they’d like to share with members of the same group. All seems pretty straight forward so far.

I used to run OpenLDAP with Kerberos to do all this, I had LDAP manage autofs and groups. Everything worked perfectly.

But now I cannot chgrp.

The permissions of the exported directories on the NFS server are:
drwx–x–x root root /san/home
drwxrwxrwx root root /san/otherdisks

But under home each user directory is owned by the user:
drwx–x–x user1 user1 /san/home/user1

NOTE: “other” means machines within same organization using same AD but built by other departments, “this” means the machines I built.

In the following scenarios it fails:

1. As AD user on “this” client machine on own home on “this” NFS server.
2. As AD user on “this” client machine on automounted disk on “this” NFS server.
3. As root on “this” client machine on automounted disk on “this” NFS server.

In the following scenarios it works:

1. As AD user on “this” client on local partitions where permissions allow.
2. As AD user logged in directly on “this” NFS server on any partition where permissions allow, including on SAN disks.
3. As root on “this” file server on any partition.
4. As AD user on “other” clients on export from “this” NFS server.
5. As AD user on “other” clients on export from “other” NFS server.
6. As AD user on “this” client on export from “other” NFS server.

This issue shows itself when I extract TAR files whilst on client machines to NFS exported shares as AD user or root, can’t chgrp!

I can do everything else, I can create, delete, even do newgrp and change my default group then create new files belonging to me with GID of new group. But still can’t chgrp

From: http://www.unix.com/red-hat/221091-cant-chgrp-error-chgrp-changing-group-file-invalid-argument.html

Linux

Dolphin bugs fixed in March 2013

Leave a comment

Here is a summary of the bug fixes that Dolphin users who upgrade to last week’s release can benefit from:

  • Bug 288824: Fix the problem that no custom icons are shown for folders which are accessed via NFS and some other file systems. See git commit 6369b556 for the infrastructure in kdelibs, and commit b8c9aa55 for the patch that makes Dolphin use it.
  • Bug 316335: Make sure that children of expanded directories are removed from the model if the parent is collapsed, and prevent that they reappear when the filter is removed. See git commit acec0e65, review request 109343.
  • Bug 315619: Do not skip rows in Details View when scrolling by clicking the empty area of the scroll bar. See git commit 6ba70a6f, review request 109210.
  • Bug 316615: If files with multiple types are selected, show the services for the file type ‘octet stream’ in the context menu. See git commit 4da8e6cd.
  • Bug 316016: Another kdelibs issue that caused Dolphin to not update the view properly. This one was about the deletion of a directory not being noticed and could be fixed thanks to good instructions to reproduce the bug provided by the forum user gedgon. See git commit 1f6d6cfc.
  • Bug 316300: Fixed a bug in the code that prevents the unintended execution of commands in the Terminal Panel when changing the view. This bug could lead to the command being executed in some corner cases. See git commit 6be6988f, review request 109431.
  • Bug 315693: Ensure that the Information panel shows “&” in filenames correctly. See git commit 914b8d88, review request 109129.
  • Bug 295300: Make sure that F5 reloads all expanded directories when viewing a remote directory. See git commit d3ad8f59, review request 109488.
  • A follow-up to the fix for bug 299371: Fix transition between normal and hover images. See git commit 472608e8, review request 109614, and Aurelién’s blog post for details about his smart debugging tricks.
  • Bug 317018: Fix a crash in the Mercurial plugin when deselecting a file to commit. See git commit 1f1392a6.
  • Bug 315569: Group files by name correctly also for non-ASCII file names. See git commit 02f4a69f, review request 109457.

Thanks to everyone who helped to make these bug fixes possible: Aurélien Gâteau, David Faure, Emmanuel Pescosta, Martin Koller, Pierre Sauter, Vishesh Yadav, Weng Xuetian.

From: http://freininghaus.wordpress.com/2013/04/11/dolphin-bugs-fixed-in-march-2013/

Linux

NFS Mount 16+ group Issue in AIX

Leave a comment

By pinnacle

Hi,
I am trying to read files from NFS mount. The ID with which I am trying to read is part of 16+ groups.

This is causing problem in doing change directory to the NFS mount directory.

I was able to get some code which does newgrp to change the default group so that I could change directories into NFS mount.
But as per the man pages of “newgrp”. Looks like newgrp command invokes new shell everytime when it is called.
I am calling newgrp command as part of my korn shell. I would like to know, if calling it will impact my rest of the shell.
Looks like I could handle this issue by using here document.
But not sure if this is the right way. I have read other documentation to handle this NFS mount 16+ group situation but nothing seems to be helpful in my case (and not easy to understand documentation)
Help is appreciated.

Code:

/usr/bin/newgrp group1 << newgrp1
echo "Changing directory to /nfsmount/abc"
cd /nfs/abc

/usr/bin/newgrp group2
cd /nfs/abc/def

cp /nfs/abc/def/test.txt /landingarea/app
if [ $? -eq 0 ];
then
echo "copy successfull"
else
echo "copy failed
fi
newgrp1

…read more

Source: FULL ARTICLE at The UNIX and Linux Forums

Linux

Replaying log stuck during boot

Leave a comment

By filosophizer

I had some problems with NFS see here: http://www.unix.com/302790997-post9.html

and now I cannot boot the partition

when I boot I get stuck here

Code:
Saving Base Customize Data to boot disk
Starting the sync daemon
Mounting the platform dump file system, /var/adm/ras/platform
mount: 0506-324 Cannot mount /dev/fwdump on /var/adm/ras/platform: A file or dir
ectory in the path name does not exist.
Starting the error daemon
System initialization completed.
Setting tunable parameters...complete
Starting Multi-user Initialization
Performing auto-varyon of Volume Groups
Activating all paging spaces ...read more

Source: FULL ARTICLE at The UNIX and Linux Forums

Linux

Trouble with .tar creation over NFS mount

Leave a comment

By ikn3

Hello,

I am trying to backup a directory to an NFS mount. But after mounting the “tar” command is failing.

1. Created folder for mount point: test1
2. Mounted desired mount:
[root@server_name1 ~]# mount -t nfs server_name2:/backup/WMSAPP_backup -w /test1/
[root@server_name1 ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVolRoot
19G 14G 4.1G 78% /
/dev/mapper/VolGroup00-LogVolTmp
9.5G 3.9G 5.1G 44% /tmp
/dev/mapper/VolGroup00-LogVolVar
4.8G 574M 4.0G 13% /var
/dev/mapper/VolGroup00-LogVolApps
99G 14G 81G 15% /apps/scope
/dev/sda1 996M 41M 904M 5% /boot
tmpfs 7.9G 0 7.9G 0% /dev/shm
server_name2:/backup/WMSAPP_backup
1008G 80G 878G 9% /test1

[root@servera-name1 ~]# tar cvf /test1/app_scope.tar /apps/scope/
tar: /test1/app_scope.tar: Cannot open: Permission denied
tar: Error is not recoverable: exiting now

A. Is there a different way of mounting where we can pass credentials. I read somewhere that we do not need credentials to mount as NFS.

B. Is there a different tar option that we can use…

THanks in advance for help.

…read more
Source: FULL ARTICLE at The UNIX and Linux Forums

Linux

GlusterFS: First impressions

Leave a comment

Recently I fooled around with GlusterFS, a distributed file system especially intended for use as backend storage. The first impression is quite good – as long as you use it for the right task.

Background

GlusterFS is a distributed file system which is supposed to scale to large storage sizes. Besides file distribution it also offers “RAID” like features: if you have two GlusterFS servers you can either stripe the data on both of them, or mirror them. Or, if you got more servers, you can even create more complex setups with a mixture of striping and mirroring. The client protocol is very similar to NFS, and thus clients can GlusterFS servers via GlusterFS-Fuse or directly via NFS.

The advantage of a distributed file system is obvious: if one server goes down, the clients fail over to another server, and you still have the data. Also, you can add more servers in case you need more storage. A distinct advantage of GlusterFS compared to for example AFS or Ceph is that you do not need to worry about setting up special servers dedicated to processes like addressing the data. Each GlusterFS server has the same rights and tasks as the next (in simple setups, highly complex setups may vary.

Competition

GlusterFS faces competition first of all in its own field: distributed file systems as mentioned above (Ceph, AFS, etc.). But for simpler setups you can also create similar results with a shared block level device like DRBD and and NFS or even cluster file systems like GFS and OCFS. And in the end GlusterFS steps up to fight against high cost storage systems (SAN, …).

The Setup

For my tests of GlusterFS I used a couple of CentOS 6 VMs in KVM on my main machine. I followed the well written GlusterFS-CentOS-Howto by falco. However, one thing which is probably not outlined enough in the howto: GlusterFS really depends on host name resolution. And really depending means that an entry in /etc/hosts on the GlusterFS machines is not enough. You should have a working DNS!

That said, the easiest way to accomplish this with a running KVM test setup is to just add the necessary entries to /etc/hosts on the host side (!). These information are forwarded to the VM guests and provide a reliable name resolution.

Tests and Results

I run a couple of tests: shutting down a server, shutting down the interfaces, shutting down the GlusterFS services, etc. The data on the machines were a couple of various text files, nothing fancy.

And all in all, I must say I was impressed with the features and capabilities: the setup was reliable, files where automatically distributed, servers started offline where resynced automatically, and so on. The collision detection is pretty neat, it works on file level: even if there occurs a split brain, i/o is only blocked for files which are actually affected. This is – of course and by design – a huge advantage over shared block devices which block the access to the entire …read more
Source: FULL ARTICLE at Planet KDE

Linux

NFS issue with autofs in CentOS 6.3

Leave a comment

By bashily

I am running CentOS 6.3 as a VM on a host which has the same installation. I configured my NFS server and I am guessing it works. I say guessing because I can mount the desired folder with mount command on my client machine. So, when I run:

Code:
mount -t nfs -o vers=3 vm2.domain.com:/nethome /neth

it mounts the folder at “/neth”;however autofs doesn’t do the same and I don’t even get any error!
my auto.master:

Code:
/neth /etc/auto.neth --timeout=60

my auto.neth:

Code:
* -fstype=nfs,rw,soft,nosuid,nfsvers=3 vm2.domain.com:/nethome/&

I should mention that I have local DNS installed and it work with no problem.
any suggestions?

…read more
Source: FULL ARTICLE at The UNIX and Linux Forums

Linux

AIX NFS Shared File System Question

Leave a comment

By filosophizer

NFS server: test6
Exported directory: /recovery6
NFS client: test1
NFS local mount point: /recovery6

A) On the NFS Server machine/system:
1- Mounted a filesystem called /recovery6 (JFS2) ,
2- Starting the NFS Deamons using command startsrc -g nfs.
3- Exporting the /recovery6 filesystem using smitty as below:

Code:
# smitty mknfsexp

Pathname of directory to export [/recovery6]
Anonymous UID [-2]
Public filesystem? no
* Export directory now, system restart or both both
Pathname of alternate exports file []
Allow access by NFS versions []
External name of directory (NFS V4 access only) []
Referral locations (NFS V4 access only) []
Replica locations []
Ensure primary hostname in replica list yes
Allow delegations? no
Scatter none
* Security method 1 [sys,krb5p,krb5i,krb5,dh]
* Mode to export directory read-write
Hostname list. If exported read-mostly []
Hosts & netgroups allowed client access []
Hosts allowed root access []
Security method 2 []
Mode to export directory []

If there were no problems, you should see an "OK".

root@test6:/>cat /etc/exports
/recovery6 -sec=sys:krb5p:krb5i:krb5:dh:none,rw

root@test6:/>cat /etc/xtab
/recovery6 -sec=sys:krb5p:krb5i:krb5:dh:none,rw

root@test6:/>ls -ltra | grep recovery6
drwxrwxrwx 3 root system 256 Feb 18 22:07 recovery6

root@test6:/>showmount -e
export list for test6:
/recovery6 (everyone)

B) On the NFS Client:
1- Creating a directory called /recovery6
2- Starting the NFS Deamons using command startsrc -g nfs.
3- Mounting the /recovery6 filesystem as following:

Code:
mount test6:/recovery6 /recovery6

root@test1:/>df -g

test6:/recovery6 99.00 98.98 1% 7 1% /recovery6

root@test1:/recovery6>ls -ltra > testfileontest1.txt
root@test1:/recovery6>ls -ltra
total 40
drwxr-xr-x 31 root system 4096 Feb 18 12:29 ..
drwxr-xr-x 2 root system 256 Feb 18 15:16 lost+found
-rw-r--r-- 1 root system 3163 Feb 18 16:35 test6.txt
-rw-r--r-- 1 root system 1 Feb 18 17:05 1
-rw-r--r-- 1 nobody nobody 3355 Feb 18 2013 test1.txt
-rw-r--r-- 1 nobody nobody 466 Feb 18 2013 testfileontest1.txt
drwxrwxrwx 3 root ...read more
Source: FULL ARTICLE at The UNIX and Linux Forums

Linux

NFS Performance Issue

Leave a comment

By moshesa

Hi,
I have a conflict.
I have 2 servers: the 1st creates an application logs and the 2nd is an empty server.

I want to export (read-only) from the 1st server by NFS the directory that contains the logs to the 2nd server.

Now, the question is:
If in the 2nd server i’m doing a lot of manipulates and reads of the logs (in the NFS from the 1st server), from which server is it takes the massive resources? (CPU, RAM)

thank you all!

…read more
Source: FULL ARTICLE at The UNIX and Linux Forums

Linux

Program sharing on NFS

Leave a comment

By xstaci

I am not sure is this plausible…

I have a NFS master server on a solaris box (secured by NIS)
And I have a dozen of virtual machines running 32 and 64 bits linux and windows, running different types of servers.

I am not sure is it possible to move most of the programs to the NFS and have symbolic links pointing to the location on the NFS. This way all vm will be able to have the same versions of program for consistency (such as all Win2008R2 will have a symbolic link “shortcut”, or /bin directory in Linux will be replaced by symbolic links pointing to a bin directory on NFS).

…read more
Source: FULL ARTICLE at The UNIX and Linux Forums

Linux

OVM Server for SPARC … Need Your Help Guys !

Leave a comment

By Mack1982

>* I have two SPARC T4-2 servers:
– Oracle Solaris 11.1 Installed.
– Oracle VM Server for SPARC 3.0 software Installed.
– Shared LUN provisioned to both servers from Clariion CX4 storage box (shared LUN to be used for the Live Migration of the VMs).
– Oracle VM Agent 3.2.1 for SPARC installed.

* Oracle Linux and Oracle VM Manager 3.2.1 installed on Oracle X6220 server.
– the T4-2 SPARC servers has been discovered and added to a pool using the OVM Manager.

How can i configure the shared LUN that was provisioned from the CX4 storage box to the OVM servers to be as the VMs repo./location and use the Live Migration Feature?
I tried to scan/discover the local disks attached to OVM servers from the Manager GUI but it didn’t drop any thing !

Please advice about the proper configuration apart from using NFS …… if it is not possible to use the SAN …. how we can configure the NFS so !

Source: FULL ARTICLE at The UNIX and Linux Forums

Linux

Upgrade to TL8 failed: bos.net.NFS.client 6.1.8.1 (usr: COMMITTED, root:

1 Comment

By thecobra151

dears

i am trying to upgrade the TL from TL7 to TL8 and i facing this issue AIX6.1

Code:
<>

+-----------------------------------------------------------------------------+
BUILDDATE Verification ...
+-----------------------------------------------------------------------------+
Verifying build dates...
0503-466 installp: The build date requisite check failed for fileset bos.net.nfs.client.
Installed fileset build date is 1043. Selected fileset does not have a build date, but one is required.
0503-466 installp: The build date requisite check failed for fileset bos.net.nfs.client.
Installed fileset build date is 1044. Selected fileset does not have a build date, but one is required.
0503-466 installp: The build date requisite check failed for fileset bos.net.nfs.client.
Installed fileset build date is 1048. Selected fileset does not have a build date, but one is required.
0503-466 installp: The build date requisite check failed for fileset bos.net.nfs.client.
Installed fileset build date is 1141. Selected fileset does not have a build date, but one is required.
0503-466 installp: The build date requisite check failed for fileset bos.net.nfs.client.
Installed fileset build date is 1207. Selected fileset does not have a build date, but one is required.
installp: Installation failed due to BUILDDATE requisite failure.

Code:
lppchk -v
lppchk: The following filesets need to be installed or corrected to bring
the system to a consistent state:
bos.net.nfs.client 6.1.8.1 (usr: COMMITTED, root: not installed)

Source: FULL ARTICLE at The UNIX and Linux Forums