Sponsored Content
Operating Systems AIX I/O speed to CIFS mounted Windows Share Post 302592350 by Corona688 on Monday 23rd of January 2012 03:08:34 PM
Old 01-23-2012
Code:
$ ethtool -S lan
NIC statistics:
     tx_bytes: 21380238224
     tx_zero_rexmt: 22949902
     tx_one_rexmt: 0
     tx_many_rexmt: 0
     tx_late_collision: 0
     tx_fifo_errors: 0
     tx_carrier_errors: 0
     tx_excess_deferral: 0
     tx_retry_error: 0
     rx_frame_error: 0
     rx_extra_byte: 0
     rx_late_collision: 0
     rx_runt: 0
     rx_frame_too_long: 0
     rx_over_errors: 2
     rx_crc_errors: 809
     rx_frame_align_error: 0
     rx_length_error: 0
     rx_unicast: 80133796
     rx_multicast: 70099
     rx_broadcast: 922636
     rx_packets: 81126531
     rx_errors_total: 811
     tx_errors_total: 0
     tx_deferral: 0
     tx_packets: 22949902
     rx_bytes: 100320558664
     tx_pause: 0
     rx_pause: 0
     rx_drop_frame: 59
     tx_unicast: 6062140
     tx_multicast: 2204304
     tx_broadcast: 16550392661358
$

I custom-renamed my network card to lan with a udev rule, yours would likely show up as eth1 or similar. I think rx_pause was very very high due to the cheating switch. If your laptop doesn't have a gigabit ethernet port, you won't see it at all.

Of course, this being switched traffic, you may not see any of that unless the traffic is between the linux machine and the AIX host, rather than between different hosts..

Last edited by Corona688; 01-23-2012 at 04:25 PM..
 

10 More Discussions You Might Find Interesting

1. Solaris

Mounting CIFS share

Is it possible to mount a samba share on a solaris system? I know this is possible with Linux using a fstype of smbfs. I am trying to aviod having to share the same directories via cifs and nfs on a solaris box to windows and solaris clients. (3 Replies)
Discussion started by: mhm4
3 Replies

2. AIX

share with cifs

Im trying to share a directory with cifs my aix box with a windows server. but when I try to mount mount -v cifs -n 172.19.90.240/suc_user/tommy /directory /directory1/directory1 I got this error There was an error connecting the share or the server. Make sure the lsdev command shows that... (1 Reply)
Discussion started by: lo-lp-kl
1 Replies

3. UNIX for Advanced & Expert Users

Ownership problem using a CIFS-mounted volume

Hello, I am trying to use a storage service for backing large amounts (terabytes) of data. The service uses Linux machines and allows mounting of their disks using the CIFS/SMB protocol. I do have the option of using rsync directly over the network without mounting. But in order to... (4 Replies)
Discussion started by: same1290
4 Replies

4. Shell Programming and Scripting

Script to copy User home folders to mounted windows share

First of all, let me state that I am a windows admin. I have a windows share mounted to /mnt/server I need a script that will either login as sudo or perform commands with sudo rights. I need the script to copy all of the users /home folders to the mounted windows share. Now If I can... (7 Replies)
Discussion started by: EricM
7 Replies

5. HP-UX

user can't write on cifs share but OK with Windows Explorer

Share ServerA ==== The Samba server is running on Samba version 3.0.22 based HP CIFS Server A.02.03.04 /opt/cifsclient/sbin/cifsclientd version: HP CIFS Client - Version A.02.02.02 smb file: My previous casw was thew user wasn't able to write to the share from Windows... (1 Reply)
Discussion started by: lamoul
1 Replies

6. AIX

AIX cifs: mount Windows Server 2008 share ?

Hello, I've been using AIX cifs to mount windows XP shares with no problems till now. Now it's Windows Server 2008 R2 - no go: mount -v cifs -n host1/user1/pass1 /share1 /mountpt1 There was an error connecting the share or the server. Make sure the lsdev command shows that device nsmb0 is in... (6 Replies)
Discussion started by: vilius
6 Replies

7. Solaris

Can't connect to CIFS share

