Sponsored Content
Full Discussion: NFS + usb2 in FreeBSD6
Special Forums Hardware Filesystems, Disks and Memory NFS + usb2 in FreeBSD6 Post 302201896 by ramen_noodle on Tuesday 3rd of June 2008 11:08:05 AM
Old 06-03-2008
NFS + usb2 in FreeBSD6

I'm encountering some minor difficulties using a home brewed storage system for backups and some content storage.

The backup server is FreeBSD 6 with a seagate external usb drive attached. The drive is nfs shared and linux clients access it via nfs v3.
The symptoms I'm seeing are that the usb drive seems to wind down after every transaction and needs
> 1 second to spin and seek after i/o. This is bothersome because the operation copying blocks..and if a browser this will stall the entire application.
Any quick insight into this issue?
 

8 More Discussions You Might Find Interesting

1. BSD

Unable to use 'su' command on FreeBSD6.2

Hi, I'm unable to do 'su' on my FreeBSD6.2 machine, I can remote ssh login as root but 'su' simply doesn't work at all. The message I get says that "The Operation Not Permitted". Requesting any help. Thanks in advance. (3 Replies)
Discussion started by: Praveen_218
3 Replies

2. Solaris

NFS write error on host : Stale NFS file handle

:confused:Hi all When i see in the /var/adm/messages, i saw the following error unix: NFS write error on host : Stale NFS file handle. unix: (file handle: 45ca415 3e7 a0000 2c7f6 3ebfc25f a0000 2 3e49) It is using sunOS 5.7. Is anybody know what is this error? Is is related to any network... (2 Replies)
Discussion started by: AirWalker83
2 Replies

3. Solaris

All dependicies of nfs service is online but nfs is offline

Hi all in my server all nfs dependices are online but nfs client is offline root@BIWAPP1 # svcs -a|grep nfs disabled Sep_05 svc:/network/nfs/server:default online Sep_05 svc:/network/nfs/rquota:default online Sep_05 svc:/network/nfs/mapid:default online ... (9 Replies)
Discussion started by: spandhan
9 Replies

4. Solaris

Solaris 9 as a nfs client -- centos as a nfs server.

Hello, I have a centos as nfs server, its name is centos_A. After I finish the setup of the nfs server, the other linux can access this nfs server immediately via /net/centos_A/* But, My solaris 9 can not access /net/centos_A/* immediately. I have to leave /net/centos_A, and wait for about... (1 Reply)
Discussion started by: bruceharbin
1 Replies

5. Solaris

Window NFS VS Solaris NFS

Hi all, currently i wish to build a NFS server (windows based), is it the I/O speed will slower than the NFS server in Solaris? any impact, i using the NFS in windows? (2 Replies)
Discussion started by: SmartAntz
2 Replies

6. AIX

AIX NFS Server and NFS Client

Hi 2 ALL, try to run NFS Server in AIX 7.1 : 1. Step by step on NFS Server node mkdir /tmp/test chgrp staff /tmp/test chmod 775 /tmp/test-- create export directory (fs) mknfsexp -d /tmp/test -t ro exportfs -va show mount -e :/# exportfs -av exports: 1831-187 re-exported /tmp/test... (4 Replies)
Discussion started by: penchev
4 Replies

7. Shell Programming and Scripting

Mount NFS Share On NFS Client via bash script.

I need a help of good people with effective bash script to mount nfs shared, By the way I did the searches, since i haven't found that someone wrote a script like this in the past, I'm sure it will serve more people. The scenario as follow: An NFS Client with Daily CRON , running bash script... (4 Replies)
Discussion started by: Brian.t
4 Replies

8. Solaris

NFS write error on host xyz: Stale NFS file handle - Solaris 10

Oct 13 12:19:15 xyz nfs: NFS write error on host xyz: Stale NFS file handle. Oct 13 12:19:15 xyz nfs: (file handle: 68000000 1bc5492e 20000000 377c5e 1ce9395c 720a6203 40000000 bdfb0400) Oct 13 12:19:15 xyz nfs: NFS write error on host zyz: Stale NFS file handle. Oct 13 12:19:15 xyz nfs: ... (5 Replies)
Discussion started by: psychocandy
5 Replies
STABLERESTART(5)					      BSD File Formats Manual						  STABLERESTART(5)

NAME
nfs-stablerestart -- restart information for the NFSv4 server SYNOPSIS
nfs-stablerestart DESCRIPTION
The nfs-stablerestart file holds information that allows the NFSv4 server to restart without always returning the NFSERR_NOGRACE error, as described in the NFSv4 server specification; see Network File System (NFS) Version 4 Protocol RFC 3530, Section 8.6.3. The first record in the file, as defined by struct nfsf_rec in /usr/include/fs/nfs/nfsrvstate.h, holds the lease duration of the last incar- nation of the server and the number of boot times that follows. Following this are the number of previous boot times listed in the first record. The lease duration is used to set the grace period. The boot times are used to avoid the unlikely occurrence of a boot time being reused, due to a TOD clock going backwards. This record and the previous boot times with this boot time added is re-written at the end of the grace period. The rest of the file are appended records, as defined by struct nfst_rec in /usr/include/fs/nfs/nfsrvstate.h and are used represent one of two things. There are records which indicate that a client successfully acquired state and records that indicate a client's state was revoked. State revoke records indicate that state information for a client was discarded, due to lease expiry and an otherwise conflicting open or lock request being made by a different client. These records can be used to determine if clients might have done either of the edge conditions. If a client might have done either edge condition or this file is empty or corrupted, the server returns NFSERR_NOGRACE for any reclaim request from the client. For correct operation of the server, it must be ensured that the file is written to stable storage by the time a write op with IO_SYNC speci- fied has returned. This might require hardware level caching to be disabled for a local disk drive that holds the file, or similar. FILES
/var/db/nfs-stablerestart NFSv4 stable restart file /var/db/nfs-stablerestart.bak backup copy of the file SEE ALSO
nfsv4(4), nfsd(8) BUGS
If the file is empty, the NFSv4 server has no choice but to return NFSERR_NOGRACE for all reclaim requests. Although correct, this is a highly undesirable occurrence, so the file should not be lost if at all possible. The backup copy of the file is maintained and used by the nfsd(8) to minimize the risk of this occurring. To move the file, you must edit the nfsd sources and recompile it. This was done to discour- age accidental relocation of the file. BSD
April 10, 2011 BSD
All times are GMT -4. The time now is 06:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy