I have a machine A NFS mounted on machine B
I am doing a build from machine B on the MFS mounted dir of machine A but I keep getting the following:
NFS server A not responding still trying.
I go to machine A and can log onto machine A and everything seems fine.
How do I go about finding... (6 Replies)
Hi,
I've got a really old system we use for call logging. The OS is SCO 3.2
uname -a output
SCO_SV bts7053 3.2 2 i386
the problem we are having is that its no longer doing its backups. The original problem was the tape drive, which has been replaced twice now. Because the company are... (1 Reply)
Ok, so I have an nfs mount setup and within it there are symbolic links to other directories and such.
So anyways I created a link to a directory like so
ln -s /var/stuff/more/stuff/here/ stuff/
and i ended up with directory stuff with link 'here' inside.
so i was pieved and decided... (1 Reply)
I am having a really bad day today.
I am trying to get an nfs mount to work. I want to have a mount from machinea:/home going to /home on machineb. I can mount machinea:/home on any mount point EXCEPT /home and see the files. I can not see the files or list the directory (it hangs) when I mount... (17 Replies)
I am trying to set up an OpenSolaris box to be an NFS server.
The OpenSolaris version is 2008.11.
The kernel (uname -a output) is: SunOS minime-28 5.11 snv_101b i86pc i386 i86pc
It is running ZFS but I know nothing about ZFS.
I have an entry in the /etc/dfs/dfstab file:
share -F... (1 Reply)
Hi everybody!
I have a very big problem, I can not make any updates on my debian lenny.
I get everytime this errors with apt-get update:
Err http://security.debian.org lenny/updates Release.gpg
Connection failed
Err http://www.backports.org lenny-backports Release.gpg
Connection... (2 Replies)
Hi,
I have two machines (AIX) each on a different VLAN.
Need to mount a filesystem using nfs on the other one.
When I export the nfs file system its a breeze. But when I try to mount it on the other machine the smitty command hangs on "running" and i get an OK from smitty but with this... (6 Replies)
Hi All,
I hoping someone can help me get my NFS working properly. I don't know why I'm having little issues... Overall, NFS is working, therefore, the problem may not be with NFS. I can ssh to remote nodes and view NFS shared directories (/home). Here is the problem, when on a node and I open a... (2 Replies)
Hi all,
i have some doubts in a situation that i fail to get an answer in Google.
I have a solaris 10 nfs server and 5 centos 6.0 nfs clients.
The problem/situation is that in the clients the free memory is "disappearing" along the time (passing to used)..and it gets free if i umount the... (5 Replies)
Discussion started by: blast
5 Replies
LEARN ABOUT CENTOS
tc-bfifo
PBFIFO(8) Linux PBFIFO(8)NAME
pfifo - Packet limited First In, First Out queue
bfifo - Byte limited First In, First Out queue
SYNOPSIS
tc qdisc ... add pfifo [ limit packets ]
tc qdisc ... add bfifo [ limit bytes ]
DESCRIPTION
The pfifo and bfifo qdiscs are unadorned First In, First Out queues. They are the simplest queues possible and therefore have no overhead.
pfifo constrains the queue size as measured in packets. bfifo does so as measured in bytes.
Like all non-default qdiscs, they maintain statistics. This might be a reason to prefer pfifo or bfifo over the default.
ALGORITHM
A list of packets is maintained, when a packet is enqueued it gets inserted at the tail of a list. When a packet needs to be sent out to
the network, it is taken from the head of the list.
If the list is too long, no further packets are allowed on. This is called 'tail drop'.
PARAMETERS
limit Maximum queue size. Specified in bytes for bfifo, in packets for pfifo. For pfifo, defaults to the interface txqueuelen, as speci-
fied with ifconfig(8) or ip(8). The range for this parameter is [0, UINT32_MAX].
For bfifo, it defaults to the txqueuelen multiplied by the interface MTU. The range for this parameter is [0, UINT32_MAX] bytes.
Note: The link layer header was considered when counting packets length.
OUTPUT
The output of tc -s qdisc ls contains the limit, either in packets or in bytes, and the number of bytes and packets actually sent. An
unsent and dropped packet only appears between braces and is not counted as 'Sent'.
In this example, the queue length is 100 packets, 45894 bytes were sent over 681 packets. No packets were dropped, and as the pfifo queue
does not slow down packets, there were also no overlimits:
# tc -s qdisc ls dev eth0
qdisc pfifo 8001: dev eth0 limit 100p
Sent 45894 bytes 681 pkts (dropped 0, overlimits 0)
If a backlog occurs, this is displayed as well.
SEE ALSO tc(8)AUTHORS
Alexey N. Kuznetsov, <kuznet@ms2.inr.ac.ru>
This manpage maintained by bert hubert <ahu@ds9a.nl>
iproute2 10 January 2002 PBFIFO(8)