Hello guys, as of recently I'm unable to connect to one of my CIFS shares and I've no clue why that may be. As you can see in the first attachment a connection attempt to tony prompts for user credentials but when I try to connect to Videos it claims not being able to find the resource which is... (1 Reply)
Discussion started by: Tony~
1 Replies

8. AIX

CIFS share re-export NFS

Hi Guys, need help here. i have windows server that share a folder C:/ABCDE i configure samba client in AIX server as /EDCBA and it working fine. then i want to share this /EDCBA to another AIX server using NFS. in the /etc/exportfs i have put /EDCBA... (1 Reply)
Discussion started by: prossits
1 Replies

9. Shell Programming and Scripting

Directory / File changes on CIFS share mounted on Red Hat Linux

I have a requirement to copy the changed file on CIFS share mounted on Red Hat Linux to a remote FTP/SFTP server. I tried inotify-tools, but this didn't track the modified files. Has anyone tried incron or any other suggestion? (1 Reply)
Discussion started by: SupeAlok
1 Replies

10. Windows & DOS: Issues & Discussions

Unable to access the CIFS share folder on windows by IP

Hi All Actually I have NAS Storage and Suddenly I got problem Unable to access the CIFS share folder on windows host, however the IP is pinging and the share is accessible via share name. The share can be accessed via share name only on Windows higher Windows Versions. Any help guys (4 Replies)
Discussion started by: Abu_SM
4 Replies
GETIFADDRS(3)						     Linux Programmer's Manual						     GETIFADDRS(3)

