Hello, I've got a real doozie.. We recently implemented a b89 as zfs/nfs/ cifs server. The NFS client is HP-UX (11.23).
What's happening is when our dba edits a file on the nfs mount with vi, it will not save. I removed vi from the mix by doing 'touch /nfs/file1' then 'echo abc > /nfs/file1' and it just sat there while the nfs servers cpu went up to 50% (one full core). This nfsstat is most troubling (I zeroed it and only tried to echo data into a file so this is the numbers for about 2 minutes before I CTRL-C'ed the echo command). Version 3: (11242416 calls) null getattr setattr lookup access readlink 0 0% 5600958 49% 5600895 49% 19 0% 9 0% 0 0% read write create mkdir symlink mknod 0 0% 40494 0% 5 0% 0 0% 0 0% 0 0% remove rmdir rename link readdir readdirplus 3 0% 0 0% 0 0% 0 0% 0 0% 7 0% fsstat fsinfo pathconf commit 12 0% 0 0% 0 0% 14 0% Thats a lot of getattr and setattr! Does anyone have any advice on where I should start to figure out what is going on? truss, dtrace, snoop.. so many choices! Thanks, -Andy _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss