Subject: Re: problem ZFS / NFS from FreeBSD nfsv3 client -- periodic NFS server not resp - msg#00697

List: os.solaris.opensolaris.zfs

Date: Prev Next Index Thread: Prev Next Index

On Sep 25, 2006, at 2:49 PM, Mike Kupfer wrote:

"Chad" == Chad Leigh <-- Shire.Net LLC" <chad@xxxxxxxxx>> writes:

Chad> There seems to be no packet headers or time stamps or anything --
Chad> just a lot of binary data. What am I looking for?

Use "snoop -i <capture_file>" to decode the capture file.

OK, a little snoop help is required.

I ran bgsnoop as follows:

# ./bgsnoop.sh -t a -r -d e1000g0

According to the snoop man page

-t [ r | a | d ] Time-stamp presentation. Time-stamps
are accurate to within 4
microseconds. The default is for
times to be presented in d (delta)
format (the time since receiving the
previous packet). Option a (abso-
lute) gives wall-clock time. Option
r (relative) gives time relative to
the first packet displayed. This can
be used with the -p option to
display time relative to any
selected packet.

so -t a should show wall clock time

But my feed looks like the following and I don't see any "wall clock" time stamps. I need to be able to get some sort of wall-time stamp on this so that I can know where to look in my snoop dump for offending issues...

