Re: [CentOS] OT: Replacing Venerable NAS

[Ian Pilcher]

On 11/18/2015 09:31 AM, Tim Evans wrote:

Would like to hear recommendations here.  Besides the ReadyNAS, I have
worked with a Thecus NAS (don't recall model). What are the features I
should look at?


Not a recommendation per se, but if you're interested in running CentOS
on your NAS, I've put together a some kernel modules and a monitoring
daemon for the Thecus N5550 here:

  https://github.com/ipilcher/n5550

--

Ian Pilcher arequip...@gmail.com
 "I grew up before Mark Zuckerberg invented friendship" 


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-docs] Self Introduction

[YosiyukiOoyama]

On 2015年11月19日 01:35, Yosiyuki Ooyama wrote:

My family name is Ooyama.
My last name is Ooyama.
My full name is "Yosiyuki Ooyama".
Sorry.


On 2015年11月19日 01:23, Akemi Yagi wrote:

On Wed, Nov 18, 2015 at 2:48 AM, OoyamaYosiyuki
 wrote:

your FirstnameLastname username

FirstnameLastname=OoyamaYosiyuki
username=OoyamaYosiyuki

the proposed subject of your Wiki contribution(s)

I want to "transulation".  I want to transulation to japanese.

the proposed location of your Wiki contribution(s)

I want to contribute "Japanese" CentOS Wiki

Thanks for your offer to help with the Japanese translation. Before
doing a proper setup, I have one minor question. Your "Last name" (姓)
is Ooyama, I presume. So, your wiki name is expected to be
YosiyukiOoyama.

You don't have to change this if you are aware of the "reversed"
status. As a Japanese, in a way, this is a more natural way. For
people that are not familiar, in Japan our names go Last First. For
example my full name is "Yagi Akemi".

Cheers,

Akemi (this is my FirstName :-)
___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS] OT: Replacing Venerable NAS

[Tim Evans]

On 11/18/2015 11:50 AM, m.r...@5-cent.us wrote:


What size storage are you looking at, and what's your budget? Are we
talking a 4TB drive, or 33TB, or...?


Sorry, should've mentioned this is for home/home office. The ReadyNAS is 
a four-bay unit, with 500GB disks.  Will want a four-bay, probably with 
1- or 2-TB disks.



--
Tim Evans   |   5 Chestnut Court
UNIX System Admin Consulting|   Owings Mills, MD 21117
http://www.tkevans.com/ |   443-394-3864
tkev...@tkevans.com
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-docs] Self Introduction

[Akemi Yagi]

On Wed, Nov 18, 2015 at 8:48 AM, YosiyukiOoyama
 wrote:
> On 2015年11月19日 01:35, Yosiyuki Ooyama wrote:
>
> My family name is Ooyama.
> My last name is Ooyama.
> My full name is "Yosiyuki Ooyama".
> Sorry.

I actually did not ask a question in my previous mail. :(

Would you like to recreate your account as YosiyukiOoyama ? Or keep
the one you already have. Either is fine, so it is up to you.

Akemi
___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS] OT: Replacing Venerable NAS

[m . roth]

Tim Evans wrote:
> I have an original-label Infrant (now NetGear) ReadyNAS storage
> appliance that's been running for 8+ years. Except for replacing its
> power supply, it has not skipped a beat in all this time.
>
> I use it primarily as a backup device (via NFS) for a couple of Linux
> machines, (via SMB) for a couple of Windows PC's, and (via ftp) for web
> sites at my hosting provider.
>
> SMART+ reporting shows ~75K hours operation, with zero sectors
> reallocated, on each of the four disks.
>
> I'm thinking I should be looking for a replacement, even with all this
> good info/luck.
>
> Would like to hear recommendations here.  Besides the ReadyNAS, I have
> worked with a Thecus NAS (don't recall model). What are the features I
> should look at?

What size storage are you looking at, and what's your budget? Are we
talking a 4TB drive, or 33TB, or...?

mark

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Intel SSD

[Michael Hennebry]

On Wed, 18 Nov 2015, Birta Levente wrote:

I have a supermicro server, motherboard is with C612 chipset and beside that 
with LSI3108 raid controller integrated.

Two Intel SSD DC S3710 200GB.
OS: Centos 7.1 up to date.

My problem is that the Intel SSD Data Center Tool (ISDCT) does not recognize 
the SSD drives when they connected to the standard S-ATA ports on the 
motherboard, but through the LSI raid controller is working.


Does somebody know what could be the problem?

I talked to the Intel support and they said the problem is that Centos is not 
supported OS ... only RHEL 7.

But if not supported should not work on the LSI controlled neither.


Perhaps the tool looks for the string RHEL.
My recollection is that when IBM PC's were fairly new,
IBM used that trick with some of its software.
To work around that, some open source developers used the string "not IBM".
I think this was pre-internet, so google might not work.

If it's worth the effort, you might make another "CentOS" distribution,
but call it "not RHEL".

--
Michael   henne...@web.cs.ndsu.nodak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
 --  someeecards
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] OT: Replacing Venerable NAS

[Tim Evans]

I have an original-label Infrant (now NetGear) ReadyNAS storage 
appliance that's been running for 8+ years. Except for replacing its 
power supply, it has not skipped a beat in all this time.


I use it primarily as a backup device (via NFS) for a couple of Linux 
machines, (via SMB) for a couple of Windows PC's, and (via ftp) for web 
sites at my hosting provider.


SMART+ reporting shows ~75K hours operation, with zero sectors 
reallocated, on each of the four disks.


I'm thinking I should be looking for a replacement, even with all this 
good info/luck.


Would like to hear recommendations here.  Besides the ReadyNAS, I have 
worked with a Thecus NAS (don't recall model). What are the features I 
should look at?


Thanks.
--
Tim Evans   |5 Chestnut Court
443-394-3864|Owings Mills, MD 21117
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] centos 7 and keychain

[Tony Mountifield]

In article <564c97ec.2090...@gmail.com>,
Pete Stieber  wrote:
> On 11/17/2015 11:27 AM, PS = Pete Stieber wrote:
> PS>> Is there a centos recommended repository for
> PS>> centos 7 where I can obtain the keychain
> PS>> package?
> 
> 
> I guess building from source may be my only option if I don't hear from 
> anyone.

The first thing I would try is to get the SRPM for CentOS6, install it
in CentOS7 and see if it will rebuild: rpmbuild -bb keychain.spec
(or something like that).

If not, then I would work on updating the SRPM so that it does build.

That would be much more preferable than building directly from source
outside of the package manager.

Cheers
Tony
-- 
Tony Mountifield
Work: t...@softins.co.uk - http://www.softins.co.uk
Play: t...@mountifield.org - http://tony.mountifield.org
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] centos 7 and keychain

[Pete Stieber]

On 11/17/2015 11:27 AM, PS = Pete Stieber wrote:
PS>> Is there a centos recommended repository for
PS>> centos 7 where I can obtain the keychain
PS>> package?

On 11/17/2015 8:19 PM, WJ = Wes James wrote:
WJ> I can only see a version for centos 6:
WJ>
WJ> http://pkgs.repoforge.org/keychain/
WJ>
WJ> You’ll need to download the src and see if
WJ>you can build it. ??

Thanks Wes,

I found old web sites that suggest using rpmforge, but there isn't a 
version for CentOS 7 there and the CentOS wiki...


https://wiki.centos.org/AdditionalResources/Repositories

...lists RPMForge/RepoForge as a "known problem repository".

I found the following...

http://pkgs.org/centos-7/psychotic-ninja-x86_64/

which include keychain...

http://pkgs.org/centos-7/psychotic-ninja-x86_64/keychain-2.7.1-1.el7.psychotic.noarch.rpm.html

but was wondering about the integrity of this.

Any opinions?

I guess building from source may be my only option if I don't hear from 
anyone.


TIA,
Pete


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Intel SSD

[Matt Garman]

I always tell vendors I'm using RHEL, even though we're using CentOS.
If you say CentOS, some vendors immediately throw up their hands and
say "unsupported" and then won't even give you the time of day.

A couple tricks for fooling tools into thinking they are on an actual
RHEL system:
1. Modify /etc/redhat-release to say RedHat Enterprise Linux or
whatever the actual RHEL systems have
2. Similarly modify /etc/issue

Another tip that has proven successful: run the vendor tool under
strace.  Sometimes you can get an idea of what it's trying to do and
why it's failing.  This is exactly what we did to determine why a
vendor tool wouldn't work on CentOS.  We had modified
/etc/redhat-release (as in (1) above), but forgot about /etc/issue.
Strace showed the program existing immediately after an open() call to
/etc/issue.

Good luck!




On Wed, Nov 18, 2015 at 9:24 AM, Michael Hennebry
 wrote:
> On Wed, 18 Nov 2015, Birta Levente wrote:
>
>> I have a supermicro server, motherboard is with C612 chipset and beside
>> that with LSI3108 raid controller integrated.
>> Two Intel SSD DC S3710 200GB.
>> OS: Centos 7.1 up to date.
>>
>> My problem is that the Intel SSD Data Center Tool (ISDCT) does not
>> recognize the SSD drives when they connected to the standard S-ATA ports on
>> the motherboard, but through the LSI raid controller is working.
>>
>> Does somebody know what could be the problem?
>>
>> I talked to the Intel support and they said the problem is that Centos is
>> not supported OS ... only RHEL 7.
>> But if not supported should not work on the LSI controlled neither.
>
>
> Perhaps the tool looks for the string RHEL.
> My recollection is that when IBM PC's were fairly new,
> IBM used that trick with some of its software.
> To work around that, some open source developers used the string "not IBM".
> I think this was pre-internet, so google might not work.
>
> If it's worth the effort, you might make another "CentOS" distribution,
> but call it "not RHEL".
>
> --
> Michael   henne...@web.cs.ndsu.nodak.edu
> "Sorry but your password must contain an uppercase letter, a number,
> a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
>  --  someeecards
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-docs] Self Introduction

