On 12 February 2011 c. 05:13:33 Ted Unangst wrote:
> On Fri, Feb 11, 2011 at 5:05 PM, Vadim Zhukov <persg...@gmail.com> wrote:
> > - NTFS causes problems exhausting kernel memory when, for example,
> > running find(1) on Windows folder.
>
> can you run find in a smaller folder a few times, and send the output
> of vmstat -m | grep -i ntfs?
After running find on /win/Users/pers/Documents:
packet tags, temp, NTFS data, NTFS vrun, AGP Memory, DRM
USB, memdesc, temp, NTFS vrun, DRM
USB device, NDP, temp, NTFS data, NTFS vrun, AGP Memory, DRM
NTFS node, NTFS fnode, NTFS data, NTFS vrun, DRM
UVM aobj, USB, USB device, temp, NTFS data, bluetooth, DRM
NTFS mount, NTFS attr, NTFS data, DRM
UVM amap, UVM aobj, USB, crypto data, temp, NTFS data, DRM
VM swap, UVM amap, temp, NTFS mount, DRM
USB, memdesc, temp, NTFS dir, DRM
UVM amap, temp, NTFS hash, DRM
131072 devbuf, VM swap, NTFS data
NTFS mount 2 3K 3K 39322K 2 0 0 512,2048
NTFS node 110 14K 26K 39322K 488 0 0 128
NTFS fnode 110 14K 26K 39322K 488 0 0 128
NTFS dir 105 420K 420K 39322K 122 0 0 4096
NTFS hash 1 16K 16K 39322K 1 0 0 16384
NTFS attr 495 248K 296K 39322K 1210 0 0 512
NTFS data 453 193K 194K 39322K 1029 0 0
16,64,128,256,512,1024,131072
NTFS vrun 86 2K 4K 39322K 364 0 0 16,32,64,128
After this find ran on /win/Users/pers:
packet tags, temp, NTFS data, NTFS vrun, AGP Memory, DRM
USB, memdesc, temp, NTFS vrun, DRM
USB device, NDP, temp, NTFS data, NTFS vrun, AGP Memory, DRM
NTFS node, NTFS fnode, NTFS data, NTFS vrun, DRM
UVM aobj, USB, USB device, temp, NTFS data, bluetooth, DRM
NTFS mount, NTFS attr, NTFS data, DRM
UVM amap, UVM aobj, USB, crypto data, temp, NTFS data, DRM
VM swap, UVM amap, temp, NTFS mount, DRM
USB, memdesc, temp, NTFS dir, DRM
UVM amap, temp, NTFS hash, DRM
131072 devbuf, VM swap, NTFS data
NTFS mount 2 3K 3K 39322K 2 0 0 512,2048
NTFS node 1343 168K 168K 39322K 1721 0 0 128
NTFS fnode 1343 168K 168K 39322K 1721 0 0 128
NTFS dir 1339 5356K 5356K 39322K 1356 0 0 4096
NTFS hash 1 16K 16K 39322K 1 0 0 16384
NTFS attr 5368 2684K 2684K 39322K 6083 0 0 512
NTFS data 5084 913K 913K 39322K 5660 0 0
16,64,128,256,512,1024,131072
NTFS vrun 570 12K 12K 39322K 848 0 0 16,32,64,128
And after running on /win/Users:
packet tags, temp, NTFS data, NTFS vrun, AGP Memory, DRM
USB, memdesc, temp, NTFS vrun, DRM
USB device, NDP, temp, NTFS data, NTFS vrun, AGP Memory, DRM
NTFS node, NTFS fnode, NTFS data, NTFS vrun, DRM
UVM aobj, USB, USB device, temp, NTFS data, bluetooth, DRM
NTFS mount, NTFS attr, NTFS data, DRM
UVM amap, UVM aobj, USB, crypto data, temp, NTFS data, DRM
VM swap, UVM amap, temp, NTFS mount, DRM
USB, memdesc, temp, NTFS dir, DRM
UVM amap, temp, NTFS hash, DRM
131072 devbuf, VM swap, NTFS data
NTFS mount 2 3K 3K 39322K 2 0 0 512,2048
NTFS node 1552 194K 194K 39322K 1930 0 0 128
NTFS fnode 1552 194K 194K 39322K 1930 0 0 128
NTFS dir 1549 6196K 6196K 39322K 1566 0 0 4096
NTFS hash 1 16K 16K 39322K 1 0 0 16384
NTFS attr 6272 3136K 3136K 39322K 6987 0 0 512
NTFS data 5952 1039K 1039K 39322K 6528 0 0
16,64,128,256,512,1024,131072
NTFS vrun 642 13K 13K 39322K 920 0 0 16,32,64,128
If I rerun find on previously searched folder it ends it work almost
immediately - caching? - and there is no difference in vmstat output.
--
Best wishes,
Vadim Zhukov
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
