server:zfs_issues
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| server:zfs_issues [2012/05/04 23:13] – created ashley | server:zfs_issues [2012/10/30 12:42] (current) – ashley | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| $ sysctl vfs.numvnodes vfs.zfs | $ sysctl vfs.numvnodes vfs.zfs | ||
| $ sysctl kern | grep kmem | $ sysctl kern | grep kmem | ||
| + | ===== input output stats ===== | ||
| + | gstat | ||
| + | |||
| + | |||
| + | All the arc stats can be retrieve via sysctl... | ||
| + | e.g. sysctl kstat.zfs.misc.arcstats | ||
| + | |||
| + | |||
| + | |||
| + | ===== Memory Tweak Oct2012 ===== | ||
| + | 2gb set 9:39 24/10 Uptime; | ||
| + | ater rebuild, 4Gb set on 28/10 9am | ||
| + | 2gb set in vm 12pm 30/10 | ||
| + | |||
| + | |||
| + | ===== ZFS Logging ===== | ||
| + | |||
| + | have an issue where ZFS consumes all available memory as a result of that same periodic 100.chksetuid script running. It normally grinds the machine to a halt but I think I've also had a panic. | ||
| + | |||
| + | Could you set up a log of the zfs sysctls like: | ||
| + | Code: | ||
| + | |||
| + | export ZFSLOG=/ | ||
| + | |||
| + | and see what the vfs.zfs.arc_meta_used is before it crashes? | ||
| + | |||
| + | ===== ZFS Posts ===== | ||
| + | http:// | ||
| + | |||
| + | ===== Freebsd Kernel debugging ===== | ||
| + | |||
| + | http:// | ||
server/zfs_issues.1336173184.txt.gz · Last modified: (external edit)
