search for: kthr

...st to 4194304 bytes, did move [sender] expand file_list to 8388608 bytes, did move ERROR: out of memory in receive_file_entry rsync error: error allocating core memory buffers (code 22) at util.c(116) ------------------------------ vmstat output: System configuration: lcpu=6 mem=16384MB ent=0.60 kthr memory page faults cpu ----- ----------- ------------------------ ------------ ----------------------- r b avm fre re pi po fr sr cy in sy cs us sy id wa pc ec 3 0 4580615 3986 0 5 0 230 860 0 395 7664 2278 60 29 11 0 0....

I just installed build 41 of Nevada on a SunBlade 1500 with 2GB of ram. I wanted to check out zfs since the delay of S10U2 I really could not wait any longer :) I installed it on my system and created a zpool out of an approximately 40GB disk slice. I then wanted to build a version of thunderbird that contains a local patch that we like. So I download the source tar ball. I try to untar it on the

...18:07:34 2 60 0 38 18:07:39 2 39 0 59 18:07:44 2 50 0 48 18:07:49 2 21 0 77 Average 3 40 0 57 </pre> A lot of system time is eating up the CPU. Using vmstat shows: <pre> kthr memory page disk faults cpu r b w swap free re mf pi po fr de sr s1 s2 s3 s4 in sy cs us sy id 0 0 0 2593264 373392 182 1013 4 0 0 0 0 0 0 0 23 1483 9112 1862 3 9 88 0 0 0 2647980 425032 246 1168 2 0 0 0 0 0 0 0 23 896 23589 2229 4...

Hello, I am running SAMBA 2.0.7.0 on AIX 4.3.3.0 I have a 1 Tera Byte filesystem on AIX made available to NT and MAC. There is heavy IO activity on this filesystem and all of a sudden the NT's and MAC's can't read or write any file on this shared filesystem. Also AIX is running out of memory whenever this happens and files cannot be copied onto the said filesystem even at unix

...8960 0 0 0 0 0 0 0 18 0 0 0 394 123737 891 7 93 0 0 0 60 956872 240748 0 0 0 0 0 0 0 22 0 0 0 397 123310 892 7 93 0 0 0 60 949088 232964 0 0 0 0 0 0 0 27 0 0 0 402 123672 925 7 93 0 1 0 60 943940 227816 0 0 0 0 0 0 0 29 0 0 0 400 121999 916 7 93 0 kthr memory page disk faults cpu r b w swap free re mf pi po fr de sr s0 s1 s1 -- in sy cs us sy id 0 0 60 936860 220736 0 0 0 0 0 0 0 22 0 0 0 397 123031 894 7 93 0 0 0 60 928368 212244 0 0 0 0 0 0 0 27 0 0 0 400 123579 934 7...

....857 53880 pollsys .005 603 -------- ------ ---- sys totals: 5.605 485098 30265 usr time: 5.519 elapsed: 61.520 ps:13968 is mysqld process''s pid [root at ssd /data/mysqldata3]#vmstat 1 kthr memory page disk faults cpu r b w swap free re mf pi po fr de sr s1 s2 s3 s5 in sy cs us sy id 0 0 0 575836 1388816 1 18 0 0 0 0 1 3 17 17 17 1226 4185 2008 1 0 99 0 0 0 211652 5620432 21 99 0 0 0 0 0 0 461 470 473 4207 8834 16311 1...

Hi all, I have exchanged my Dell R610 in favor of a Sun Fire 4170 M2 which has 32 GB RAM installed. I am running Sol11Expr on this host and I use it to primarily serve Netatalk AFP shares. From day one, I have noticed that the amount of free RAM decereased and along with that decrease the overall performance of ZFS decreased as well. Now, since I am still quite a Solaris newbie, I seem to

...G 899 154 2.59M 1.45M misc 20.6M 52.0G 0 0 0 0 ---------- ----- ----- ----- ----- ----- ----- f3-1 504G 720G 1.00K 0 4.35M 0 misc 20.6M 52.0G 0 0 0 0 ---------- ----- ----- ----- ----- ----- ----- ^C kthr memory page disk faults cpu r b w swap free re mf pi po fr de sr m0 m1 m2 m1 in sy cs us sy id 0 0 0 8266008 1100560 0 0 0 0 0 0 0 0 0 0 0 2392 589 9592 0 21 79 1 0 0 8266008 1100560 0 0 0 0 0 0 0 0 0 0 0 3909 1458 13330 0...

...c3t3d0 - - 0 60 0 7.56M mirror 39.9G 424G 0 59 0 7.43M c3t4d0 - - 0 59 0 7.43M c3t5d0 - - 0 59 0 7.43M ---------- ----- ----- ----- ----- ----- ----- some data from vmstat as well: kthr memory page disk faults cpu r b w swap free re mf pi po fr de sr cd cd f0 s0 in sy cs us sy id 0 0 0 22436700 13658804 7 2 0 0 0 0 0 0 0 20 1 527 1037 312 0 0 100 0 0 0 13341124 4574844 25 69 0 0 0 0 0 0 0 0 0 1844 149575 2155...

Joseph Little wrote: > I''d love to "vote" to have this addressed, but apparently votes for > bugs are no available to outsiders. > > What''s limiting Stanford EE''s move to using ZFS entirely for our > snapshoting filesystems and multi-tier storage is the inability to > access .zfs directories and snapshots in particular on NFSv3 clients.