search for: 358m

...7.9G 0 7.9G 0% /dev/shm tmpfs 7.9G 643M 7.3G 9% /run tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup /dev/mapper/prop-root 15G 11G 2.9G 79% / tmpfs 7.9G 12K 7.9G 1% /tmp /dev/mapper/prop-boot 477M 95M 358M 21% /boot /dev/mapper/prop-home 222G 215G 7.6G 97% /home I'll add this info to the bug report. I've got 7.6G left. I think I'll attach a new disk with enough space and copy the contents over so I can keep the system running. I'll hopefully be able to work on the bug soon t...

...t;> tmpfs 7.9G 643M 7.3G 9% /run >> tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup >> /dev/mapper/prop-root 15G 11G 2.9G 79% / >> tmpfs 7.9G 12K 7.9G 1% /tmp >> /dev/mapper/prop-boot 477M 95M 358M 21% /boot >> /dev/mapper/prop-home 222G 215G 7.6G 97% /home >> >> I'll add this info to the bug report. > > Just to be clear, it has multiple virtual block devices, eg. > /dev/vda and /dev/vdb ...? > > This isn't (currently) a supported configuration...

...7.9G 0 7.9G 0% /dev/shm tmpfs 7.9G 3.9M 7.9G 1% /run tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup /dev/mapper/prop-root 15G 7.4G 6.3G 55% / tmpfs 7.9G 0 7.9G 0% /tmp /dev/mapper/prop-boot 477M 95M 358M 21% /boot /dev/mapper/prop-home 222G 212G 9.9G 96% /home The image is the 222G /home partition only. The other partitions are on another image. Any ideas how to troubleshoot this would be greatly appreciated. Thanks, Alex

...7.9G 0 7.9G 0% /dev/shm tmpfs 7.9G 3.9M 7.9G 1% /run tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup /dev/mapper/prop-root 15G 7.4G 6.3G 55% / tmpfs 7.9G 0 7.9G 0% /tmp /dev/mapper/prop-boot 477M 95M 358M 21% /boot /dev/mapper/prop-home 222G 212G 9.9G 96% /home The image is the 222G /home partition only. The other partitions are on another image. Any ideas how to troubleshoot this would be greatly appreciated. Thanks, Alex

...7.9G 0 7.9G 0% /dev/shm tmpfs 7.9G 3.9M 7.9G 1% /run tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup /dev/mapper/prop-root 15G 7.4G 6.3G 55% / tmpfs 7.9G 0 7.9G 0% /tmp /dev/mapper/prop-boot 477M 95M 358M 21% /boot /dev/mapper/prop-home 222G 212G 9.9G 96% /home The image is the 222G /home partition only. The other partitions are on another image. There are a bunch of links regarding other methods for resizing an LVM from within a VM. I don't know which to follow. Can someone make a recomm...

....9G 0% /dev/shm > tmpfs 7.9G 643M 7.3G 9% /run > tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup > /dev/mapper/prop-root 15G 11G 2.9G 79% / > tmpfs 7.9G 12K 7.9G 1% /tmp > /dev/mapper/prop-boot 477M 95M 358M 21% /boot > /dev/mapper/prop-home 222G 215G 7.6G 97% /home > > I'll add this info to the bug report. Just to be clear, it has multiple virtual block devices, eg. /dev/vda and /dev/vdb ...? This isn't (currently) a supported configuration for virt-resize, although it ough...

...0 7.9G 0% /dev/shm > tmpfs 7.9G 3.9M 7.9G 1% /run > tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup > /dev/mapper/prop-root 15G 7.4G 6.3G 55% / > tmpfs 7.9G 0 7.9G 0% /tmp > /dev/mapper/prop-boot 477M 95M 358M 21% /boot > /dev/mapper/prop-home 222G 212G 9.9G 96% /home > > The image is the 222G /home partition only. The other partitions are > on another image. > > Any ideas how to troubleshoot this would be greatly appreciated. > Thanks, > Alex > > ___________________...

...************************************************************************************************ ccn10$ df -lh Filesystem Size Used Avail Use% Mounted on /dev/sda1 1.5G 1.3G 149M 90% / tmpfs 252M 0 252M 0% /dev/shm /dev/sda6 4.2G 3.6G 358M 92% /tmp /dev/sda5 938M 706M 184M 80% /var ccn10$ dmesg | grep DMA DMA zone: 4096 pages, LIFO batch:1 ccn10$ for i in `seq 1 10`; do hdparm -tT /dev/sda1; done Timing cached reads: 516 MB in 2.00 seconds = 257.78 MB/sec Timing buffered disk reads: 62 MB in 3.03 secon...

Hi, >> >> > # virt-resize -d --expand /dev/sda1 --LV-expand /dev/mapper/prop-home >> >> > prop-1.img prop-expand.img >> >> > command line: virt-resize -d --expand /dev/sda1 --LV-expand >> >> > /dev/mapper/prop-home prop-1.img prop-expand.img >> >> > Examining prop-1.img ... >> >> > libguestfs: trace:

...************************************************************************************************ ccn10$ df -lh Filesystem Size Used Avail Use% Mounted on /dev/sda1 1.5G 1.3G 149M 90% / tmpfs 252M 0 252M 0% /dev/shm /dev/sda6 4.2G 3.6G 358M 92% /tmp /dev/sda5 938M 706M 184M 80% /var ccn10$ dmesg | grep DMA DMA zone: 4096 pages, LIFO batch:1 ccn10$ for i in `seq 1 10`; do hdparm -tT /dev/sda1; done Timing cached reads: 516 MB in 2.00 seconds = 257.78 MB/sec Timing buffered disk reads: 62 MB in 3.03 secon...

Following is the output of top command at my server and i find the high usage very much alarming. We are basically a team of three developers working on same machine(remotely), so we run mongrel_rails servers from out ~/public/app directories. We also run a cluster of mongrel servers using apache2.2. Is this much memory use normal? PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+

Hi, I just installed 2009.06 and found that compression isn''t enabled by default when filesystems are created. Does is make sense to have an RFE open for this? (I''ll open one tonight if need be.) We keep telling people to turn on compression. Are there any situations where turning on compression doesn''t make sense, like rpool/swap? what about rpool/dump? Thanks, ~~sa

...build/lib/Target/Hexagon/CMakeFiles 389M build/lib/Transforms/Scalar/CMakeFiles/LLVMScalarOpts.dir 389M build/lib/Transforms/Scalar/CMakeFiles 389M build/lib/Transforms/Scalar 373M build/lib/Target/X86/CMakeFiles/LLVMX86CodeGen.dir 373M build/lib/Target/X86/CMakeFiles 360M build/lib/Target/AArch64 358M build/tools/clang/lib/StaticAnalyzer/Core/CMakeFiles/clangStaticAnalyzerCore.dir 358M build/tools/clang/lib/StaticAnalyzer/Core/CMakeFiles 358M build/tools/clang/lib/StaticAnalyzer/Core 356M build/tools/clang/unittests/Tooling/CMakeFiles/ToolingTests.dir/RecursiveASTVisitorTests 352M build/lib/Targ...