search for: 125g

...9;d > make a separate logical drive/partition, and mount that, rsync everything > from /var/www to that, then shut down the web, and remount the new > filesystem on /var/www. > > Root, itself, doesn't need to be huge. We're using 500G, and seriously > considering making it 125G in the future, with data, or web stuff, is on a > separate partition, so when there's a sudden explosion of data, / is safe. > > mark > Mark, Thanks for your input. Well, we are talking much smaller scale here (only about 30 GB at present, planning to roughly double it)....

Hello all, In your view, what is the most reliable and safe way to increase an LV housing the root filesystem of a Centos 6 VM. I am thinking either growing the virtual HD virtual device, or creating a new device and adding it as a PV to the VM, or perhaps migrating the whole FS to a new virtual disk. Any input on how best to proceed would be appreciated. Cheers, Boris.

...of cluster). Here's some df statments to help clarify: > > (brick1 = engine; brick2=data, brick4=iso): > Filesystem Size Used Avail Use% Mounted on > /dev/mapper/gluster-engine 25G 12G 14G 47% /gluster/brick1 > /dev/mapper/gluster-data 136G 125G 12G 92% /gluster/brick2 > /dev/mapper/gluster-iso 25G 7.3G 18G 29% /gluster/brick4 > 192.168.8.11:/engine 15G 9.7G 5.4G 65% > /rhev/data-center/mnt/glusterSD/192.168.8.11:_engine > 192.168.8.11:/data 136G 125G 12G 92% > /rhev/data-center/m...

...ff under, say, /var/www, I'd make a separate logical drive/partition, and mount that, rsync everything from /var/www to that, then shut down the web, and remount the new filesystem on /var/www. Root, itself, doesn't need to be huge. We're using 500G, and seriously considering making it 125G in the future, with data, or web stuff, is on a separate partition, so when there's a sudden explosion of data, / is safe. mark

...rate logical drive/partition, and mount that, rsync >> everything from /var/www to that, then shut down the web, and >> remount the new filesystem on /var/www. >> >> Root, itself, doesn't need to be huge. We're using 500G, and seriously >> considering making it 125G in the future, with data, or web stuff, is on >> a separate partition, so when there's a sudden explosion of data, / is >> safe. > > Well, we are talking much smaller scale here (only about 30 GB at > present, planning to roughly double it). <snip> Ok, that *is* small...

...owever "xm debug-key D" doesn''t produce any output on the console or xm dmesg. Settings and RAM-worth of different bitness guests that were bootable on a box with 384G of RAM: dom0_mem total_available_memory 32bit 64bit min:3G,max:128G 128 125G 127G -128G 128 65G 128G min:3G,max:-128G 240 65G 239G min:3G,max:160G 150 115G 149G We''re either missing something fundamental about how to configure this, or there''s a bug in b...

...have space. Filesystem Size Used Avail Use% Mounted on /dev/sda2 9.7G 806M 8.4G 9% / /dev/sda1 99M 14M 80M 15% /boot none 2.0G 0 2.0G 0% /dev/shm /dev/sda3 97G 226M 92G 1% /opt /dev/sda6 166G 33G 125G 21% /var -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20070322/32f45db7/attachment.html>

...emcpower2a ONLINE 0 0 0 errors: No known data errors everything is great but I''ve made a mistake and I would like to remove emcpower2a from my pool and I cannot do that... Well the mistake that I made is that I did not format my device correctly so instead of adding 125gig I added 128meg here is my partition on that disk: partition> print Current partition table (original): Total disk cylinders available: 63998 + 2 (reserved cylinders) Part Tag Flag Cylinders Size Blocks 0 root wm 0 - 63 128.00MB (64/...

I just setup a new laptop with - Xen-unstable (http://xenbits.xensource.com/xen-unstable.git), installed via "make xen", "make install-xen", "make tools", "make install-tools" - dom0 kernel 2.6.30-rc6-tip (from git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git, changed to bleeding edge via "git checkout origin/xen-tip/next b xen tip/next

I have a 5-500GB disk Raid-Z pool that has been producing checksum errors right after upgrading SXCE to build 121. They seem to be randomly occurring on all 5 disks, so it doesn''t look like a disk failure situation. Repeatingly running a scrub on the pools randomly repairs between 20 and a few hundred checksum errors. Since I hadn''t physically touched the machine, it seems a

...metaslab 24 offset 60000000000 spacemap 3187 free 11.2G segments 2230 maxsize 9.20G freepct 4% metaslab 25 offset 64000000000 spacemap 3296 free 161G segments 10786 maxsize 125G freepct 62% metaslab 26 offset 68000000000 spacemap 3497 free 20.7G segments 21594 maxsize 2.71G freepct 8% metaslab 27 offset 6c000000000 spacemap 3858 free 104G segments...