search for: 25gb

...em /largedisk with 550784264 blocks. After everything is installed and mounted, I get the following in a df: /dev/sda8 550784264 32828 522773144 1% /largedisk The avail + used != total, not even close. I realize that the 32828 is probably the journal, but where could the other 25GB have gone? Thanks, Stephen

...ng: # free -m total used free shared buffers cached Mem: 32093 23975 8118 0 189 5736 -/+ buffers/cache: 18049 14043 Swap: 4095 22 4073 So the machine has 32GB of RAM, and java process needs 25GB to start. When I make a restart the java process dies and in log: Jul 4 08:17:27 test.local solr: Error occurred during initialization of VM Jul 4 08:17:27 test.local solr: Could not reserve enough space for object heap Jul 4 08:17:27 test.local solr: [FAILED] Then a second restart is ok, the...

Can anyone help make sense of this? This is an ext3 partition. It's only showing 403GB out of 426GB used, but then it says only 632MB available? Where'd the extra ~25GB go? [scarolan at server]$ df -H /disks/vrac5 Filesystem Size Used Avail Use% Mounted on /dev/sdb2 426GB 403GB 632MB 100% /disks/vrac5

...34.2 GB of memory. my R process was killed several times when i tried to use 4GB of data for svm. Now I am using a subset of that data and it is only 1.4 GB. i remove all unnecessary objects before calling svm(). I have monitored the memory consumption and found that before i call svm() my AMI has 25GB of free memory. after calling svm(), this free memory starts going down and at the end i have only 1.7 gb of memory and R gives me error that it can not create vector of size 3.4 gb. Its true that if i do not have enough memory then how R will create the vector. But my question is how svm function...

What do you guys recommend for backing up a small CentOS server in a business environment. It will have (3) 300gb drives in a raid 5 array but I don't anticipate more than about 25gb of data that needs to be backed up each night. I want a lot of backups with a rotation scheme that included daily, weekly, and monthly copies. I want the daily copies of the data kept until the next week, and the weekly copy being kept for four weeks, and the monthly copies being kept for a year....

Hi, we ran a benchmark using btrfs on a server that essentially does the equivalent of the following: Open one large (25GB) test-set file for reading, which consists of many small randomly generated messages. Each message consists of a primary key (an integer in the range of 0 to 1,000,000) and a random number of arbitrary data bytes (length in the range from 10 to 1000 byte). For each message, the server opens the fi...

...~~~~~~~~~~~~~~~~~~~~~ Number of Bricks: 9 Transport-type: tcp Hot Tier : Hot Tier Type : Replicate Number of Bricks: 1 x 3 = 3 Cold Tier: Cold Tier Type : Distributed-Replicate Number of Bricks: 2 x 3 = 6 performance.flush-behind: on performance.cache-max-file-size: 128MB performance.cache-size: 25GB diagnostics.count-fop-hits: off diagnostics.latency-measurement: off cluster.tier-mode: cache features.ctr-enabled: on transport.address-family: inet nfs.disable: on performance.client-io-threads: off ~~~~~~~~~~~~~~~~~~~~~ Without write cache, bricks in hot tier got around 1.5 GB/s write speed an...

Hi Nithya, I'm on Gluster 4.0.1. I don't think the bricks were smaller before - if they were, maybe 20GB because Linode's minimum is 20GB, then I extended them to 25GB, resized with resize2fs as instructed, and rebooted many times over since. Yet, gluster refuses to see the full disk size. Here's the status detail output: gluster volume status dev_apkmirror_data detail Status of volume: dev_apkmirror_data ----------------------------------------------------...

...t 05:17, Artem Russakovskii <archon810 at gmail.com> wrote: > >> Hi Nithya, >> >> I'm on Gluster 4.0.1. >> >> I don't think the bricks were smaller before - if they were, maybe 20GB >> because Linode's minimum is 20GB, then I extended them to 25GB, resized >> with resize2fs as instructed, and rebooted many times over since. Yet, >> gluster refuses to see the full disk size. >> >> Here's the status detail output: >> >> gluster volume status dev_apkmirror_data detail >> Status of volume: dev_apkmir...

Hi, I have a 3-brick replicate volume, but for some reason I can't get it to expand to the size of the bricks. The bricks are 25GB, but even after multiple gluster restarts and remounts, the volume is only about 8GB. I believed I could always extend the bricks (we're using Linode block storage, which allows extending block devices after they're created), and gluster would see the newly available space and extend to us...

...0 0 0.0.0.0:123 0.0.0.0:* 11528/ntpd Is there any way or option that only listen 127.0.0.1 for security reason? Thanks in advacne. _________________________________________________________________ ???? ????! ??? ??? ???? ????! ??? ??! 25GB ???? ?! ???? ??? ?? ?? http://im.msn.co.kr/Univ/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20090612/48f6cbb5/attachment-0001.html>