[Akemi Yagi]

On Wed, Nov 18, 2015 at 2:48 AM, OoyamaYosiyuki
 wrote:
> your FirstnameLastname username
>
> FirstnameLastname=OoyamaYosiyuki
> username=OoyamaYosiyuki
>
> the proposed subject of your Wiki contribution(s)
>
> I want to "transulation".  I want to transulation to japanese.
>
> the proposed location of your Wiki contribution(s)
>
> I want to contribute "Japanese" CentOS Wiki

Thanks for your offer to help with the Japanese translation. Before
doing a proper setup, I have one minor question. Your "Last name" (姓)
is Ooyama, I presume. So, your wiki name is expected to be
YosiyukiOoyama.

You don't have to change this if you are aware of the "reversed"
status. As a Japanese, in a way, this is a more natural way. For
people that are not familiar, in Japan our names go Last First. For
example my full name is "Yagi Akemi".

Cheers,

Akemi (this is my FirstName :-)
___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS] Intel SSD

[Eero Volotinen]

strace -f -e open software_binary might help, but I have noticed that
Centos is not really 100% binary compatible in some cases.



--
Eero

2015-11-18 17:42 GMT+02:00 Matt Garman :

> I always tell vendors I'm using RHEL, even though we're using CentOS.
> If you say CentOS, some vendors immediately throw up their hands and
> say "unsupported" and then won't even give you the time of day.
>
> A couple tricks for fooling tools into thinking they are on an actual
> RHEL system:
> 1. Modify /etc/redhat-release to say RedHat Enterprise Linux or
> whatever the actual RHEL systems have
> 2. Similarly modify /etc/issue
>
> Another tip that has proven successful: run the vendor tool under
> strace.  Sometimes you can get an idea of what it's trying to do and
> why it's failing.  This is exactly what we did to determine why a
> vendor tool wouldn't work on CentOS.  We had modified
> /etc/redhat-release (as in (1) above), but forgot about /etc/issue.
> Strace showed the program existing immediately after an open() call to
> /etc/issue.
>
> Good luck!
>
>
>
>
> On Wed, Nov 18, 2015 at 9:24 AM, Michael Hennebry
>  wrote:
> > On Wed, 18 Nov 2015, Birta Levente wrote:
> >
> >> I have a supermicro server, motherboard is with C612 chipset and beside
> >> that with LSI3108 raid controller integrated.
> >> Two Intel SSD DC S3710 200GB.
> >> OS: Centos 7.1 up to date.
> >>
> >> My problem is that the Intel SSD Data Center Tool (ISDCT) does not
> >> recognize the SSD drives when they connected to the standard S-ATA
> ports on
> >> the motherboard, but through the LSI raid controller is working.
> >>
> >> Does somebody know what could be the problem?
> >>
> >> I talked to the Intel support and they said the problem is that Centos
> is
> >> not supported OS ... only RHEL 7.
> >> But if not supported should not work on the LSI controlled neither.
> >
> >
> > Perhaps the tool looks for the string RHEL.
> > My recollection is that when IBM PC's were fairly new,
> > IBM used that trick with some of its software.
> > To work around that, some open source developers used the string "not
> IBM".
> > I think this was pre-internet, so google might not work.
> >
> > If it's worth the effort, you might make another "CentOS" distribution,
> > but call it "not RHEL".
> >
> > --
> > Michael   henne...@web.cs.ndsu.nodak.edu
> > "Sorry but your password must contain an uppercase letter, a number,
> > a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
> >  --
> someeecards
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > https://lists.centos.org/mailman/listinfo/centos
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] OT: Replacing Venerable NAS

[Frank Cox]

On Wed, 18 Nov 2015 12:38:06 -0500
Tim Evans wrote:

> Sorry, should've mentioned this is for home/home office. The ReadyNAS is 
> a four-bay unit, with 500GB disks.  Will want a four-bay, probably with 
> 1- or 2-TB disks.

I just bought a QNAP TS-251 a couple of months ago to replace my old  Intel 
SS4000E fileserver that started looking like it was thinking about dying after 
a dozen years in service.

So far I'm pretty happy with this QNAP, though I did have to spend a while in 
the setup screen turning off a bunch of stuff that I don't need, want, or care 
about.  In particular, it was creating a ton of .@_thumb files every night.  
Since I use it exclusively for  file backups, I don't want any of the 
"multimedia" stuff that it can do, but now that I've got all of that turned 
off, it's a slick little fileserver.

The one that I got is only two bays but they sell bigger ones if you want it.  
I just got the two bay model with two 1tb hard drives in it.

-- 
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] OT: Replacing Venerable NAS

[m . roth]

Tim Evans wrote:
> On 11/18/2015 11:50 AM, m.r...@5-cent.us wrote:
>
>> What size storage are you looking at, and what's your budget? Are we
>> talking a 4TB drive, or 33TB, or...?
>
> Sorry, should've mentioned this is for home/home office. The ReadyNAS is
> a four-bay unit, with 500GB disks.  Will want a four-bay, probably with
> 1- or 2-TB disks.
>
Recommendation #1: get a multi-bay drive, and buy your own drives - it'll
be cheaper. That being said, we really like our WD Red 4TB drives. They
run about $160 each. The Red *are* for NAS, SAN, etc.

   mark

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Intel SSD

[Valeri Galtsev]

On Wed, November 18, 2015 12:05 pm, m.r...@5-cent.us wrote:
> Michael Hennebry wrote:
>> On Wed, 18 Nov 2015, Birta Levente wrote:
>>
>>> I have a supermicro server, motherboard is with C612 chipset and beside
> that with LSI3108 raid controller integrated.Two Intel SSD DC S3710
> 200GB. OS: Centos 7.1 up to date.
>>>
>>> My problem is that the Intel SSD Data Center Tool (ISDCT) does not
> recognize the SSD drives when they connected to the standard S-ATA
> ports on the motherboard, but through the LSI raid controller is
> working.
>>>
>>> Does somebody know what could be the problem?
> 
>> Perhaps the tool looks for the string RHEL.
>> My recollection is that when IBM PC's were fairly new,
>> IBM used that trick with some of its software.
>> To work around that, some open source developers used the string "not
>>  IBM".I think this was pre-internet, so google might not work.
>>
>> If it's worth the effort, you might make another "CentOS" distribution,
> but call it "not RHEL".
>>
> I'll add to that: it was only maybe three years ago that to get one of
> Dell's support tools (Dset, maybe) to run on one of our CentOS boxes was
> to edit /etc/redhat-release so that it had the RH info, instead of saying
> CentosOS release ... You might try that.
>
>> --
>> Michael   henne...@web.cs.ndsu.nodak.edu
>> "Sorry but your password must contain an uppercase letter, a number, a
> haiku, a gang sign, a heiroglyph, and the blood of a virgin."
>
> That's never going to work - where the hell do you find a virgin?

Will extra virgin olive oil be fair replacement?

>
> mark
>
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>



Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] OT: Replacing Venerable NAS

[Gordon Messmer]

On 11/18/2015 07:31 AM, Tim Evans wrote:

Would like to hear recommendations here.


https://www.ixsystems.com/freenas-mini/

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Intel SSD

[m . roth]

Michael Hennebry wrote:
> On Wed, 18 Nov 2015, Birta Levente wrote:
>
>> I have a supermicro server, motherboard is with C612 chipset and beside
that with LSI3108 raid controller integrated.Two Intel SSD DC S3710
200GB. OS: Centos 7.1 up to date.
>>
>> My problem is that the Intel SSD Data Center Tool (ISDCT) does not
recognize the SSD drives when they connected to the standard S-ATA
ports on the motherboard, but through the LSI raid controller is
working.
>>
>> Does somebody know what could be the problem?

> Perhaps the tool looks for the string RHEL.
> My recollection is that when IBM PC's were fairly new,
> IBM used that trick with some of its software.
> To work around that, some open source developers used the string "not
>  IBM".I think this was pre-internet, so google might not work.
>
> If it's worth the effort, you might make another "CentOS" distribution,
but call it "not RHEL".
>
I'll add to that: it was only maybe three years ago that to get one of
Dell's support tools (Dset, maybe) to run on one of our CentOS boxes was
to edit /etc/redhat-release so that it had the RH info, instead of saying
CentosOS release ... You might try that.

> --
> Michael   henne...@web.cs.ndsu.nodak.edu
> "Sorry but your password must contain an uppercase letter, a number, a
haiku, a gang sign, a heiroglyph, and the blood of a virgin."

That's never going to work - where the hell do you find a virgin?

mark



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] OT: Replacing Venerable NAS

[Warren Young]

On Nov 18, 2015, at 11:04 AM, Gordon Messmer  wrote:
> 
> On 11/18/2015 07:31 AM, Tim Evans wrote:
>> Would like to hear recommendations here.
> 
> https://www.ixsystems.com/freenas-mini/

For those who don’t know why you’d pay $1000 for a diskless 4-bay NAS box when 
there are $300-500 boxes that are superficially similar from QNAP, Synology, 
and others:

- ZFS.  Modern cheap NAS boxes have gained some ZFS-like features (online 
expansion and such) but they’re still not ZFS.

- FreeNAS.  Many low-end NASes use proprietary or rebadged ODM management 
software that barely scrapes by in terms of features and support, whereas 
FreeNAS has a long-standing open source developer community behind it.