1 0.00000 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=50E5 (read,lookup,modify,extend,delete,execute)
2 0.00045 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=339B (read,lookup,modify,extend,delete,execute)
3 0.00019 freebsd-internal.shire.net -> bagend-i1 NFS C LOOKUP3 FH=339B 1159219290.M400972P15189_courierlock.freebsd.shire.net
4 0.00019 freebsd-internal.shire.net -> bagend-i1 NFS C LOOKUP3 FH=339B 1159219290.M400972P15189_courierlock.freebsd.shire.net
5 0.00026 freebsd-internal.shire.net -> bagend-i1 NFS C CREATE3 FH=339B (UNCHECKED) 1159219290.M400972P15189_courierlock.freebsd.shire.net
6 0.00045 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=878C (read,lookup,modify,extend,delete,execute)
7 0.00013 freebsd-internal.shire.net -> bagend-i1 NFS C LOOKUP3 FH=50E5 tmp
8 0.00013 freebsd-internal.shire.net -> bagend-i1 NFS C LOOKUP3 FH=339B 1159219290.M400972P15189_courierlock.freebsd.shire.net
9 0.00019 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=878C (read,lookup,modify,extend,delete,execute)
10 0.00026 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=878C (read,lookup,modify,extend,delete,execute)
11 0.00019 freebsd-internal.shire.net -> bagend-i1 NFS C WRITE3 FH=878C at 0 for 24 (ASYNC)
12 0.00026 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=878C (read,lookup,modify,extend,delete,execute)
13 0.00013 freebsd-internal.shire.net -> bagend-i1 NFS C LOOKUP3 FH=339B courier.lock
14 0.00013 freebsd-internal.shire.net -> bagend-i1 NFS C COMMIT3 FH=878C at 0 for 24
15 0.00032 freebsd-internal.shire.net -> bagend-i1 NFS C LINK3 FH=878C to FH=339B courier.lock
16 0.00026 freebsd-internal.shire.net -> bagend-i1 NFS C LOOKUP3 FH=339B 1159219290.M400972P15189_courierlock.freebsd.shire.net
17 0.00019 freebsd-internal.shire.net -> bagend-i1 NFS C REMOVE3 FH=339B 1159219290.M400972P15189_courierlock.freebsd.shire.net
18 0.00032 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=339B (read,lookup,modify,extend,delete,execute)
19 0.00019 freebsd-internal.shire.net -> bagend-i1 NFS C FSSTAT3 FH=50E5
20 0.00019 freebsd-internal.shire.net -> bagend-i1 NFS C READDIR3 FH=339B Cookie=0 for 8192
21 0.00026 freebsd-internal.shire.net -> bagend-i1 NFS C LOOKUP3 FH=339B courier.lock
22 0.00019 freebsd-internal.shire.net -> bagend-i1 NFS C LOOKUP3 FH=339B 1159219290.M405999P15189_imapuid_164.freebsd.shire.net
23 0.00026 freebsd-internal.shire.net -> bagend-i1 NFS C LOOKUP3 FH=339B 1159219290.M405999P15189_imapuid_164.freebsd.shire.net
24 0.00013 freebsd-internal.shire.net -> bagend-i1 NFS C CREATE3 FH=339B (UNCHECKED) 1159219290.M405999P15189_imapuid_164.freebsd.shire.net
25 0.00032 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=868C (read,lookup,modify,extend,delete,execute)
26 0.00013 freebsd-internal.shire.net -> bagend-i1 NFS C LOOKUP3 FH=339B 1159219290.M405999P15189_imapuid_164.freebsd.shire.net
27 0.00013 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=EE81 (read,lookup,modify,extend,delete,execute)
28 0.00013 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=EE81 (read,lookup,modify,extend,delete,execute)
29 0.05840 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=868C (read,lookup,modify,extend,delete,execute)
30 0.00019 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=868C (read,lookup,modify,extend,delete,execute)
31 0.00026 freebsd-internal.shire.net -> bagend-i1 NFS C SETATTR3 FH=868C
32 0.04253 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=87E5 (read,lookup,modify,extend,delete,execute)
33 0.00019 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=87E5 (read,lookup,modify,extend,delete,execute)
34 0.00026 freebsd-internal.shire.net -> bagend-i1 NFS C FSSTAT3 FH=50E5
35 0.09871 freebsd-internal.shire.net -> bagend-i1 TCP D=2049 S=828 Ack=1388080234 Seq=414843977 Len=0 Win=65535 Options=<nop,nop,tstamp 633351866 31062869>
36 0.09588 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=3C9B (read,lookup,modify,extend,delete,execute)
37 0.00026 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=3C9B (read,lookup,modify,extend,delete,execute)
38 0.00026 freebsd-internal.shire.net -> bagend-i1 NFS C FSSTAT3 FH=50E5
39 0.00432 freebsd-internal.shire.net -> bagend-i1 NFS C LOOKUP3 FH=339B 1159219290.M405999P15189_imapuid_164.freebsd.shire.net
40 0.00019 freebsd-internal.shire.net -> bagend-i1 NFS C REMOVE3 FH=339B 1159219290.M405999P15189_imapuid_164.freebsd.shire.net
41 0.00544 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=A6E5 (read,lookup,modify,extend,delete,execute)
42 0.00026 freebsd-internal.shire.net -> bagend-i1 NFS C LOOKUP3 FH=A6E5 :list
43 0.00019 freebsd-internal.shire.net -> bagend-i1 NFS C SETATTR3 FH=A6E5
44 0.00078 freebsd-internal.shire.net -> bagend-i1 NFS C LOOKUP3 FH=50E5 courierimapkeywords
45 0.00019 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=A6E5 (read,lookup,modify,extend,delete,execute)
46 0.00013 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=A6E5 (read,lookup,modify,extend,delete,execute)
47 0.00019 freebsd-internal.shire.net -> bagend-i1 NFS C FSSTAT3 FH=50E5
48 0.02208 freebsd-internal.shire.net -> bagend-i1 NFS C LOOKUP3 FH=A6E5 .3767952.1130327968.H497313P29943.freebsd.shire.net
49 0.00026 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=D4BD (read,lookup,modify,extend,delete,execute)
50 0.00013 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=D4BD (read,lookup,modify,extend,delete,execute)
51 0.00032 freebsd-internal.shire.net -> bagend-i1 NFS C LOOKUP3 FH=A6E5 .3806200.1141843328.H928068P3390.freebsd.shire.net
52 0.00013 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=DABD (read,lookup,modify,extend,delete,execute)
53 0.00013 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=DABD (read,lookup,modify,extend,delete,execute)
54 0.00026 freebsd-internal.shire.net -> bagend-i1 NFS C LOOKUP3 FH=A6E5 .3830089.1149025540.H610574P94084.freebsd.shire.net
55 0.00019 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=CEBD (read,lookup,modify,extend,delete,execute)
56 0.00013 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=CEBD (read,lookup,modify,extend,delete,execute)
57 0.00026 freebsd-internal.shire.net -> bagend-i1 NFS C LOOKUP3 FH=A6E5 .3863990.1159190932.H248287P24183.freebsd.shire.net
58 0.00019 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=6C9F (read,lookup,modify,extend,delete,execute)
59 0.00013 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=6C9F (read,lookup,modify,extend,delete,execute)
60 0.00026 freebsd-internal.shire.net -> bagend-i1 NFS C LOOKUP3 FH=A6E5 .3864038.1159209259.H328539P97232.freebsd.shire.net
61 0.00019 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=5E8F (read,lookup,modify,extend,delete,execute)
62 0.00013 freebsd-internal.shire.net -> bagend-i1 NFS C ACCESS3 FH=5E8F (read,lookup,modify,extend,delete,execute)
63 0.00111 freebsd-internal.shire.net -> bagend-i1 NFS C LOOKUP3 FH=50E5 tmp
64 0.00019 freebsd-internal.shire.net -> bagend-i1 NFS C LOOKUP3 FH=339B courier.lock
65 0.00019 freebsd-internal.shire.net -> bagend-i1 NFS C REMOVE3 FH=339B courier.lock
66 0.09890 freebsd-internal.shire.net -> bagend-i1 TCP D=2049 S=828 Ack=1388085198 Seq=414847545 Len=0 Win=65535 Options=<nop,nop,tstamp 633351971 31062892>
freebsd

