Hi,
I'm new to CentOS and also on the list, since I usually work with Debian. My
problem is as follows:
I have a NAS where users connect to do their backups. Each user has a folder
shared where only he can enter. Multiple users get connected from a CentOS 5.7
to the NAS, each in its shared fol
Le 23/11/2011 12:11, Guitart Francesc a écrit :
> Hi,
>
> I'm new to CentOS and also on the list, since I usually work with Debian. My
> problem is as follows:
>
> I have a NAS where users connect to do their backups. Each user has a folder
> shared where only he can enter. Multiple users get con
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ..
Hello all,
I am trying to create a corosync/pacemaker cluster using CentOS 6.0.
However, I'm having a great deal of difficulty doing so.
Corosync has a valid configuration file and an authkey has been generated.
When I run /etc/init.d/corosync I see that only corosync is started.
>From experienc
I tried several ways but still no help. The following are the output (stock
Centos 6 2.6.32-71.29.1.el6.x86_64 kernel), grub works fine and it located
kernel and initial ramdisk. but kernel booting faied at the very beginning...
Any suggestions are more than appreciated.
--
On 11/23/2011 11:40 AM, Robinson Tiemuqinke wrote:
> I tried several ways but still no help. The following are the output (stock
> Centos 6 2.6.32-71.29.1.el6.x86_64 kernel), grub works fine and it located
> kernel and initial ramdisk. but kernel booting faied at the very beginning...
>
> Any su
Hi Johnny,
Thanks a lot. I'll upgrade kernel to the cr repository, and give it a try now.
--Guolin
From: Johnny Hughes
To: centos@centos.org
Sent: Wednesday, November 23, 2011 9:55 AM
Subject: Re: [CentOS] Any ideas?? -- Re: EC2 compatible kernel for centos
On 11/23/11 3:11 AM, Guitart Francesc wrote:
> here I connect through SMB port 445
why in dogs name are you using SMB, a Microsoft Windows protocol, for
Unix to NAS file sharing? Unix systems should use NFS for file
sharing. netbios is a tangled mess of poorly planned protocols with
extensi
Hey folks,
I looked back through the list archives and there are surprisingly few
threads with "SSD" in the subject.
In my new job I've been handed over a number of things that were
outstanding with the previous Sys Admin, and one of them was an SSD
that was suspect. I just plugged it into a di
I've tried with cr kernel, not it moves much faster but still fails -- fails at
the partition failure, this setup is S3 backed image.
root (hd0)
Filesystem type is ext2fs, using whole disk
kernel /boot/vmlinuz-2.6.32-131.17.1.el6.x86_64 ro root=/dev/sda1 rd_NO_LUKS rd
_NO_LVM rd_NO_MD rd_NO_DM L
Hi,
Did you configure corosync ?
Normally corosync starts pacemaker, which in turn starts the heartbeat
deamons.
But you have to configure the latter using for example a pcmk file with
configuration in /etc/corosync/conf.d/ (from the top of my head).
I normally use :
http://www.clusterlabs.org/do
Robinson Tiemuqinke wrote:
> I've tried with cr kernel, not it moves much faster but still fails --
> fails at the partition failure, this setup is S3 backed image.
>
> root (hd0)
> Filesystem type is ext2fs, using whole disk
> kernel /boot/vmlinuz-2.6.32-131.17.1.el6.x86_64 ro root=/dev/sda1
> rd
Hi Mark,
Would you mind to elaborate your steps of fixing?
I'm using 'yum groupinstall --installroot=/ ...' method, then
Install(not update) the newest kernel from cr/ repository.
Did you rebuild initial ramdisk? If so, what's your command to do that? Thanks
a lot.
--Rob
__
Hi, Rob,
Robinson Tiemuqinke wrote:
>
> Would you mind to elaborate your steps of fixing?
>
> I'm using 'yum groupinstall --installroot=/ ...' method, then
> Install(not update) the newest kernel from cr/ repository.
>
> Did you rebuild initial ramdisk? If so, what's your command to do that?
> T
Hi Mark, John and all,
Finally got it work! hew..
The last part which makes the difference is change the /dev/sda1 to /dev/xvde1
in files /boot/grub/menu.lst and /etc/fstab. the file system type set to 'ext2'
(from ext3) for /dev/xvde1 as well -- this is a S3 backed AMI image. There is
Am 23.11.2011 14:24 schrieb "Michel van Deventer" :
>
> Hi,
>
> Did you configure corosync ?
> Normally corosync starts pacemaker, which in turn starts the heartbeat
> deamons.
> But you have to configure the latter using for example a pcmk file with
> configuration in /etc/corosync/conf.d/ (from t
16 matches
Mail list logo