- Much bigger CPU than is typical for the low-end NAS boxes.  Many low-end NAS 
boxes have gigabit Ethernet ports, but if you don’t put enough CPU grunt behind 
that port, you can’t fill it.  As a rule, you need at least 1 GHz of CPU to 
fill a gigabit pipe.

- Much more RAM than in low-end NAS boxes.  Partly this is because ZFS (the 
storage subsystem for FreeNAS) is a RAM-hungry pig, but the benefit you get 
from that is that more of your data is in RAM, so even if your spindles aren’t 
fast enough to fill the gigabit pipe, data from cache can fill it.

- L2ARC and ZIL upgrade options, which are intermediary caches between RAM and 
disk.  Again, this helps you to keep that gigabit pipe full.

- They’re serious server-grade machines, not borderline flimsy boxes competing 
largely on price.  Built in and supported from Silicon Valley, not China. :)

- iXsystems sponsors FreeNAS and FreeBSD (via PC-BSD) developers.  Does your 
alternative choice of NAS provider sponsor open source developers?

- Those latter two points mean you can actually call them and get someone on 
the phone who knows what they’re talking about.  The last time my Lacie NAS 
choked, I had to just nuke it and re-mirror all the data.

I don’t have a FreeNAS mini, and I have never used one.  But, I’ve been lusting 
after them for some time now.  Next time one of my NASes dies, one of these is 
going to be high on the list of choices for replacement.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Intel SSD

[Gordon Messmer]

On 11/18/2015 06:25 AM, Birta Levente wrote:
My problem is that the Intel SSD Data Center Tool (ISDCT) does not 
recognize the SSD drives when they connected to the standard S-ATA 
ports on the motherboard, but through the LSI raid controller is working. 


Check your BIOS settings for non-standard modes on the SATA ports. Maybe 
they're in legacy (IDE) or an incompatible RAID mode.  Intel's docs 
don't note specific requirements, but I'd expect ports in AHCI mode to 
work correctly.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] OT: Replacing Venerable NAS

[Bill Campbell]

We're using Synology boxes with good results so far.

They're built on Linux with ssh access and good support for
things like rsync.

They have options to backup to remote servers including Amazon too.

On Wed, Nov 18, 2015, Tim Evans wrote:
> I have an original-label Infrant (now NetGear) ReadyNAS storage  
> appliance that's been running for 8+ years. Except for replacing its  
> power supply, it has not skipped a beat in all this time.
>
> I use it primarily as a backup device (via NFS) for a couple of Linux  
> machines, (via SMB) for a couple of Windows PC's, and (via ftp) for web  
> sites at my hosting provider.
>
> SMART+ reporting shows ~75K hours operation, with zero sectors  
> reallocated, on each of the four disks.
>
> I'm thinking I should be looking for a replacement, even with all this  
> good info/luck.
>
> Would like to hear recommendations here.  Besides the ReadyNAS, I have  
> worked with a Thecus NAS (don't recall model). What are the features I  
> should look at?
>
> Thanks.
> -- 
> Tim Evans |5 Chestnut Court
> 443-394-3864  |Owings Mills, MD 21117
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>

-- 
Bill
-- 
INTERNET:   b...@celestial.com  Bill Campbell; Celestial Software LLC
URL: http://www.celestial.com/  PO Box 820; 6641 E. Mercer Way
Voice:  (206) 236-1676  Mercer Island, WA 98040-0820
Fax:(206) 232-9186  Skype: jwccsllc (206) 855-5792

If you think health care is expensive now, wait until you see what it coses
when it's free -- P.J. O'Rourke
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Running Fedora under CentOS via systemd-nspawn?

[Matt Garman]

I actually built HandBrake 0.10.2 (the latest) under C7 (using a
CentOS 7 nspawn container so as not to pollute the main system with
the dozens of deps I installed).  Full details here if you're
interested:

http://raw-sewage.net/articles/fedora-under-centos/

The problem with the newer version of HandBrake is that it requires (a
very recent version of) gtk3, which in turn has several other deps
that need to be upgraded on C7.  But I worked through all that, and
can provide all the spec files if anyone wants.

Anyway, the HandBrake problem is solved for me (in possibly multiple ways).

But I'm just fascinated by the possibilities of nspawn, and wondering
how far one can take it before instabilities are introduced.

Consider how many people out there have similar problems as me: want
to run CentOS for stability/reliability/vendor support, but also want
some bleeding-edge software that's only available on Fedora (or Ubuntu
or Arch).  If it's "safe" to run these foreign distributions under
CentOS via nspawn, then I think that's a simple solution.  Virtual
Machines are of course a possible solution, but they seem overkill for
this class of problem.  And not to mention. possibly
inefficient---something like HandBrake should benefit from running on
bare metal, rather than under a virtualized CPU.







On Wed, Nov 18, 2015 at 1:11 PM, Lamar Owen  wrote:
> On 11/17/2015 12:39 PM, Matt Garman wrote:
>>
>> Now I have a need for a particular piece of software: HandBrake.  I
>> found this site[1] that packages it for both Fedora and CentOS.  But
>> the CentOS version is a little older, as the latest HandBrake requires
>> gtk3.  The latest version is available for Fedora however.
>>
> Hmm, Nux Dextop (li.nux.ro) has HandBrake 0.9.9 for C7, but not yet 0.10.2.
> Nux! is around this list and might be able to shed light on what is needed
> for 0.10.2.
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] OT: Replacing Venerable NAS

[Warren Young]

On Nov 18, 2015, at 12:16 PM, Chris Adams  wrote:
> 
> Once upon a time, Warren Young  said:
>> - They’re serious server-grade machines, not borderline flimsy boxes 
>> competing largely on price.  Built in and supported from Silicon Valley, not 
>> China. :)
> 
> iXsystems sells rebadged SuperMicro stuff, nothing special (not made in
> Silicon Valley).

Good to know, though I must say, the SuperMicro stuff I’ve used is a cut above 
typical desktop PC or commodity grade hardware.  Not on par with super high end 
stuff, but well above average.

> iX found and fixed a FreeBSD kernel NFS bug, but it was a
> painful experience.

I see that story in the exact opposite way: iXsystems found and fixed the 
problem, expending heroic levels of effort to do so.  

By contrast, I’ve had several $300-500 NASes become unmountable for one reason 
or another, and the vendor was no use *at all* in getting it remounted.  I had 
to rebuild the NAS from backups each time.

It’s rather annoying to buy a NAS, then later realize you need to buy *another* 
NAS as a mirror in case the first one roaches itself.  Isn’t that what 
redundant storage is supposed to avoid?

Meanwhile, I’ve never had a ZFS pool become unmountable, even when the disk 
enclosure hardware was failing underneath it.

> Then, early this year, we had a node fail, and it took them almost a
> month to get us a replacement.

That’s not good.

But have you gotten better turn time from the $300-500 NAS providers for the 
same service?

Did you opt for advance replacement, and if not, why not?

> Their idea of HA is to monitor the ethernet links, not the services;

Do the $300-500 NAS boxes even try to do HA failover?

> even though we have multiple links in a LAG

I’ve also had trouble with FreeBSD’s lagg feature.  Fortunately, my use case 
allowed me to switch to a round-robin DNS based load balancing scheme instead.  
I don’t think you can do that with NFS, by its nature.

> And today, when trying to open a ticket, their website is broken because
> one of their DNS servers is returning 10.0.0.240 for part of their
> website (where the CSS is served).

Yes, I noticed their site was running awfully slowly.  Embarrassing, but I 
don’t see what it has to do with the quality of their FreeNAS boxes.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Running Fedora under CentOS via systemd-nspawn?

[Lamar Owen]

On 11/17/2015 12:39 PM, Matt Garman wrote:

Now I have a need for a particular piece of software: HandBrake.  I
found this site[1] that packages it for both Fedora and CentOS.  But
the CentOS version is a little older, as the latest HandBrake requires
gtk3.  The latest version is available for Fedora however.

Hmm, Nux Dextop (li.nux.ro) has HandBrake 0.9.9 for C7, but not yet 
0.10.2.  Nux! is around this list and might be able to shed light on 
what is needed for 0.10.2.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] OT: Replacing Venerable NAS

[Chris Adams]

Once upon a time, Warren Young  said:
> - They’re serious server-grade machines, not borderline flimsy boxes 
> competing largely on price.  Built in and supported from Silicon Valley, not 
> China. :)

iXsystems sells rebadged SuperMicro stuff, nothing special (not made in
Silicon Valley).

We bought an iXsystems TrueNAS (commercial version of FreeNAS +
"supported" hardware) system at $DAYJOB about 2 years ago, with the
dual-node "HA" setup, and it was not a pleasant experience.  Over the
first 6 months or so, our longest functioning uptime was about 10 days.
NFS would run and then just stop serving (no errors or anything).
Eventually, iX found and fixed a FreeBSD kernel NFS bug, but it was a
painful experience.

Then, early this year, we had a node fail, and it took them almost a
month to get us a replacement.

Their idea of HA is to monitor the ethernet links, not the services;
even though we have multiple links in a LAG, if one drops, the node
fails over (and now we're having trouble with CentOS 7 NFS clients when
the TrueNAS has a failover).  When we had NFS problems, we had to
monitor that externally and manually trigger a failover.  Failover
consists of "reboot the active node"; there's no graceful cluster tool
(such as Pacemaker on Linux).

And today, when trying to open a ticket, their website is broken because
one of their DNS servers is returning 10.0.0.240 for part of their
website (where the CSS is served).

-- 
Chris Adams 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] OT: Replacing Venerable NAS

[John R Pierce]

On 11/18/2015 10:42 AM, Bill Campbell wrote:

We're using Synology boxes with good results so far.


I've heard good things about Synology.

My home NAS going on 3 years now is a HP Microserver running FreeNAS, 
with 4 x 3TB SATA drives.




--
john r pierce, recycling bits in santa cruz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-virt] CentOS 6 Xen package update (including XSA-156)

[Johnny Hughes]

On 11/18/2015 07:31 AM, Pasi Kärkkäinen wrote:
> On Wed, Nov 18, 2015 at 02:20:49PM +0200, Manuel Wolfshant wrote:
>> On 11/18/2015 02:08 PM, Pasi Kärkkäinen wrote:
>>> Hello,
>>>
>>> On Sun, Nov 15, 2015 at 06:42:18PM +0200, Pasi Kärkkäinen wrote:
 On Sun, Nov 15, 2015 at 02:04:58PM +0200, Pasi Kärkkäinen wrote:
> On Thu, Nov 12, 2015 at 02:00:27PM +, George Dunlap wrote:
>> So going forward, we're moving the CentOS 6 Xen packages from the
>> custom "xen4" repos that were introduced several years ago, to repos
>> based on its position as a sub-project of the Virt Sig.  That will
>> make things consistent between all the sigs, as well as between CentOS
>> 6 and 7 Xen packages.
>>
>> Unfortunately, XSA-156 came up rather suddenly and is a bit blocked by
>> this transition.
>>
>> So please help us test the new repository structure, so that we can
>> with conscience push the updates to xen4 users in general.
>>
> Seems to work for me!
>
>
 Except now on another system I see this problem:

>>> Anyone else seeing this libvirt-python problem with virt-manager and/or 
>>> virt-viewer ?
>>>
>>> (happens on a freshly installed system, so no earlier libvirt rpms 
>>> installed)
>>>
>> It tries to install half of the OS, but it works for me.  It seems
>> that your yum does not like that you already have
>> libvirt-client-1.2.15-3.el6.x86_64. Mine is happy to bring in
>> libvirt-{python,client}-0.10.2-54.el6_7.2.x86_64 from updates
>>
> 
> libvirt-{python,client}-0.10.2-54.el6_7.2.x86_64 are the centos core packages,
> while the libvirt-client-1.2.15-3.el6.x86_64 is the Virt SIG provided one,
> which has Xen support enabled.
> 
> So I need the 1.2.15-3 versions, but it seems libvirt-python is not included 
> in the Virt SIG built ones..
> 
> So that's an issue/problem..


It looks like either this needs to be tagged into the proper repo or a
new version built:

http://cbs.centos.org/koji/buildinfo?buildID=252

Pasi, that version exists here:

http://mirror.centos.org/centos/6.7/xen4/x86_64/Packages/

Can you see if it works with :

http://mirror.centos.org/centos/6.7/xen4/x86_64/Packages/libvirt-python-1.2.10-2.el6.x86_64.rpm


Thanks,
Johnny Hughes






signature.asc
Description: OpenPGP digital signature
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS] OT: Replacing Venerable NAS

[Gordon Messmer]

On 11/18/2015 11:16 AM, Chris Adams wrote:

Once upon a time, Warren Young  said:

- They’re serious server-grade machines, not borderline flimsy boxes competing 
largely on price.  Built in and supported from Silicon Valley, not China. :)

iXsystems sells rebadged SuperMicro stuff, nothing special (not made in
Silicon Valley).


They aren't fabbed there, but the assembly is done in the USA.

We used the mini extensively in my previous position, managing IT for a 
few dozen small businesses.  As backup systems go, it was very 
reliable.  We didn't use them as servers, though.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] OT: Replacing Venerable NAS

[John R Pierce]

On 11/18/2015 11:55 AM, Warren Young wrote:

It’s rather annoying to buy a NAS, then later realize you need to buy*another*  
NAS as a mirror in case the first one roaches itself.  Isn’t that what 
redundant storage is supposed to avoid?



no, RAID is purely availability when faced with single or double drive 
failure, nothing else.   classic raid is most certainly NOT about data 
integrity, as the raid stripes aren't checksummed, they assume hardware 
data integrity.




--
john r pierce, recycling bits in santa cruz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] OT: Replacing Venerable NAS

[Chris Adams]

Once upon a time, Warren Young  said:
> I see that story in the exact opposite way: iXsystems found and fixed the 
> problem, expending heroic levels of effort to do so.  
> 
> By contrast, I’ve had several $300-500 NASes become unmountable for one 
> reason or another, and the vendor was no use *at all* in getting it remounted.

So, I was offering my opinion (backed by some personal anecdotes) of
iXsystems.  The system we had with all this trouble was much more than
$300 (more like $30,000); IMHO it isn't "heroic levels of effort" to do
something they told us it could do before we wrote the check.

> Did you opt for advance replacement, and if not, why not?

Yes, we had purchased a support contract that included advance
replacement.  They had no replacement part and took several weeks to
find one.

> I’ve also had trouble with FreeBSD’s lagg feature.  Fortunately, my use case 
> allowed me to switch to a round-robin DNS based load balancing scheme 
> instead.  I don’t think you can do that with NFS, by its nature.

Yes, NFS talks to a single IP at a time.  My problem isn't with FreeBSD,
it with the TrueNAS software; it considers any configured network link
dropping as a reason to fail over (even if the link is in a LAG).  That
is not configurable behavior.

> Yes, I noticed their site was running awfully slowly.  Embarrassing, but I 
> don’t see what it has to do with the quality of their FreeNAS boxes.

Mainly just more anecdotal evidence about the company and their general
reliability.

I know there are fans of iXsystems and FreeNAS; I am not one of them
(nor is anyone in my office).  We also sold a TrueNAS system to a
customer, they had trouble (different problems from us), and we just
about lost the customer.

-- 
Chris Adams 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Linux ate my RAM...

[Kwan Lowe]

Hello everyone,

Excuse the title. I'm trying to do something very specific that goes
against some common assumptions.

I am aware of how Linux uses available memory to cache. This, in
almost all cases, is desirable. I've spent years explaining to users
how to properly read the free output.

I'm now trying to increase VM density on host systems (by host, I mean
the physical system, not the underlying guest machines).

VMWare can over-allocate memory as long as it's not being used.
Because of caching, from VMWare's perspective, all Linux memory is
being "used". I am aware of the inherent risks in over-allocation of
resources on a VMWare system.This tuning is strictly for development
systems where performance and stability are not as critical. The
increase in vm density is an acceptable tradeoff.

My questions:
1) What options are available in CentOS to limit the page cache? SuSe
has vm.pagecache_limit_mb and vm.pagecache_limit_ignore_dirty which,
in conjunction with swappiness tweaks, appears to do what I need.

2) Any experience with enabling /sys/kernel/mm/ksm/run on non-KVM
workloads? As KSM only applies to non-pagecache memory, it doesn't
immediately help me here but could be incrementally useful
(https://www.kernel.org/doc/Documentation/vm/ksm.txt).

3) Is there any way to control /proc/sys/vm/drop_caches and limit it
to a number of entries or age?  Dropping the filesystem cache, though
it unmarks those pages, has performance implications.

Thanks in advance for any input or links.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS-announce] CESA-2015:2081 Moderate CentOS 6 postgresql Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2015:2081 Moderate

Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-2081.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
0e97fe4a73fd3e52d253aa01a78d4a2c75e57415e62a2468dc8639352016e817  
postgresql-8.4.20-4.el6_7.i686.rpm
54877c2fedcbdd30cc66941d449dc70077fc886fcac53e3d589e764452171354  
postgresql-contrib-8.4.20-4.el6_7.i686.rpm
23992e58740882150065ac43e544b4f8aa53a942b9393e354faa7bf20411b4b4  
postgresql-devel-8.4.20-4.el6_7.i686.rpm
a4fc45d81815c93da5d5a3948eaba1f598937a0e6b80a7ced9de1958daa66158  
postgresql-docs-8.4.20-4.el6_7.i686.rpm
217f335cc844426b53558859ae65f7e45b96e02ea2e3b267288f9404bbba9fd4  
postgresql-libs-8.4.20-4.el6_7.i686.rpm
6e7534efb6c9eb1db98ec1e1e581a351cee2733f7d641decb390f6f60d448099  
postgresql-plperl-8.4.20-4.el6_7.i686.rpm
cc50decba345bf784b9821edb1c8f1921a708a4d9440f444ece54383c2bf005b  
postgresql-plpython-8.4.20-4.el6_7.i686.rpm
b1d88b3f571a551d5438f3f397ecf79a1bbf45df822019160db4f22776e6a91e  
postgresql-pltcl-8.4.20-4.el6_7.i686.rpm
65e5d758024188f6ba096bc1c96754f45d6ce98944beddb9ecfa087dad9bf55f  
postgresql-server-8.4.20-4.el6_7.i686.rpm
9b4ddd7a4cf4ff7c24e91be92fa8062092e19672f3fb939817abd7d770eb9baa  
postgresql-test-8.4.20-4.el6_7.i686.rpm