...re should be 120 outputs in total (10 years each with 12 months), but at present it's only reaching 12 outputs. I'd be grateful to learn what I'm doing wrong here so that I can solve this. Many thanks as ever, Steve _________________________________________________________________ 25GB of FREE Online Storage ? Find out more

...=1541880 On 17 April 2018 at 05:17, Artem Russakovskii <archon810 at gmail.com> wrote: > Hi Nithya, > > I'm on Gluster 4.0.1. > > I don't think the bricks were smaller before - if they were, maybe 20GB > because Linode's minimum is 20GB, then I extended them to 25GB, resized > with resize2fs as instructed, and rebooted many times over since. Yet, > gluster refuses to see the full disk size. > > Here's the status detail output: > > gluster volume status dev_apkmirror_data detail > Status of volume: dev_apkmirror_data > --------------...

...n810 at gmail.com> >> wrote: >> >>> Hi Nithya, >>> >>> I'm on Gluster 4.0.1. >>> >>> I don't think the bricks were smaller before - if they were, maybe 20GB >>> because Linode's minimum is 20GB, then I extended them to 25GB, resized >>> with resize2fs as instructed, and rebooted many times over since. Yet, >>> gluster refuses to see the full disk size. >>> >>> Here's the status detail output: >>> >>> gluster volume status dev_apkmirror_data detail >>>...

...you running? Were the bricks smaller earlier? Regards, Nithya On 15 April 2018 at 00:09, Artem Russakovskii <archon810 at gmail.com> wrote: > Hi, > > I have a 3-brick replicate volume, but for some reason I can't get it to > expand to the size of the bricks. The bricks are 25GB, but even after > multiple gluster restarts and remounts, the volume is only about 8GB. > > I believed I could always extend the bricks (we're using Linode block > storage, which allows extending block devices after they're created), and > gluster would see the newly availabl...

...tcp > > Hot Tier : > Hot Tier Type : Replicate > Number of Bricks: 1 x 3 = 3 > > Cold Tier: > Cold Tier Type : Distributed-Replicate > Number of Bricks: 2 x 3 = 6 > > performance.flush-behind: on > performance.cache-max-file-size: 128MB > performance.cache-size: 25GB > > diagnostics.count-fop-hits: off > diagnostics.latency-measurement: off > cluster.tier-mode: cache > features.ctr-enabled: on > transport.address-family: inet > nfs.disable: on > performance.client-io-threads: off > ~~~~~~~~~~~~~~~~~~~~~ > > Without write cache,...

Hello, I need to automate installation of CentOS 7.0 using PXE and kickstart. My server is diskless, I'm installing CentOS on a 25GB LUN on a FC SAN with 4 paths. This LUN is the only one accessible by the server. Anaconda processes successfully the installation. But on reboot, I get stuck on a prompt after BIOS. I think I have an issue with storage configuration / bootloader configuration... I can install it using the ISO,...

...n810 at gmail.com> >> wrote: >> >>> Hi Nithya, >>> >>> I'm on Gluster 4.0.1. >>> >>> I don't think the bricks were smaller before - if they were, maybe 20GB >>> because Linode's minimum is 20GB, then I extended them to 25GB, resized >>> with resize2fs as instructed, and rebooted many times over since. Yet, >>> gluster refuses to see the full disk size. >>> >>> Here's the status detail output: >>> >>> gluster volume status dev_apkmirror_data detail >>>...

...-2.96.126. Fedora Core 3 doesn't come with it but you can get it from Fedora Core 2. WBEL and CentOS should have it installed by default. 3 - Download the latest version of Oracle Applications from edelivery.oracle.com. Latest release available is 11.5.10 and comes in 46 zip files totalling a 25Gb. It expands to about the same size since there's a lot of compressed files in it. 4 - Create a new group called dba. Create a new user called oracle and assign dba as the primary group. 5 - Log in as oracle and edit the .bash_profile to add the variable LD_ASSUME_KERNEL=2.4.19. Make sure yo...

...t; wrote: >>> >>>> Hi Nithya, >>>> >>>> I'm on Gluster 4.0.1. >>>> >>>> I don't think the bricks were smaller before - if they were, maybe 20GB >>>> because Linode's minimum is 20GB, then I extended them to 25GB, resized >>>> with resize2fs as instructed, and rebooted many times over since. Yet, >>>> gluster refuses to see the full disk size. >>>> >>>> Here's the status detail output: >>>> >>>> gluster volume status dev_apkmirror_d...