cheers,
mike

---
Chad Leigh -- Shire.Net LLC
Your Web App and Email hosting provider
chad at shire.net

smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
zfs-discuss mailing list
zfs-discuss@xxxxxxxxxxxxxxx
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Was this page helpful?

Thread at a glance:

Previous Message by Date: click to view message preview

Good PCI controllers for Nevada?

Just thought I'd share some recent experiences. I had an Adaptec ASH-1233 PCI controller (based on the Silicon Image SII0680ACL144 chip) in my Nevada build 45 system (a white box PC based on the AMD 3200+ CPU). This system is the backup for my main home server. Using zfs send | rsh zfs receive to copy the data, I was only getting about 4MB/sec to a RAIDZ1 pool of 4 X IDE 300GB drives (2 on the internal IDE controller and 2 on the Adaptec). I swapped the Adaptec for the "generic" CompuUSA PCI "ULtra ATA / 133 PCI Card". It's SKU 293595. It's based on the ITE IT8212F. I give you the details because with the same disk, just swapping controllers, I'm now moving on average 34MB/sec. This message posted from opensolaris.org

Next Message by Date: click to view message preview

Re: Re: Re: low disk performance

other example: rsyncing from/to the same zpool: device r/s w/s Mr/s Mw/s wait actv svc_t %w %b c6 25.0 276.5 1.3 3.8 1.9 16.5 61.1 0 135 sd44 6.0 158.3 0.3 0.4 1.9 15.5 106.2 33 [b]100[/b] sd45 6.0 37.1 0.3 1.1 0.0 0.3 6.5 0 10 sd46 8.0 42.1 0.4 1.1 0.0 0.4 7.3 0 15 sd47 5.0 39.1 0.3 1.1 0.0 0.3 7.3 0 10 sd44 is always at 100, performance are really really low .. Using 3 lun or 4 lun in the zpool is the same. any suggest? This message posted from opensolaris.org

Previous Message by Thread: click to view message preview

Re: problem ZFS / NFS from FreeBSD nfsv3 client -- periodic NFS server not resp

>>>>> "Chad" == Chad Leigh <-- Shire.Net LLC" <chad@xxxxxxxxx>> writes: Chad> There seems to be no packet headers or time stamps or anything -- Chad> just a lot of binary data. What am I looking for? Use "snoop -i <capture_file>" to decode the capture file. cheers, mike

Next Message by Thread: click to view message preview

Re: problem ZFS / NFS from FreeBSD nfsv3 client -- periodic NFS server not resp

>>>>> "Chad" == Chad Leigh <-- Shire.Net LLC" <chad@xxxxxxxxx>> writes: Chad> so -t a should show wall clock time The capture file always records absolute time. So you (just) need to use "-t a" when you decode the capture file. Sorry for not making the clear earlier. mike

Loading Comments...