x86_64:
0e97fe4a73fd3e52d253aa01a78d4a2c75e57415e62a2468dc8639352016e817  
postgresql-8.4.20-4.el6_7.i686.rpm
2cf6ecc14534ef1bb553da2743b1a2b7679ad6e076dd2301d241833c8288e02c  
postgresql-8.4.20-4.el6_7.x86_64.rpm
0cebe83b0f5f91d5055eec015539904d9d6c5c6e4a41848f0f39ddfebf54a082  
postgresql-contrib-8.4.20-4.el6_7.x86_64.rpm
23992e58740882150065ac43e544b4f8aa53a942b9393e354faa7bf20411b4b4  
postgresql-devel-8.4.20-4.el6_7.i686.rpm
f02d225b9769f8a69c9a38bdc360e92b96d37b37db2c372ca020d597dea19dae  
postgresql-devel-8.4.20-4.el6_7.x86_64.rpm
b001349770fb86984191de0d8a90d30d41dab95ca1467d8e31ef067cefd050b8  
postgresql-docs-8.4.20-4.el6_7.x86_64.rpm
217f335cc844426b53558859ae65f7e45b96e02ea2e3b267288f9404bbba9fd4  
postgresql-libs-8.4.20-4.el6_7.i686.rpm
252e3df351f8007191831d1c40b13e868811672d11c40a81fac17e3d213be926  
postgresql-libs-8.4.20-4.el6_7.x86_64.rpm
54c0316956e115eb0c41c445a211675cff32f2628575765b368de7a735119350  
postgresql-plperl-8.4.20-4.el6_7.x86_64.rpm
60e79f2a2d21dd3d8d8e1714ca063ecd5a2a302db824f9a735006c700bc351e7  
postgresql-plpython-8.4.20-4.el6_7.x86_64.rpm
ba395b85bb86749ddb58b1e43509412c684d0b18c7fe41052874073dafc926de  
postgresql-pltcl-8.4.20-4.el6_7.x86_64.rpm
d189c260a6280f771eeed522750d4f7928fad095293fdd287f29b4dd2e8f6871  
postgresql-server-8.4.20-4.el6_7.x86_64.rpm
77309a9e212b2f424990eae82510308ea036d9a40040162068be8b4f0a66a597  
postgresql-test-8.4.20-4.el6_7.x86_64.rpm

Source:
b0eb57695234f5cc6f2ab2df3eef661726f065926a303cfa0278cc003ab24ed2  
postgresql-8.4.20-4.el6_7.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

[CentOS-announce] CESA-2015:2086 Important CentOS 5 java-1.6.0-openjdk Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2015:2086 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-2086.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
aa99f34b3c368695046b073a2065735f41b443f5014998662141472784808fc8  
java-1.6.0-openjdk-1.6.0.37-1.13.9.4.el5_11.i386.rpm
22a5e9945db46cbc09e28e944037f97e08ada786a29633fc0749c473bf27a75e  
java-1.6.0-openjdk-demo-1.6.0.37-1.13.9.4.el5_11.i386.rpm
1c74dc66b90779a55849b0f2857c99ed7c44d0e4071bfd0afec944d85df32e2b  
java-1.6.0-openjdk-devel-1.6.0.37-1.13.9.4.el5_11.i386.rpm
6fdbd6c9f8cf75a2e59755291275d4dd649ae80a723389495e5174eab93cdf20  
java-1.6.0-openjdk-javadoc-1.6.0.37-1.13.9.4.el5_11.i386.rpm
9cb01c62fa3a3c13e33a88fe3e121d9e0509a3fe1aadf1b13a45067046eecf4e  
java-1.6.0-openjdk-src-1.6.0.37-1.13.9.4.el5_11.i386.rpm

x86_64:
647faf2b65173da2df9cb57b1fc4c55605474eb675b8695551d6ea51f695213c  
java-1.6.0-openjdk-1.6.0.37-1.13.9.4.el5_11.x86_64.rpm
1e99cb89adbd0b8331adbef47eab6911df5fb042481c004dc9e55978c828acf0  
java-1.6.0-openjdk-demo-1.6.0.37-1.13.9.4.el5_11.x86_64.rpm
df9c09dc2debaf5315d92f63a2516ba59f1b1a21cf9b8c1817beaa3b76f2f700  
java-1.6.0-openjdk-devel-1.6.0.37-1.13.9.4.el5_11.x86_64.rpm
e85105b2fe6f41629828fcae5f78bc62bd3b4d4b3e41a27f06c333799c3e74cf  
java-1.6.0-openjdk-javadoc-1.6.0.37-1.13.9.4.el5_11.x86_64.rpm
3a46d303cfaff3b86d43d157a039181542895f45d109c77bd0f81540f69a75e0  
java-1.6.0-openjdk-src-1.6.0.37-1.13.9.4.el5_11.x86_64.rpm

Source:
02ad1a69ec9a3b1832ec47ff1c4f13fcb54d45f55bf5d9907b6a582888b71bb8  
java-1.6.0-openjdk-1.6.0.37-1.13.9.4.el5_11.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: JohnnyCentOS

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

[CentOS-announce] CESA-2015:2078 Moderate CentOS 7 postgresql Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2015:2078 Moderate

Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-2078.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
dac984ae0f6ec9bbb3fbf89ab18387c911ecd381d0d42502212090583a255fb0  
postgresql-9.2.14-1.el7_1.i686.rpm
48c8a0de83c28f79cc1a85f1b6572560860563610721ee7700d7ada688d25b4e  
postgresql-9.2.14-1.el7_1.x86_64.rpm
da0f25e0fa38d0fc93d6b3817797b67ed1f5130e49c91477b19f27bde73770f7  
postgresql-contrib-9.2.14-1.el7_1.x86_64.rpm
4ff2972830681f8b3878fb465c3b0eb93e315645eb5f8d32d19f04b983f563a6  
postgresql-devel-9.2.14-1.el7_1.i686.rpm
eae197326a7ae78b9f633c718d0e7eb48f5ac3520fe5ff787ab07dfb9a23ab79  
postgresql-devel-9.2.14-1.el7_1.x86_64.rpm
efd8026ec5026a22471688e0c19b2a53657c8d9a770829dbc12234c46e1c  
postgresql-docs-9.2.14-1.el7_1.x86_64.rpm
3897ca7ab0e9ed9df4c81c3e15da0ba069b74bd59c2e9743755e3654d8b3b712  
postgresql-libs-9.2.14-1.el7_1.i686.rpm
4a409cfde77bc7b14f18a152e896ad3290aef94355a8c9ee993e9075b05160e9  
postgresql-libs-9.2.14-1.el7_1.x86_64.rpm
89f5050225e4bc4ca162822ed0bdd16a0cf34f0b70fd0b2b3422a5850d37556d  
postgresql-plperl-9.2.14-1.el7_1.x86_64.rpm
35868c84234ab8afe3fdc05b181463f2161e2785fe0f55d21ec5368eb556c7a6  
postgresql-plpython-9.2.14-1.el7_1.x86_64.rpm
2598a7f5e6b3d9fa1354fd373c039d7eec38e980b60af005a0051096d5e845a6  
postgresql-pltcl-9.2.14-1.el7_1.x86_64.rpm
bd457b9b0838e97e8dc54e8d730ac75da3ab297623bebaae23ec249c9da32fb2  
postgresql-server-9.2.14-1.el7_1.x86_64.rpm
59674923b6e61253f8442a75ad7b1b671af6d8f3d02fac54ee9d93402c357f0a  
postgresql-test-9.2.14-1.el7_1.x86_64.rpm
7e81ff716e88e95e0157c53a02d2050c4858cce6d8fd22ace50287f18c481789  
postgresql-upgrade-9.2.14-1.el7_1.x86_64.rpm

Source:
7e684cc6556afa15a60582354c7a110461946416b70332fe09bbb499bd6f0aec  
postgresql-9.2.14-1.el7_1.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

Re: [CentOS] Intel SSD

[Johnny Hughes]

On 11/18/2015 09:51 AM, Eero Volotinen wrote:
> strace -f -e open software_binary might help, but I have noticed that
> Centos is not really 100% binary compatible in some cases.

CentOS Linux is not 100% bit for bit compatible with RHEL in ANY cases :)

CentOS and RHEL are built from mostly the same source code (we remove RH
trademarks and take out RHN update pieces).

But RHEL source code is rebuilt on RHEL in the Red Hat isolated build
system .. and CentOS Linux is built CentOS in our isolated build system.

Red Hat does not always release everything in their build system (they
might do 2 or 3 versions before they release something).  We only have
things they released (and we built) in our build system.

That means almost every single compiled binary file is 'not exactly' the
same (on a bit for bit basis) when compared between CentOS Linux and RHEL.


Thanks,
Johnny Hughes

> 
> 
> 
> --
> Eero
> 
> 2015-11-18 17:42 GMT+02:00 Matt Garman :
> 
>> I always tell vendors I'm using RHEL, even though we're using CentOS.
>> If you say CentOS, some vendors immediately throw up their hands and
>> say "unsupported" and then won't even give you the time of day.
>>
>> A couple tricks for fooling tools into thinking they are on an actual
>> RHEL system:
>> 1. Modify /etc/redhat-release to say RedHat Enterprise Linux or
>> whatever the actual RHEL systems have
>> 2. Similarly modify /etc/issue
>>
>> Another tip that has proven successful: run the vendor tool under
>> strace.  Sometimes you can get an idea of what it's trying to do and
>> why it's failing.  This is exactly what we did to determine why a
>> vendor tool wouldn't work on CentOS.  We had modified
>> /etc/redhat-release (as in (1) above), but forgot about /etc/issue.
>> Strace showed the program existing immediately after an open() call to
>> /etc/issue.
>>
>> Good luck!
>>
>>
>>
>>
>> On Wed, Nov 18, 2015 at 9:24 AM, Michael Hennebry
>>  wrote:
>>> On Wed, 18 Nov 2015, Birta Levente wrote:
>>>
 I have a supermicro server, motherboard is with C612 chipset and beside
 that with LSI3108 raid controller integrated.
 Two Intel SSD DC S3710 200GB.
 OS: Centos 7.1 up to date.

 My problem is that the Intel SSD Data Center Tool (ISDCT) does not
 recognize the SSD drives when they connected to the standard S-ATA