NAME
getifaddrs, freeifaddrs - get interface addresses SYNOPSIS
#include <sys/types.h> #include <ifaddrs.h> int getifaddrs(struct ifaddrs **ifap); void freeifaddrs(struct ifaddrs *ifa); DESCRIPTION
The getifaddrs() function creates a linked list of structures describing the network interfaces of the local system, and stores the address of the first item of the list in *ifap. The list consists of ifaddrs structures, defined as follows: struct ifaddrs { struct ifaddrs *ifa_next; /* Next item in list */ char *ifa_name; /* Name of interface */ unsigned int ifa_flags; /* Flags from SIOCGIFFLAGS */ struct sockaddr *ifa_addr; /* Address of interface */ struct sockaddr *ifa_netmask; /* Netmask of interface */ union { struct sockaddr *ifu_broadaddr; /* Broadcast address of interface */ struct sockaddr *ifu_dstaddr; /* Point-to-point destination address */ } ifa_ifu; #define ifa_broadaddr ifa_ifu.ifu_broadaddr #define ifa_dstaddr ifa_ifu.ifu_dstaddr void *ifa_data; /* Address-specific data */ }; The ifa_next field contains a pointer to the next structure on the list, or NULL if this is the last item of the list. The ifa_name points to the null-terminated interface name. The ifa_flags field contains the interface flags, as returned by the SIOCGIFFLAGS ioctl(2) operation (see netdevice(7) for a list of these flags). The ifa_addr field points to a structure containing the interface address. (The sa_family subfield should be consulted to determine the format of the address structure.) This field may contain a null pointer. The ifa_netmask field points to a structure containing the netmask associated with ifa_addr, if applicable for the address family. This field may contain a null pointer. Depending on whether the bit IFF_BROADCAST or IFF_POINTOPOINT is set in ifa_flags (only one can be set at a time), either ifa_broadaddr will contain the broadcast address associated with ifa_addr (if applicable for the address family) or ifa_dstaddr will contain the destina- tion address of the point-to-point interface. The ifa_data field points to a buffer containing address-family-specific data; this field may be NULL if there is no such data for this interface. The data returned by getifaddrs() is dynamically allocated and should be freed using freeifaddrs() when no longer needed. RETURN VALUE
On success, getifaddrs() returns zero; on error, -1 is returned, and errno is set appropriately. ERRORS
getifaddrs() may fail and set errno for any of the errors specified for socket(2), bind(2), getsockname(2), recvmsg(2), sendto(2), mal- loc(3), or realloc(3). VERSIONS
The getifaddrs() function first appeared in glibc 2.3, but before glibc 2.3.3, the implementation supported only IPv4 addresses; IPv6 sup- port was added in glibc 2.3.3. Support of address families other than IPv4 is available only on kernels that support netlink. ATTRIBUTES
For an explanation of the terms used in this section, see attributes(7). +----------------------------+---------------+---------+ |Interface | Attribute | Value | +----------------------------+---------------+---------+ |getifaddrs(), freeifaddrs() | Thread safety | MT-Safe | +----------------------------+---------------+---------+ CONFORMING TO
Not in POSIX.1. This function first appeared in BSDi and is present on the BSD systems, but with slightly different semantics documented-- returning one entry per interface, not per address. This means ifa_addr and other fields can actually be NULL if the interface has no address, and no link-level address is returned if the interface has an IP address assigned. Also, the way of choosing either ifa_broadaddr or ifa_dstaddr differs on various systems. NOTES
The addresses returned on Linux will usually be the IPv4 and IPv6 addresses assigned to the interface, but also one AF_PACKET address per interface containing lower-level details about the interface and its physical layer. In this case, the ifa_data field may contain a pointer to a struct rtnl_link_stats, defined in <linux/if_link.h> (in Linux 2.4 and earlier, struct net_device_stats, defined in <linux/netdevice.h>), which contains various interface attributes and statistics. EXAMPLE
The program below demonstrates the use of getifaddrs(), freeifaddrs(), and getnameinfo(3). Here is what we see when running this program on one system: $ ./a.out lo AF_PACKET (17) tx_packets = 524; rx_packets = 524 tx_bytes = 38788; rx_bytes = 38788 wlp3s0 AF_PACKET (17) tx_packets = 108391; rx_packets = 130245 tx_bytes = 30420659; rx_bytes = 94230014 em1 AF_PACKET (17) tx_packets = 0; rx_packets = 0 tx_bytes = 0; rx_bytes = 0 lo AF_INET (2) address: <127.0.0.1> wlp3s0 AF_INET (2) address: <192.168.235.137> lo AF_INET6 (10) address: <::1> wlp3s0 AF_INET6 (10) address: <fe80::7ee9:d3ff:fef5:1a91%wlp3s0> Program source #define _GNU_SOURCE /* To get defns of NI_MAXSERV and NI_MAXHOST */ #include <arpa/inet.h> #include <sys/socket.h> #include <netdb.h> #include <ifaddrs.h> #include <stdio.h> #include <stdlib.h> #include <unistd.h> #include <linux/if_link.h> int main(int argc, char *argv[]) { struct ifaddrs *ifaddr, *ifa; int family, s, n; char host[NI_MAXHOST]; if (getifaddrs(&ifaddr) == -1) { perror("getifaddrs"); exit(EXIT_FAILURE); } /* Walk through linked list, maintaining head pointer so we can free list later */ for (ifa = ifaddr, n = 0; ifa != NULL; ifa = ifa->ifa_next, n++) { if (ifa->ifa_addr == NULL) continue; family = ifa->ifa_addr->sa_family; /* Display interface name and family (including symbolic form of the latter for the common families) */ printf("%-8s %s (%d) ", ifa->ifa_name, (family == AF_PACKET) ? "AF_PACKET" : (family == AF_INET) ? "AF_INET" : (family == AF_INET6) ? "AF_INET6" : "???", family); /* For an AF_INET* interface address, display the address */ if (family == AF_INET || family == AF_INET6) { s = getnameinfo(ifa->ifa_addr, (family == AF_INET) ? sizeof(struct sockaddr_in) : sizeof(struct sockaddr_in6), host, NI_MAXHOST, NULL, 0, NI_NUMERICHOST); if (s != 0) { printf("getnameinfo() failed: %s ", gai_strerror(s)); exit(EXIT_FAILURE); } printf(" address: <%s> ", host); } else if (family == AF_PACKET && ifa->ifa_data != NULL) { struct rtnl_link_stats *stats = ifa->ifa_data; printf(" tx_packets = %10u; rx_packets = %10u " " tx_bytes = %10u; rx_bytes = %10u ", stats->tx_packets, stats->rx_packets, stats->tx_bytes, stats->rx_bytes); } } freeifaddrs(ifaddr); exit(EXIT_SUCCESS); } SEE ALSO
bind(2), getsockname(2), socket(2), packet(7), ifconfig(8) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. GNU
2017-09-15 GETIFADDRS(3)
All times are GMT -4. The time now is 09:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy