Failed To Save Mount Nfs Error - Mount.nfs Input/output Error
Contents |
HCL Search Reviews Search ISOs Go to Page... LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie [SOLVED] mount nfs problem: mount(2) mount.nfs: mount(2): input/output error mount.nfs: mount system call failed Input/Output error, virtual box involved User Name Remember Me? Password Linux -
Mount Windows Nfs Share On Linux Input Output Error
Newbie This Linux forum is for members that are new to Linux. Just starting out and have a
Rpc: Failed To Contact Portmap
question? If it is not in the man pages or the how-to's this is the place! Notices Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing
Input/output Error Nfs
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. Are you mount nolock example new to LinuxQuestions.org? Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now 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. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Click Here to receive this Complete Guide absolutely
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing nfs input output error windows Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom ls: reading directory .: input/output error nfs Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 ls reading directory input output error in linux Português Español USA Site: Veritas Veritas PartnerNet An error occurs while mounting nfs share in SRD mode for RHEL 5.7 Article:000014713 Publish: Article URL:http://www.veritas.com/docs/000014713 Support http://www.linuxquestions.org/questions/linux-newbie-8/mount-nfs-problem-mount-2-input-output-error-virtual-box-involved-788435/ / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions https://www.veritas.com/support/en_US/article.000014713 Problem While mounting nfs share in Symantec Recovery Disk (SRD) mode for RHEL 5.7, the following error occurs: mount: Mounting [machineip]:/mnt/nfs on /mnt/nfs failed : Input/output error Error Message mount: Mounting [machineip]:/mnt/nfs on /mnt/nfs failed : Input/output error Cause By default, in RHEL 5.7 recovery disk environment, the rpc.statd that is required by NFS for remote locking may not be running. In this situation, do local locking using the -o nolock option to connect to NFS share for accessing the recovery points. Solution Run the mount command with the “-o nolock” option using the following syntax: #mount -t nfs -o nolock [MachineIP]:/mnt/nfs /tmp/nfsApplies ToRed Hat Enterprise Linux 5.7 Terms of use for this information are found in Legal Notices.
Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to th[x] | Forgot Password Login: [x] First Last Prev Next This issue is not in your last search results. Issue36634 - [NFS] General input/output error opening file on NFS mount https://bz.apache.org/ooo/show_bug.cgi?id=36634 Summary: [NFS] General input/output error opening file on NFS mount Status: CLOSED DUPLICATE of https://linuxconfig.org/how-to-configure-nfs-on-linux issue 53682 Product: General Classification: Code Component: ui Version: 680m58 Hardware: PC Linux, all Importance: P2 Trivial with 13 votes (vote) TargetMilestone: --- Assigned To: thorsten.martens QA Contact: issues@framework URL: Keywords: needmoreinfo, oooqa Depends on: Blocks: Show dependency tree /graph Reported: 2004-11-04 05:02 UTC by gordonke Modified: 2005-10-20 00:32 UTC (History) CC List: 7 output error users (show) caolanm daniel.kasak flibby05 genstef issues openoffice-bugs richlv See Also: Issue Type: DEFECT Latest Confirmation in: --- Developer Difficulty: --- Attachments Add an attachment (proposed patch, testcase, etc.) Note You need to log in before you can comment on or make changes to this issue. Description gordonke 2004-11-04 05:02:26 UTC Every time I try to open a file on an NFS automount I get "General input/output error while accessing filename". input output error NFS server is another linux box. This happens for both word processor and spreadsheet. The same files copied to a local directory open fine. Comment 1 michael.ruess 2004-11-04 06:52:25 UTC Framework issue. Comment 2 michael.ruess 2004-11-04 06:53:33 UTC . Comment 3 thackert 2004-12-12 16:59:49 UTC Have you tried this with a newer version of OOo (1.9.60 or 1.9.62 or some cws builds)? Does it occur there also? If not: Could this issue be closed then? Comment 4 hpollak 2004-12-17 07:12:45 UTC I have the same problem allso under 1.9.65. This is a very big trouble for me, cause I use a server share for exchange with other users, working on the same doc. Comment 5 ibmail 2005-01-14 03:10:47 UTC I have the same issue using 1.9.69. However, 1.1.0 works well with NFS. Comment 6 gordonke 2005-02-15 22:40:16 UTC Retested under 1.9.77 and there has been some improvement. Documents are now successfully opened Read Only. Attempts to save a document (File, Save As) to an NFS share create a 0 byte file and the message: Error saving the document
Us How to configure NFS on Linux Contents[Hide]IntroductionScenarioPrerequisitesServer export fileMost common exports optionsEdit exports fileRestart NFS daemonMount remote file system on clientConfigure automountConclusionAppendix ATurn off firewall on Redhat like systems:Add iptables rules to allow NFS communication 1.Introduction The Network File System is certainly one of the most widely used network services. Network file system (NFS) is based on the Remote procedure call which allows the client to automatically mount remote file systems and therefore transparently provide an access to it as if the file system is local. 2.Scenario In this scenario we are going to export the file system from the an IP address 10.1.1.50 ( NFS server ) host and mount it on an a host with an IP address 10.1.1.55 ( NFS Client ). Both NFS server and NFS client will be running Ubuntu Linux. 3.Prerequisites At this point, we assume that the NFS service daemon is already installed on your system, including portmap daemon on which NFS setup depends. If you have not done so yet simply install nfs-common package on both NFS client and NFS server using using apt-get tool. # apt-get install nfs-common The command above will fetch and install all support files common to NFS client and NFS server including portmap. Additionally we need to install extra package on our NFS server side. apt-get install nfs-kernel-server This package is the actual NFS daemon listenning on both UDP and TCP 2049 ports. Execute rpcinfo -p to check correctness of your NFS installation and to actually confirm that NFS server is indeed running and accepting calls on a port 2049: # rpcinfo -p | grep nfs 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 4 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs Furthermore, before we start exporting and mounting NFS directories, your system needs to actually support network file system. To check whether your system supports NFS grep /proc/filesystems and search for nfs. # cat /proc/filesystems | grep nfs nodev nfs nodev nfs4 If you do not see any output it means that NFS is not supported or the NFS module have not been loaded into your kernel. To load NFS module execute: # modprobe nfs When installed correctly, the NFS daemon should be now listening on both UDP and TCP 2049 port and portmap should be waiting for instructions on a port 111. At this point you should have portmap listening on both NFS server and NFS client: rpcinfo -p | grep portmap 100000 2 tcp 111 portmapper 100000 2 udp 111 portmap