>> ports on
 the motherboard, but through the LSI raid controller is working.

 Does somebody know what could be the problem?

 I talked to the Intel support and they said the problem is that Centos
>> is
 not supported OS ... only RHEL 7.
 But if not supported should not work on the LSI controlled neither.
>>>
>>>
>>> Perhaps the tool looks for the string RHEL.
>>> My recollection is that when IBM PC's were fairly new,
>>> IBM used that trick with some of its software.
>>> To work around that, some open source developers used the string "not
>> IBM".
>>> I think this was pre-internet, so google might not work.
>>>
>>> If it's worth the effort, you might make another "CentOS" distribution,
>>> but call it "not RHEL".
>>>
>>> --
>>> Michael   henne...@web.cs.ndsu.nodak.edu
>>> "Sorry but your password must contain an uppercase letter, a number,
>>> a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
>>>  --
>> someeecards
>>> ___
>>> CentOS mailing list
>>> CentOS@centos.org
>>> https://lists.centos.org/mailman/listinfo/centos
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
> 




signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS-announce] CESA-2015:2086 Important CentOS 6 java-1.6.0-openjdk Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2015:2086 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-2086.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
e8af0bccd304323e1aa843eb766e70c14e41f10d37f36a10a119a2e5a0a29d99  
java-1.6.0-openjdk-1.6.0.37-1.13.9.4.el6_7.i686.rpm
1d5d0435df46b38dd76625bf74d399130fc880d253cce65cc56af02ae95369f6  
java-1.6.0-openjdk-demo-1.6.0.37-1.13.9.4.el6_7.i686.rpm
a1fb61dd21d3c39e76dd4b586616a0eb9f0e7385f4ffc0646b64caab8e39e023  
java-1.6.0-openjdk-devel-1.6.0.37-1.13.9.4.el6_7.i686.rpm
e6ef8834495a00342c6795c6350e481121ec1679a11faf111974a8e1cfb513e9  
java-1.6.0-openjdk-javadoc-1.6.0.37-1.13.9.4.el6_7.i686.rpm
8746d8d277b92216022f72bde731eb208376ef80189ff9b537b39818af6191a4  
java-1.6.0-openjdk-src-1.6.0.37-1.13.9.4.el6_7.i686.rpm

x86_64:
5aa22726ce93be62ff0833e0ff0a2258dd44b36968f9787c106ce7abac9de92b  
java-1.6.0-openjdk-1.6.0.37-1.13.9.4.el6_7.x86_64.rpm
5fa7345e069a5d00c0257e1559ec8fe97a2f828306d5538a22c773f800c07181  
java-1.6.0-openjdk-demo-1.6.0.37-1.13.9.4.el6_7.x86_64.rpm
ed681b21bbcb93543dffc3f82ed8bd93226ad1cdd640d4300c3656630664bce6  
java-1.6.0-openjdk-devel-1.6.0.37-1.13.9.4.el6_7.x86_64.rpm
c83158d7a0c733b44279ccb95a66a87c137441e1a47c55be94d057e667289a23  
java-1.6.0-openjdk-javadoc-1.6.0.37-1.13.9.4.el6_7.x86_64.rpm
a248aefa9bc1c02541ff465f6eb6f98a32072b6fef348adcdf924fd051d06151  
java-1.6.0-openjdk-src-1.6.0.37-1.13.9.4.el6_7.x86_64.rpm

Source:
5d935ad8df489bd9c6dcf51e5fa0cdb2eda17face6eccce30cccf8fbfd0312f3  
java-1.6.0-openjdk-1.6.0.37-1.13.9.4.el6_7.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

[CentOS-announce] CESA-2015:2086 Important CentOS 7 java-1.6.0-openjdk Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2015:2086 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-2086.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
dbde32b3ea0f1870bd997de2978ae16c39b5702982e26641b1361e525d836a2a  
java-1.6.0-openjdk-1.6.0.37-1.13.9.4.el7_1.x86_64.rpm
8c10f117b441e78024068c7d8aebdbe23ed46a772e739c2ec6c8fc5a9bd19300  
java-1.6.0-openjdk-demo-1.6.0.37-1.13.9.4.el7_1.x86_64.rpm
b9cc50e5cc098bd8cdec6d2c57ed9957b84b17140b20c4dff86116a321fb5743  
java-1.6.0-openjdk-devel-1.6.0.37-1.13.9.4.el7_1.x86_64.rpm
d7555996e4355cfd7f42227a7dcbc82760cb92dd0387c0e8943a62d58a96a85c  
java-1.6.0-openjdk-javadoc-1.6.0.37-1.13.9.4.el7_1.x86_64.rpm
242c990b1fb3bbbec7ae853077c9785752d1a11364241070004ed245a84fd564  
java-1.6.0-openjdk-src-1.6.0.37-1.13.9.4.el7_1.x86_64.rpm

Source:
5ca8bb4d945891ee068baac317351d7a571cf7dbf8e28f94fb1b2e2679580aeb  
java-1.6.0-openjdk-1.6.0.37-1.13.9.4.el7_1.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

[CentOS-docs] Self Introduction

[OoyamaYosiyuki]

 *

   your /FirstnameLastname/ username

FirstnameLastname=OoyamaYosiyuki
username=OoyamaYosiyuki

 * the proposed subject of your Wiki contribution(s)

I want to "transulation".  I want to transulation to japanese.

 * the proposed location of your Wiki contribution(s)

I want to contribute "Japanese" CentOS Wiki

___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-virt] CentOS 6 Xen package update (including XSA-156)

[Manuel Wolfshant]

On 11/18/2015 02:08 PM, Pasi Kärkkäinen wrote:

Hello,

On Sun, Nov 15, 2015 at 06:42:18PM +0200, Pasi Kärkkäinen wrote:

On Sun, Nov 15, 2015 at 02:04:58PM +0200, Pasi Kärkkäinen wrote:

On Thu, Nov 12, 2015 at 02:00:27PM +, George Dunlap wrote:

So going forward, we're moving the CentOS 6 Xen packages from the
custom "xen4" repos that were introduced several years ago, to repos
based on its position as a sub-project of the Virt Sig.  That will
make things consistent between all the sigs, as well as between CentOS
6 and 7 Xen packages.

Unfortunately, XSA-156 came up rather suddenly and is a bit blocked by
this transition.

So please help us test the new repository structure, so that we can
with conscience push the updates to xen4 users in general.


Seems to work for me!



Except now on another system I see this problem:


Anyone else seeing this libvirt-python problem with virt-manager and/or 
virt-viewer ?

(happens on a freshly installed system, so no earlier libvirt rpms installed)

It tries to install half of the OS, but it works for me.  It seems that 
your yum does not like that you already have 
libvirt-client-1.2.15-3.el6.x86_64. Mine is happy to bring in 
libvirt-{python,client}-0.10.2-54.el6_7.2.x86_64 from updates


wolfy



# yum install virt-manager
..
..
..

--> Finished Dependency Resolution
Error: Package: libvirt-python-0.10.2-54.el6_7.2.x86_64 (updates)
Requires: libvirt.so.0(LIBVIRT_PRIVATE_0.10.2)(64bit)
Available: libvirt-client-0.10.2-54.el6.x86_64 (base)
libvirt.so.0(LIBVIRT_PRIVATE_0.10.2)(64bit)
Available: libvirt-client-0.10.2-54.el6_7.2.x86_64 (updates)
libvirt.so.0(LIBVIRT_PRIVATE_0.10.2)(64bit)
Installed: libvirt-client-1.2.15-3.el6.x86_64 (@centos-virt-xen)
Not found
  You could try using --skip-broken to work around the problem
  You could try running: rpm -Va --nofiles --nodigest


Are we missing a build of libvirt-python 1.2.15 package?



___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 6 Xen package update (including XSA-156)

[Pasi Kärkkäinen]

On Wed, Nov 18, 2015 at 02:20:49PM +0200, Manuel Wolfshant wrote:
> On 11/18/2015 02:08 PM, Pasi Kärkkäinen wrote:
> >Hello,
> >
> >On Sun, Nov 15, 2015 at 06:42:18PM +0200, Pasi Kärkkäinen wrote:
> >>On Sun, Nov 15, 2015 at 02:04:58PM +0200, Pasi Kärkkäinen wrote:
> >>>On Thu, Nov 12, 2015 at 02:00:27PM +, George Dunlap wrote:
> So going forward, we're moving the CentOS 6 Xen packages from the
> custom "xen4" repos that were introduced several years ago, to repos
> based on its position as a sub-project of the Virt Sig.  That will
> make things consistent between all the sigs, as well as between CentOS
> 6 and 7 Xen packages.
> 
> Unfortunately, XSA-156 came up rather suddenly and is a bit blocked by
> this transition.
> 
> So please help us test the new repository structure, so that we can
> with conscience push the updates to xen4 users in general.
> 
> >>>Seems to work for me!
> >>>
> >>>
> >>Except now on another system I see this problem:
> >>
> >Anyone else seeing this libvirt-python problem with virt-manager and/or 
> >virt-viewer ?
> >
> >(happens on a freshly installed system, so no earlier libvirt rpms installed)
> >
> It tries to install half of the OS, but it works for me.  It seems
> that your yum does not like that you already have
> libvirt-client-1.2.15-3.el6.x86_64. Mine is happy to bring in
> libvirt-{python,client}-0.10.2-54.el6_7.2.x86_64 from updates
> 

libvirt-{python,client}-0.10.2-54.el6_7.2.x86_64 are the centos core packages,
while the libvirt-client-1.2.15-3.el6.x86_64 is the Virt SIG provided one,
which has Xen support enabled.

So I need the 1.2.15-3 versions, but it seems libvirt-python is not included in 
the Virt SIG built ones..

So that's an issue/problem..


-- Pasi


> wolfy
> 
> 
> >># yum install virt-manager
> >>..
> >>..
> >>..
> >>
> >>--> Finished Dependency Resolution
> >>Error: Package: libvirt-python-0.10.2-54.el6_7.2.x86_64 (updates)
> >>Requires: libvirt.so.0(LIBVIRT_PRIVATE_0.10.2)(64bit)
> >>Available: libvirt-client-0.10.2-54.el6.x86_64 (base)
> >>libvirt.so.0(LIBVIRT_PRIVATE_0.10.2)(64bit)
> >>Available: libvirt-client-0.10.2-54.el6_7.2.x86_64 (updates)
> >>libvirt.so.0(LIBVIRT_PRIVATE_0.10.2)(64bit)
> >>Installed: libvirt-client-1.2.15-3.el6.x86_64 (@centos-virt-xen)
> >>Not found
> >>  You could try using --skip-broken to work around the problem
> >>  You could try running: rpm -Va --nofiles --nodigest
> >>
> >>
> >>Are we missing a build of libvirt-python 1.2.15 package?
> 
> 
> ___
> CentOS-virt mailing list
> CentOS-virt@centos.org
> https://lists.centos.org/mailman/listinfo/centos-virt
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS] Intel SSD

[Eero Volotinen]

What is Intel SSD Data Center Tool (ISDCT) ? Does Linux kernel detect disk
on sata ports?

Supported usually means that they have tested it and they can say that it
works.. Many of hardware still works as linux kernel support
lots of drivers -- even they are not officially supported by vendor.

--
Eero

2015-11-18 16:25 GMT+02:00 Birta Levente :

> Hi
>
> I have a supermicro server, motherboard is with C612 chipset and beside
> that with LSI3108 raid controller integrated.
> Two Intel SSD DC S3710 200GB.
> OS: Centos 7.1 up to date.
>
> My problem is that the Intel SSD Data Center Tool (ISDCT) does not
> recognize the SSD drives when they connected to the standard S-ATA ports on
> the motherboard, but through the LSI raid controller is working.
>
> Does somebody know what could be the problem?
>
> I talked to the Intel support and they said the problem is that Centos is
> not supported OS ... only RHEL 7.
> But if not supported should not work on the LSI controlled neither.
>
> Thanks,
>
> --
>Levi
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Intel SSD

[Birta Levente]

On 18/11/2015 16:37, Eero Volotinen wrote:

What is Intel SSD Data Center Tool (ISDCT) ?


" This tool provides a command line interface for interacting with and 
issuning commands to Intel SSD Data Center devices. It is intended to 
configure and check the state of Intel PCIe SSDs and SATA SSDs for a 
production environment. "




Does Linux kernel detect disk on sata ports?



Of course they detected by kernel. They work very well, just this tool 
does not recognize them.





Supported usually means that they have tested it and they can say that
it works.. Many of hardware still works as linux kernel support
lots of drivers -- even they are not officially supported by vendor.

--
Eero

2015-11-18 16:25 GMT+02:00 Birta Levente >:

Hi

I have a supermicro server, motherboard is with C612 chipset and
beside that with LSI3108 raid controller integrated.
Two Intel SSD DC S3710 200GB.
OS: Centos 7.1 up to date.

My problem is that the Intel SSD Data Center Tool (ISDCT) does not
recognize the SSD drives when they connected to the standard S-ATA
ports on the motherboard, but through the LSI raid controller is
working.

Does somebody know what could be the problem?

I talked to the Intel support and they said the problem is that
Centos is not supported OS ... only RHEL 7.
But if not supported should not work on the LSI controlled neither.

Thanks,

--
Levi
___
CentOS mailing list
CentOS@centos.org 
https://lists.centos.org/mailman/listinfo/centos





--
   Levi
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Intel SSD

[Birta Levente]

Hi

I have a supermicro server, motherboard is with C612 chipset and beside 
that with LSI3108 raid controller integrated.

Two Intel SSD DC S3710 200GB.
OS: Centos 7.1 up to date.

My problem is that the Intel SSD Data Center Tool (ISDCT) does not 
recognize the SSD drives when they connected to the standard S-ATA ports 
on the motherboard, but through the LSI raid controller is working.


Does somebody know what could be the problem?

I talked to the Intel support and they said the problem is that Centos 
is not supported OS ... only RHEL 7.

But if not supported should not work on the LSI controlled neither.

Thanks,

--
   Levi
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Intel SSD

[Eero Volotinen]

2015-11-18 16:48 GMT+02:00 Birta Levente :

> On 18/11/2015 16:37, Eero Volotinen wrote:
>
>> What is Intel SSD Data Center Tool (ISDCT) ?
>>
>
> " This tool provides a command line interface for interacting with and
> issuning commands to Intel SSD Data Center devices. It is intended to
> configure and check the state of Intel PCIe SSDs and SATA SSDs for a
> production environment. "
>
>
> Does Linux kernel detect disk on sata ports?
>>
>>
> Of course they detected by kernel. They work very well, just this tool
> does not recognize them.
>
>
Well. You are using it on non supported configuration? You should try it
with official RHEL, it might work or not. If not, then open support ticket.

--
Eero
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] OT: Replacing Venerable NAS

[John R Pierce]

On 11/18/2015 1:25 PM, Warren Young wrote:

My point is that unreliable NAS/RAID systems*require*  this dual redundancy, 
whereas a reliable system only needs normal backups, that being the sort where 
you rarely go back and pull more than a few files at a time.


well, at the sub $1000 price point of the typical SOHO NAS box, you're 
not going to find high 'reliable' systems, with redundant power 
supplies, dual storage controllers, and everything else that goes along 
with 'high availability'.even my fairly well built $7000-ish 2U 
servers in my development lab, if the motherboard or a CPU chip fails?  
they are offline until repaired, if they were mission critical, I'd need 
pairs of everything..   if a network switch fails?  yeah, I didn't 
implement fully redundant multipath networking either.


the /really/ hard one when rolling your own highly redundant systems 
with high data integrity needed for things like transactional database 
servers, is implementing redundant storage controllers with shared 
writeback cache...   you pretty much have to get into EMC class hardware 
for this level of reliability with data integrity and performance.   and 
thats /really/ expensive stuff.



--
john r pierce, recycling bits in santa cruz

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Linux ate my RAM...

[m . roth]

Warren Young wrote:
> On Nov 18, 2015, at 1:20 PM, Kwan Lowe  wrote:
>>
>> Because of caching, from VMWare's perspective, all Linux memory is
>> being "used”.
>
> Nope.  VMware’s memory ballooning feature purposely keeps some of the
> guest’s RAM locked away from the kernel.  This is where RAM comes from
> when another guest needs more physical RAM than it currently has access
> to:
>
>   https://blogs.vmware.com/virtualreality/2008/10/memory-overcomm.html
>
> There are downsides.

> Another, of course, is that oversubscription risks running out of RAM, if
> all of the guests decide to try and use all the RAM the host told them it
> gave.  All of the guests end up being forced to deflate their balloons
> until there is no more balloon memory left.

Note that in '09, VMWare was advising us (where I was working at the time)
to not go over 2 or 2.5 times real memory

  mark

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Linux ate my RAM...

[Itamar Reis Peixoto]

On 2015-11-18 19:41, Warren Young wrote:

On Nov 18, 2015, at 1:20 PM, Kwan Lowe  wrote:


try systemd-nspawn and use it instead of virtualizing, will save you 
some bits of memory.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] OT: Replacing Venerable NAS

[Warren Young]

On Nov 18, 2015, at 2:58 PM, m.r...@5-cent.us wrote:
> 
>>> On 11/18/2015 11:55 AM, Warren Young wrote:
 It’s rather annoying to buy a NAS, then later realize you need to
 buy*another*  NAS as a mirror in case the first one roaches itself.
>>> 
> Which is why, for home, I went to MicroCenter and bought, for about $30
> USD, a hot swap drive bay that fits in my mid-sized tower, and a 2TB
> drive. Doesn't even need a sled….

That’s great if your volume fits onto a single hard disk.  I use 4-5 bay NASes 
because I have more than 8 TiB under management, and want volume level 
redundancy on top of that.  That means 4+ 4 TiB disks, at minimum, which means 
I need another like-kind NAS to backstop the first.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Linux ate my RAM...

[Warren Young]

On Nov 18, 2015, at 1:20 PM, Kwan Lowe  wrote:
> 
> Because of caching, from VMWare's perspective, all Linux memory is
> being "used”.

Nope.  VMware’s memory ballooning feature purposely keeps some of the guest’s 
RAM locked away from the kernel.  This is where RAM comes from when another 
guest needs more physical RAM than it currently has access to:

  https://blogs.vmware.com/virtualreality/2008/10/memory-overcomm.html

There are downsides.

One is that pages locked up by the balloon driver aren’t being used by Linux’s 
buffer cache.  But on the other hand, the hypervisor itself fulfills some of 
that role, which is why rebooting a VM guest is typically much faster than 
rebooting the same OS on the same bare hardware.

Another, of course, is that oversubscription risks running out of RAM, if all 
of the guests decide to try and use all the RAM the host told them it gave.  
All of the guests end up being forced to deflate their balloons until there is 
no more balloon memory left.

> The increase in vm density is an acceptable tradeoff.

Instead of oversubscribing the real RAM of the system, consider starting and 
stopping VMs at need, so that only a subset of them are running at a given 
time.  That lets you host more VMs underneath a given hypervisor than would run 
simultaneously, as long as you don’t need too many of the VMs at once.

This patterns works well for a suite of test VMs, since you probably don’t need 
to test all configurations in parallel.  You might need only one or two of the 
guests at any given time.

> 1) What options are available in CentOS to limit the page cache?

Again, you should not be tuning the Linux’s virtual memory manager to make the 
VM host happy.  That’s one of the jobs VMware Tools performs.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-es] KVM

[A.Rubio]

Desde la linea de comando con este sencillo comando.

qemu-img resize imagen.img +20GB

Luego solo te toca extender el volumen desde el sistema operativo.

El mié, 18-11-2015 a las 18:50 -0300, David González Romero escribió:
> Saludos Lista:
> 
> En una maquina virtual que cree le di un tamaño de 500Gb, ahora
> preciso aumentar ese tamaño. Es posible realizar esa operación con con
> el Hypervisor de KVM-Qemu, virt-manager?
> 
> Saludos,
> David
> ___
> CentOS-es mailing list
> CentOS-es@centos.org
> https://lists.centos.org/mailman/listinfo/centos-es


___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

Re: [CentOS] OT: Replacing Venerable NAS

[m . roth]

Warren Young wrote:
> On Nov 18, 2015, at 1:01 PM, John R Pierce  wrote:
>>
>> On 11/18/2015 11:55 AM, Warren Young wrote:
>>> It’s rather annoying to buy a NAS, then later realize you need to
>>> buy*another*  NAS as a mirror in case the first one roaches itself.
>>> Isn’t that what redundant storage is supposed to avoid?
>>
>> no, RAID is purely availability when faced with single or double drive
>> failure, nothing else.   classic raid is most certainly NOT about data
>> integrity, as the raid stripes aren't checksummed, they assume hardware
>> data integrity.
>
> I knew I’d get some kind of lecture like that.
>
> Look, I know RAID/ZFS is not a backup.  My point is simply that if you
> need to keep a mirror of your file server just in case it roaches itself,
> what you have there is dual redundancy, not a backup.  You need an offline
> backup *on top* of that, for the same reason that all hot mirrors are not
> backups.

Which is why, for home, I went to MicroCenter and bought, for about $30
USD, a hot swap drive bay that fits in my mid-sized tower, and a 2TB
drive. Doesn't even need a sled

   mark

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-es] KVM

[David González Romero]

Y si mi imagen la es .qcow2 se hace igual?

Saludos,
David

El día 18 de noviembre de 2015, 19:05, A.Rubio  escribió:
> Desde la linea de comando con este sencillo comando.
>
> qemu-img resize imagen.img +20GB
>
> Luego solo te toca extender el volumen desde el sistema operativo.
>
> El mié, 18-11-2015 a las 18:50 -0300, David González Romero escribió:
>> Saludos Lista:
>>
>> En una maquina virtual que cree le di un tamaño de 500Gb, ahora
>> preciso aumentar ese tamaño. Es posible realizar esa operación con con
>> el Hypervisor de KVM-Qemu, virt-manager?
>>
>> Saludos,
>> David
>> ___
>> CentOS-es mailing list
>> CentOS-es@centos.org
>> https://lists.centos.org/mailman/listinfo/centos-es
>
>
> ___
> CentOS-es mailing list
> CentOS-es@centos.org
> https://lists.centos.org/mailman/listinfo/centos-es
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

Re: [CentOS-es] KVM

[A.Rubio]

si

El mié, 18-11-2015 a las 19:19 -0300, David González Romero escribió:
> Y si mi imagen la es .qcow2 se hace igual?
> 
> Saludos,
> David
> 
> El día 18 de noviembre de 2015, 19:05, A.Rubio  escribió:
> > Desde la linea de comando con este sencillo comando.
> >
> > qemu-img resize imagen.img +20GB
> >
> > Luego solo te toca extender el volumen desde el sistema operativo.
> >
> > El mié, 18-11-2015 a las 18:50 -0300, David González Romero escribió:
> >> Saludos Lista:
> >>
> >> En una maquina virtual que cree le di un tamaño de 500Gb, ahora
> >> preciso aumentar ese tamaño. Es posible realizar esa operación con con
> >> el Hypervisor de KVM-Qemu, virt-manager?
> >>
> >> Saludos,
> >> David
> >> ___
> >> CentOS-es mailing list
> >> CentOS-es@centos.org
> >> https://lists.centos.org/mailman/listinfo/centos-es
> >
> >
> > ___
> > CentOS-es mailing list
> > CentOS-es@centos.org
> > https://lists.centos.org/mailman/listinfo/centos-es
> ___
> CentOS-es mailing list
> CentOS-es@centos.org
> https://lists.centos.org/mailman/listinfo/centos-es


___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

[CentOS] C7: How to configure raid at install time

[Fred Smith]

Hi all!

I'm still on C6. I'm using a RAID1 configuration (Linux software RAID)
and I'd like to either use the same one, or possibly configure it on
new drives (larger) when I upgrade to C7. (I'm really feeling the need
to move off C6.)

But it isn't at all obvious how one would do a new RAID1 setup in
Anaconda, and I don't find any user reports or other info on this
in the WIKI or forums (fora, properly, if I recall my high school
Latin).

Can anyone provide (or give pointers to) a good recipe for doing this?

thanks!

Fred
-- 
 Fred Smith -- fre...@fcshome.stoneham.ma.us 
Do you not know? Have you not heard? 
The LORD is the everlasting God, the Creator of the ends of the earth. 
  He will not grow tired or weary, and his understanding no one can fathom.
- Isaiah 40:28 (niv) -
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] C7: How to configure raid at install time

[Devin Reade]

--On Wednesday, November 18, 2015 11:07:12 PM -0500 Fred Smith 
 wrote:



But it isn't at all obvious how one would do a new RAID1 setup in
Anaconda


Don't feel bad.  The abortion that is the RHEL/CentOS 7 graphical
install interface is far too dumbed-down to be easily usable by anyone
that understands what is going on under the covers.  Oh, the irony.


Can anyone provide (or give pointers to) a good recipe for doing this?


A quick google brought up the following link that (looking just at the
disk portion) appears to be mostly correct, and should give you the
magic incantation:



The one thing I would point out regarding the above link is that despite
conventional UNIX wisdom, *don't* put /usr on a separate filesystem
in CentOS 7.  Thank you RedHat

Flames to /dev/null.

Devin

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] OT: Replacing Venerable NAS

[Devin Reade]

--On Wednesday, November 18, 2015 10:31:36 AM -0500 Tim Evans 
 wrote:



Would like to hear recommendations here.  Besides the ReadyNAS, I have
worked with a Thecus NAS (don't recall model). What are the features I
should look at?


For reasons that others have already touched on, I like FreeNAS, as
long as you're using the base system.  I have one that is running jails
so that I can run some custom software on the same box, and I think
when possible I'd prefer to keep such software off on another machine.
(In this case though, it's a situation of keeping the program as
close as possible to the data to minimize network traffic.)

I have one FreeNAS running on an HP Microserver Gen 8 (four bays,
RAID-Z2 double redundancy, which means two disks worth of usable
space).  The OS is on an internal memory stick, the spinning drives
are all data drives.  It's a nice solid piece of hardware and suitable
for home & small office.

I also have FreeNAS running in a larger system which is based on an
Intel DBS1200V3RPS motherboard, a Xeon processor, lots of ECC memory,
and 36TB of disk.  (6 SATA connectors on board, and 6TB drives were
the largest available at the time; it will get expanded soon via an
add-on RAID card running in JBOD mode.)  It's a solid system.

FreeNAS will do almost anything you'd expect of a storage device.
I'd suggest downloading it and trying it on a spare piece of (64bit)
hardware, but unless it's using ECC memory don't trust your production
data with it.  I've exercised the disk replacement process once and
it went flawlessly.  ('Twas far too early, but it was probably a
manufacturing flaw given the early failure.)

If you're planning on doing data encryption or data duplication, make
sure you read into specific hardware requirements for that before you
go and buy stuff.

And given which mailing list we're on, I'll add in that CentOS 5, 6,
and 7 NFS clients talk to it just fine.  (And OS-X clients as well,
with both NFS and AFP. I don't have windows clients, but they shouldn't
be an issue.)

Devin

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS-es] KVM

[David González Romero]

Saludos Lista:

En una maquina virtual que cree le di un tamaño de 500Gb, ahora
preciso aumentar ese tamaño. Es posible realizar esa operación con con
el Hypervisor de KVM-Qemu, virt-manager?

Saludos,
David
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

Re: [CentOS] OT: Replacing Venerable NAS

[Warren Young]

On Nov 18, 2015, at 1:01 PM, John R Pierce  wrote:
> 
> On 11/18/2015 11:55 AM, Warren Young wrote:
>> It’s rather annoying to buy a NAS, then later realize you need to 
>> buy*another*  NAS as a mirror in case the first one roaches itself.  Isn’t 
>> that what redundant storage is supposed to avoid?
> 
> 
> no, RAID is purely availability when faced with single or double drive 
> failure, nothing else.   classic raid is most certainly NOT about data 
> integrity, as the raid stripes aren't checksummed, they assume hardware data 
> integrity.

I knew I’d get some kind of lecture like that.

Look, I know RAID/ZFS is not a backup.  My point is simply that if you need to 
keep a mirror of your file server just in case it roaches itself, what you have 
there is dual redundancy, not a backup.  You need an offline backup *on top* of 
that, for the same reason that all hot mirrors are not backups.

My point is that unreliable NAS/RAID systems *require* this dual redundancy, 
whereas a reliable system only needs normal backups, that being the sort where 
you rarely go back and pull more than a few files at a time.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos