open-sharedroot-users — Discussion of user issues and wishes within the open-sharedroot project

Re: [OSR-users] New Preview RPMs for next Release Candidate of comoonics-bootimage

[Marc G. <gr...@at...>]

Hello *,
I finished the last implementations and bugfixes of the (nearly) final release 
candidate of the new comoonics tools (Version 4.5 including 
comoonics-bootimage).
Here are the last relevant changes:

* Some bugfixes in hardware detection specially with udev renaming nics and 
therefore "deadlocking" udevd (timeout gets called)
* Bugfixes in powering up nics. They might be called multiple times (i.e. when 
using bridging and bonding and vlans at once ;-) )
* Verified ocfs2 with RHEL5 and ocfs2 with SLES10
* Updated the lite option in mkinitrd <gordans approch> to be more general and 
not necessarily need "lsmod".
* Implemented filters to globally remove files from initrd (Gordan's idea)
* Implemented an update feature in the initrd (see 
https://bugzilla.atix.de/show_bug.cgi?id=340). That's a cool one. Updating an 
initrd within seconds.
* Fixed bugs (338, 331, ..)

Some thoughts to sum up:
1. It is now possible to use the lite version of mkinitrd. It should reduce 
the size of the initrd by 50%.
Use -L if you want to include all loaded modules or if you need more modules 
use either -M <modulename> or specify 
in /etc/comoonics/comoonics-bootimage.cfg
2. The mkinitrd -U updates an existing initrd an therefore also speeds up the 
initrd building. With -A <kernelversion> and -D <kernelversion> even kernels 
can be exchanged in the same initrd.

So that's it.

Open issues before having a proper RC is:
Retest with SLES10(ocfs2/nfs) and test with FC10(nfs/gfs2).

That's it, let me know what you think and have fun.

NOTE: Those packages are NOT YET production ready. And they might include
bugs as they did not undergo the Q&A. So use them at your own risc.

P.S. And may the root always be shared! ;-)

On Tuesday 10 February 2009 20:53:18 Marc Grimme wrote:
> Hello *,
> finally we got the first stage of the new version of the osr cluster suite
> in the preview channel. This will be the first release candidate for the
> next productive channel.
>
> NOTE: Those packages are NOT YET production ready. And they might include
> bugs as they did not undergo the Q&A. So use them at your own risc.
>
> 2nd NOTE: Those packages were only tested with OSR<RHEL5> clusters based on
> GFS or NFS. OSR<SLES10/ocfs2>,OSR<Fedora/gfs2|nfs> and OSR<RHEL5/ocfs2>
> will be tested next. This means you shouldn't use those packages with ocfs2
> as rootfilesystem.
>
> As this is only a preview update I will sum up the most important changes
> not automated:
>
> - Rewritten hardwaredetection: https://bugzilla.atix.de/show_bug.cgi?id=325
> - Usability review: https://bugzilla.atix.de/show_bug.cgi?id=323
> - Support for breakpoints in bootprocess
> - Break shell will always continue the bootprocess when exited
> - Bootparameters may be overwritten in Breakshell
> - Rootfs Check with bootparameter rootfsck (use with care and up to now
> only with GFS)
> - NFS OSR will not start scsi detection
> - Preview support for OSR on fedora (NFS)
> - Preview support for OSR<NFS4> without authentication
> - Preview support for OSR<RHEL5 with localfs>
> - Many small bugfixes
> Patches from Gordan Bobic (all preview status):
> - glusterfs support
> - Software RAID with md support
> - diet patch (new option to mkinitrd <-l> to make initrd smaller)
>
> Please let me know what you think
>
> Thanks
> Marc
>
> P.S. May the root always be shared! ;-)
>
> --
> Gruss / Regards,
>
> Marc Grimme
> http://www.atix.de/               http://www.open-sharedroot.org/
>
>
> ---------------------------------------------------------------------------
>--- Create and Deploy Rich Internet Apps outside the browser with
> Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing
> skills and code to build responsive, highly engaging applications that
> combine the power of local resources and data with the reach of the web.
> Download the Adobe AIR SDK and Ajax docs to start building applications
> today-http://p.sf.net/sfu/adobe-com
> _______________________________________________
> Open-sharedroot-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/open-sharedroot-users



-- 
Gruss / Regards,

Marc Grimme
http://www.atix.de/               http://www.open-sharedroot.org/

[OSR-users] Problem with OCFS2

[Stefano E. <ste...@so...>]

Hi Marc,


I succeed to get on single-node cluster with the Grub on external  
partition.
Now I have a doubt, how do I prepare the second node to add it to the  
cluster ?
What remains unclear to me is what I do to the infrastructure !
Thanks

Ing. Stefano Elmopi
Gruppo Darco - Area ICT Sistemi
Via Ostiense 131/L Corpo B, 00154 Roma

cell. 3466147165
tel.  0657060500
email:ste...@so...

Il giorno 17/mar/09, alle ore 12:49, Stefano Elmopi ha scritto:

>
>
>
> Hi Marc,
>
> I had solved by changing the parameters with which it is
> call the function clusterfs_mount_cdsl in the script  
> linuxrc.generic.sh and recreating the image,
> but if this is not tested, I change the strategy.
> I will do the procedure again because I want to have the Grub on  
> partition OCFS2,
> and then I would create the infrastructure with <nodeid> and not  
> with <nodename>,
> avoiding to create symbolic-link and to have a cleaner situation.
> To do this, I must put option -i using com-mkcdslinfrastructure ??
>
> Thanks
>
>
>
>
> Ing. Stefano Elmopi
> Gruppo Darco - Area ICT Sistemi
> Via Ostiense 131/L Corpo B, 00154 Roma
>
> cell. 3466147165
> tel.  0657060500
> email:ste...@so...
>
> Il giorno 12/mar/09, alle ore 09:23, Marc Grimme ha scritto:
>
>> On Wednesday 11 March 2009 16:35:10 Stefano Elmopi wrote:
>>> Hi Marc
>>>
>>> maybe I found a small error in the init script.
>>> The function clusterfs_mount_cdsl is called with 4 parameters:
>>> mountpoint
>>> cdsl_dir
>>> nodeid
>>> prefix="/cluster/cdsl"
>>>
>>> but, in this manner, build the directory:
>>>
>>> ...../cluster/cdsl/1/.....
>>>
>>> to mount on
>>>
>>> ...../cdsl.local/.....
>>>
>>> but the infrastructure created is of type:
>>>
>>> ...../cluster/cdsl/<nodename>/.....   and no <nodeid>.
>>>
>>> In this way the procedure goes wrong.
>>> In the linuxrc.generic.sh I have changed as is called the function
>>> clusterfs_mount_cdsl
>>> and precisely call it with <nodename> instead of <nodeid>.
>>> In this mamanner the procedure goes well and the new root OCFS2 is
>>> mounted with GRUB on local server.
>>> I hope to be clear.
>> This means you've created the cdsl infrastructure with nodenames  
>> instead of
>> nodeids. The default is to create the cdsl infrastructure with  
>> nodenames
>> although we don't support it (test it) anymore (I should open a  
>> bug!!!!). We
>> must change the default behaviour to use nodeids.
>>
>> But for you to work it around you could leave everything as it is  
>> and create
>> symbolic links from <nodename> to <nodeid> in /cluster/cdsl. What  
>> do you
>> think?
>>
>> -- 
>> Gruss / Regards,
>>
>> Marc Grimme
>> http://www.atix.de/               http://www.open-sharedroot.org/
>>
>>
>

[OSR-users] Problem with OCFS2

[Stefano E. <ste...@so...>]

Hi Marc,

I had solved by changing the parameters with which it is
call the function clusterfs_mount_cdsl in the script  
linuxrc.generic.sh and recreating the image,
but if this is not tested, I change the strategy.
I will do the procedure again because I want to have the Grub on  
partition OCFS2,
and then I would create the infrastructure with <nodeid> and not with  
<nodename>,
avoiding to create symbolic-link and to have a cleaner situation.
To do this, I must put option -i using com-mkcdslinfrastructure ??

Thanks




Ing. Stefano Elmopi
Gruppo Darco - Area ICT Sistemi
Via Ostiense 131/L Corpo B, 00154 Roma

cell. 3466147165
tel.  0657060500
email:ste...@so...

Il giorno 12/mar/09, alle ore 09:23, Marc Grimme ha scritto:

> On Wednesday 11 March 2009 16:35:10 Stefano Elmopi wrote:
>> Hi Marc
>>
>> maybe I found a small error in the init script.
>> The function clusterfs_mount_cdsl is called with 4 parameters:
>> mountpoint
>> cdsl_dir
>> nodeid
>> prefix="/cluster/cdsl"
>>
>> but, in this manner, build the directory:
>>
>> ...../cluster/cdsl/1/.....
>>
>> to mount on
>>
>> ...../cdsl.local/.....
>>
>> but the infrastructure created is of type:
>>
>> ...../cluster/cdsl/<nodename>/.....   and no <nodeid>.
>>
>> In this way the procedure goes wrong.
>> In the linuxrc.generic.sh I have changed as is called the function
>> clusterfs_mount_cdsl
>> and precisely call it with <nodename> instead of <nodeid>.
>> In this mamanner the procedure goes well and the new root OCFS2 is
>> mounted with GRUB on local server.
>> I hope to be clear.
> This means you've created the cdsl infrastructure with nodenames  
> instead of
> nodeids. The default is to create the cdsl infrastructure with  
> nodenames
> although we don't support it (test it) anymore (I should open a  
> bug!!!!). We
> must change the default behaviour to use nodeids.
>
> But for you to work it around you could leave everything as it is  
> and create
> symbolic links from <nodename> to <nodeid> in /cluster/cdsl. What do  
> you
> think?
>
> -- 
> Gruss / Regards,
>
> Marc Grimme
> http://www.atix.de/               http://www.open-sharedroot.org/
>
>

Re: [OSR-users] Problem with OCFS2

[Marc G. <gr...@at...>]

https://bugzilla.atix.de/show_bug.cgi?id=334
Marc.
On Wednesday 11 March 2009 16:35:10 Stefano Elmopi wrote:
> Hi Marc
>
> maybe I found a small error in the init script.
> The function clusterfs_mount_cdsl is called with 4 parameters:
> mountpoint
> cdsl_dir
> nodeid
> prefix="/cluster/cdsl"
>
> but, in this manner, build the directory:
>
> ...../cluster/cdsl/1/.....
>
> to mount on
>
> ...../cdsl.local/.....
>
> but the infrastructure created is of type:
>
> ...../cluster/cdsl/<nodename>/.....   and no <nodeid>.
>
> In this way the procedure goes wrong.
> In the linuxrc.generic.sh I have changed as is called the function
> clusterfs_mount_cdsl
> and precisely call it with <nodename> instead of <nodeid>.
> In this mamanner the procedure goes well and the new root OCFS2 is
> mounted with GRUB on local server.
> I hope to be clear.
>
> Bye
>
>
> Ing. Stefano Elmopi
> Gruppo Darco - Area ICT Sistemi
> Via Ostiense 131/L Corpo B, 00154 Roma
>
> cell. 3466147165
> tel.  0657060500
> email:ste...@so...
>
> Il giorno 05/mar/09, alle ore 15:17, Stefano Elmopi ha scritto:
> > Hi Marc,
> >
> > sorry but I would not have noticed that I wrote the phrase in Italian.
> > The meaning of the phrase was that I will do a test with the file
> > fstab correct
> > but then try to boot directly from the SAN!
> >
> > Thanks
> >
> >
> >
> > Ing. Stefano Elmopi
> > Gruppo Darco - Area ICT Sistemi
> > Via Ostiense 131/L Corpo B, 00154 Roma
> >
> > cell. 3466147165
> > tel.  0657060500
> > email:ste...@so...
> >
> > Il giorno 05/mar/09, alle ore 13:29, Marc Grimme ha scritto:
> >> Hi Stefano,
> >> I would say your fstab should look as follows:
> >>
> >> #/dev/sda            /                      ocfs2  defaults
> >> 0 0
> >> #LABEL=/tmp     /tmp                ext3    defaults         1 2
> >> #LABEL=/var       /var                 ext3    defaults        1 2
> >> #LABEL=/usr       /usr                 ext3    defaults        1 2
> >> #/dev/cciss/c0d0p1 /boot           ext3    defaults        1 2
> >> tmpfs                   /dev/shm                tmpfs
> >> defaults        0 0
> >> devpts                  /dev/pts                devpts
> >> gid=5,mode=620  0 0
> >> sysfs                   /sys                    sysfs
> >> defaults        0 0
> >> proc                    /proc                   proc
> >> defaults        0 0
> >> LABEL=SW-cciss/c0d0p2   swap                    swap
> >> defaults        0 0
> >>
> >> On Thursday 05 March 2009 12:41:12 Stefano Elmopi wrote:
> >>> Hi Marc,
> >>>
> >>> the process goes forward and when it starts to load CentOS
> >>> I see some errors like that does not find the file /etc/fstab,
> >>> as if the reference to find the path for files were wrong !
> >>> In the end arrive at the login screen but whatever I write, it tells
> >>> me that the login is wrong !!
> >>>
> >>> To clarify on my /etc/fstab, I must uncomment the line:
> >>>
> >>> #LABEL=/tmp              /tmp		ext3		defaults        1 2
> >>>
> >>> Comunque, ho deciso che proverò a fare tutto il boot da SAN !!!
> >>
> >> ;-)
> >> You're saying everything is booting from a SAN right?
> >>
> >> But the line:
> >> /dev/cciss/c0d0p1 /boot           ext3    defaults        1 2
> >> tell's different. Doesn't it?
> >>
> >> But the fstab obove should work.
> >>
> >>> Thanks
> >>
> >> --
> >> Gruss / Regards,
> >>
> >> Marc Grimme
> >> http://www.atix.de/               http://www.open-sharedroot.org/
>
> ---------------------------------------------------------------------------
>--- Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> Open-sharedroot-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/open-sharedroot-users



-- 
Gruss / Regards,

Marc Grimme
http://www.atix.de/               http://www.open-sharedroot.org/

Re: [OSR-users] Problem with OCFS2

[Marc G. <gr...@at...>]

On Wednesday 11 March 2009 16:35:10 Stefano Elmopi wrote:
> Hi Marc
>
> maybe I found a small error in the init script.
> The function clusterfs_mount_cdsl is called with 4 parameters:
> mountpoint
> cdsl_dir
> nodeid
> prefix="/cluster/cdsl"
>
> but, in this manner, build the directory:
>
> ...../cluster/cdsl/1/.....
>
> to mount on
>
> ...../cdsl.local/.....
>
> but the infrastructure created is of type:
>
> ...../cluster/cdsl/<nodename>/.....   and no <nodeid>.
>
> In this way the procedure goes wrong.
> In the linuxrc.generic.sh I have changed as is called the function
> clusterfs_mount_cdsl
> and precisely call it with <nodename> instead of <nodeid>.
> In this mamanner the procedure goes well and the new root OCFS2 is
> mounted with GRUB on local server.
> I hope to be clear.
This means you've created the cdsl infrastructure with nodenames instead of 
nodeids. The default is to create the cdsl infrastructure with nodenames 
although we don't support it (test it) anymore (I should open a bug!!!!). We 
must change the default behaviour to use nodeids.

But for you to work it around you could leave everything as it is and create 
symbolic links from <nodename> to <nodeid> in /cluster/cdsl. What do you 
think?

-- 
Gruss / Regards,

Marc Grimme
http://www.atix.de/               http://www.open-sharedroot.org/

[OSR-users] Problem with OCFS2

[Stefano E. <ste...@so...>]

Hi Marc

maybe I found a small error in the init script.
The function clusterfs_mount_cdsl is called with 4 parameters:
mountpoint
cdsl_dir
nodeid
prefix="/cluster/cdsl"

but, in this manner, build the directory:

...../cluster/cdsl/1/.....

to mount on

...../cdsl.local/.....

but the infrastructure created is of type:

...../cluster/cdsl/<nodename>/.....   and no <nodeid>.

In this way the procedure goes wrong.
In the linuxrc.generic.sh I have changed as is called the function  
clusterfs_mount_cdsl
and precisely call it with <nodename> instead of <nodeid>.
In this mamanner the procedure goes well and the new root OCFS2 is  
mounted with GRUB on local server.
I hope to be clear.

Bye


Ing. Stefano Elmopi
Gruppo Darco - Area ICT Sistemi
Via Ostiense 131/L Corpo B, 00154 Roma

cell. 3466147165
tel.  0657060500
email:ste...@so...

Il giorno 05/mar/09, alle ore 15:17, Stefano Elmopi ha scritto:

>
> Hi Marc,
>
> sorry but I would not have noticed that I wrote the phrase in Italian.
> The meaning of the phrase was that I will do a test with the file  
> fstab correct
> but then try to boot directly from the SAN!
>
> Thanks
>
>
>
> Ing. Stefano Elmopi
> Gruppo Darco - Area ICT Sistemi
> Via Ostiense 131/L Corpo B, 00154 Roma
>
> cell. 3466147165
> tel.  0657060500
> email:ste...@so...
>
> Il giorno 05/mar/09, alle ore 13:29, Marc Grimme ha scritto:
>
>> Hi Stefano,
>> I would say your fstab should look as follows:
>>
>> #/dev/sda            /                      ocfs2  defaults          
>> 0 0
>> #LABEL=/tmp     /tmp                ext3    defaults         1 2
>> #LABEL=/var       /var                 ext3    defaults        1 2
>> #LABEL=/usr       /usr                 ext3    defaults        1 2
>> #/dev/cciss/c0d0p1 /boot           ext3    defaults        1 2
>> tmpfs                   /dev/shm                tmpfs
>> defaults        0 0
>> devpts                  /dev/pts                devpts
>> gid=5,mode=620  0 0
>> sysfs                   /sys                    sysfs
>> defaults        0 0
>> proc                    /proc                   proc
>> defaults        0 0
>> LABEL=SW-cciss/c0d0p2   swap                    swap
>> defaults        0 0
>>
>> On Thursday 05 March 2009 12:41:12 Stefano Elmopi wrote:
>>> Hi Marc,
>>>
>>> the process goes forward and when it starts to load CentOS
>>> I see some errors like that does not find the file /etc/fstab,
>>> as if the reference to find the path for files were wrong !
>>> In the end arrive at the login screen but whatever I write, it tells
>>> me that the login is wrong !!
>>>
>>> To clarify on my /etc/fstab, I must uncomment the line:
>>>
>>> #LABEL=/tmp              /tmp		ext3		defaults        1 2
>>>
>>> Comunque, ho deciso che proverò a fare tutto il boot da SAN !!!
>> ;-)
>> You're saying everything is booting from a SAN right?
>>
>> But the line:
>> /dev/cciss/c0d0p1 /boot           ext3    defaults        1 2
>> tell's different. Doesn't it?
>>
>> But the fstab obove should work.
>>>
>>> Thanks
>>
>> -- 
>> Gruss / Regards,
>>
>> Marc Grimme
>> http://www.atix.de/               http://www.open-sharedroot.org/
>>
>>
>

[OSR-users] Problem with OCFS2

[Stefano E. <ste...@so...>]

Hi Marc,

sorry but I would not have noticed that I wrote the phrase in Italian.
The meaning of the phrase was that I will do a test with the file  
fstab correct
but then try to boot directly from the SAN!

Thanks



Ing. Stefano Elmopi
Gruppo Darco - Area ICT Sistemi
Via Ostiense 131/L Corpo B, 00154 Roma

cell. 3466147165
tel.  0657060500
email:ste...@so...

Il giorno 05/mar/09, alle ore 13:29, Marc Grimme ha scritto:

> Hi Stefano,
> I would say your fstab should look as follows:
>
> #/dev/sda            /                      ocfs2  defaults          
> 0 0
> #LABEL=/tmp     /tmp                ext3    defaults         1 2
> #LABEL=/var       /var                 ext3    defaults        1 2
> #LABEL=/usr       /usr                 ext3    defaults        1 2
> #/dev/cciss/c0d0p1 /boot           ext3    defaults        1 2
> tmpfs                   /dev/shm                tmpfs
> defaults        0 0
> devpts                  /dev/pts                devpts
> gid=5,mode=620  0 0
> sysfs                   /sys                    sysfs
> defaults        0 0
> proc                    /proc                   proc
> defaults        0 0
> LABEL=SW-cciss/c0d0p2   swap                    swap
> defaults        0 0
>
> On Thursday 05 March 2009 12:41:12 Stefano Elmopi wrote:
>> Hi Marc,
>>
>> the process goes forward and when it starts to load CentOS
>> I see some errors like that does not find the file /etc/fstab,
>> as if the reference to find the path for files were wrong !
>> In the end arrive at the login screen but whatever I write, it tells
>> me that the login is wrong !!
>>
>> To clarify on my /etc/fstab, I must uncomment the line:
>>
>> #LABEL=/tmp              /tmp		ext3		defaults        1 2
>>
>> Comunque, ho deciso che proverò a fare tutto il boot da SAN !!!
> ;-)
> You're saying everything is booting from a SAN right?
>
> But the line:
> /dev/cciss/c0d0p1 /boot           ext3    defaults        1 2
> tell's different. Doesn't it?
>
> But the fstab obove should work.
>>
>> Thanks
>
> -- 
> Gruss / Regards,
>
> Marc Grimme
> http://www.atix.de/               http://www.open-sharedroot.org/
>
>

Re: [OSR-users] Problem with OCFS2

[Marc G. <gr...@at...>]

Hi Stefano,
I would say your fstab should look as follows:

#/dev/sda            /                      ocfs2  defaults         0 0
#LABEL=/tmp     /tmp                ext3    defaults         1 2
#LABEL=/var       /var                 ext3    defaults        1 2
#LABEL=/usr       /usr                 ext3    defaults        1 2
#/dev/cciss/c0d0p1 /boot           ext3    defaults        1 2
tmpfs                   /dev/shm                tmpfs    
defaults        0 0
devpts                  /dev/pts                devpts   
gid=5,mode=620  0 0
sysfs                   /sys                    sysfs    
defaults        0 0
proc                    /proc                   proc     
defaults        0 0
LABEL=SW-cciss/c0d0p2   swap                    swap     
defaults        0 0

On Thursday 05 March 2009 12:41:12 Stefano Elmopi wrote:
> Hi Marc,
>
> the process goes forward and when it starts to load CentOS
> I see some errors like that does not find the file /etc/fstab,
> as if the reference to find the path for files were wrong !
> In the end arrive at the login screen but whatever I write, it tells
> me that the login is wrong !!
>
> To clarify on my /etc/fstab, I must uncomment the line:
>
> #LABEL=/tmp              /tmp		ext3		defaults        1 2
>
> Comunque, ho deciso che proverò a fare tutto il boot da SAN !!!
;-)
You're saying everything is booting from a SAN right?

But the line:
/dev/cciss/c0d0p1 /boot           ext3    defaults        1 2
tell's different. Doesn't it?

But the fstab obove should work.
>
> Thanks

-- 
Gruss / Regards,

Marc Grimme
http://www.atix.de/               http://www.open-sharedroot.org/

[OSR-users] Problem with OCFS2

[Stefano E. <ste...@so...>]

Hi Marc,

the process goes forward and when it starts to load CentOS
I see some errors like that does not find the file /etc/fstab,
as if the reference to find the path for files were wrong !
In the end arrive at the login screen but whatever I write, it tells  
me that the login is wrong !!

To clarify on my /etc/fstab, I must uncomment the line:

#LABEL=/tmp              /tmp		ext3		defaults        1 2

Comunque, ho deciso che proverò a fare tutto il boot da SAN !!!

Thanks



Ing. Stefano Elmopi
Gruppo Darco - Area ICT Sistemi
Via Ostiense 131/L Corpo B, 00154 Roma

cell. 3466147165
tel.  0657060500
email:ste...@so...

Il giorno 04/mar/09, alle ore 22:01, Marc Grimme ha scritto:

> Hi Stefano,
> everything looks ok.
>
> Too mount the clusterfs to /mnt/newroot is ok.
> First the rootfs is mounted to /mnt/newroot and later on changed to /.
>
> But what happens then? Is the bootprocess hanging?
>
> The only thing I can see is that you should uncomment the first line
> in /etc/fstab:
>
> On Tuesday 03 March 2009 15:15:37 Stefano Elmopi wrote:
>> Hi Marc,
>>
>> thanks for your suggestions, now the process goes forward..... but I
>> have other problems.....sigh !!!
>> From what I understand, it seems to me wrong mounting the new root.
>> My idea is to have the Grub on the local server and then switch the
>> Root on OCFS2 partition.
>> My file grub.conf:
>>
>> cat /boot/grub/grub.conf
>> # grub.conf generated by anaconda
>> #
>> # Note that you do not have to rerun grub after making changes to  
>> this
>> file
>> # NOTICE:  You have a /boot partition.  This means that
>> #          all kernel and initrd paths are relative to /boot/, eg.
>> #          root (hd0,0)
>> #          kernel /vmlinuz-version ro root=/dev/cciss/c0d0p3
>> #          initrd /initrd-version.img
>> #boot=/dev/cciss/c0d0
>> default=0
>> timeout=5
>> splashimage=(hd0,0)/grub/splash.xpm.gz
>> hiddenmenu
>> title CentOS (2.6.18-92.1.22.el5PAE)
>>         root (hd0,0)
>>         kernel /vmlinuz-2.6.18-92.1.22.el5PAE ro root=/dev/sda com-
>> debug com-stepmod
>>         initrd /initrd_sr-2.6.18-92.1.22.el5PAE.img
>>
>>
>> then I have the file fstab on the newroot:
>>
>> cat /mnt/newroot/etc/fstab
>> /dev/sda		 /       		ocfs2  defaults		0 0
>> #LABEL=/tmp              /tmp                    ext3
>> defaults        1 2
>> #LABEL=/var              /var                    ext3
>> defaults        1 2
>> #LABEL=/usr              /usr                    ext3
>> defaults        1 2
>> /dev/cciss/c0d0p1        /boot                   ext3
>> defaults        1 2
>> tmpfs                   /dev/shm                tmpfs
>> defaults        0 0
>> devpts                  /dev/pts                devpts
>> gid=5,mode=620  0 0
>> sysfs                   /sys                    sysfs
>> defaults        0 0
>> proc                    /proc                   proc
>> defaults        0 0
>> LABEL=SW-cciss/c0d0p2   swap                    swap
>> defaults        0 0
>>
>>
>> I have attached the log files that produced the server but that  
>> sounds
>> strange to me
>> is that in the Repository list, in the log files, there is the entry:
>>
>> newroot:/mnt/newroot
>>
>> should not be:
>>
>> newroot:/
>>
>> where it should be the file Repository ??
>>
>> Thanks
>
>
>
> -- 
> Gruss / Regards,
>
> Marc Grimme
> Phone: +49-89 452 3538-14
> http://www.atix.de/               http://www.open-sharedroot.org/
>
> ATIX Informationstechnologie und Consulting AG | Einsteinstrasse 10 |
> 85716 Unterschleissheim | www.atix.de | www.open-sharedroot.org
>
> Registergericht: Amtsgericht Muenchen, Registernummer: HRB 168930,  
> USt.-Id.:
> DE209485962 | Vorstand: Marc Grimme, Mark Hlawatschek, Thomas Merz  
> (Vors.) |
> Vorsitzender des Aufsichtsrats: Dr. Martin Buss
>
>

Re: [OSR-users] Problem with OCFS2

[Marc G. <gr...@at...>]

Hi Stefano,
everything looks ok.

Too mount the clusterfs to /mnt/newroot is ok. 
First the rootfs is mounted to /mnt/newroot and later on changed to /.

But what happens then? Is the bootprocess hanging?

The only thing I can see is that you should uncomment the first line 
in /etc/fstab:

On Tuesday 03 March 2009 15:15:37 Stefano Elmopi wrote:
> Hi Marc,
>
> thanks for your suggestions, now the process goes forward..... but I
> have other problems.....sigh !!!
>  From what I understand, it seems to me wrong mounting the new root.
> My idea is to have the Grub on the local server and then switch the
> Root on OCFS2 partition.
> My file grub.conf:
>
> cat /boot/grub/grub.conf
> # grub.conf generated by anaconda
> #
> # Note that you do not have to rerun grub after making changes to this
> file
> # NOTICE:  You have a /boot partition.  This means that
> #          all kernel and initrd paths are relative to /boot/, eg.
> #          root (hd0,0)
> #          kernel /vmlinuz-version ro root=/dev/cciss/c0d0p3
> #          initrd /initrd-version.img
> #boot=/dev/cciss/c0d0
> default=0
> timeout=5
> splashimage=(hd0,0)/grub/splash.xpm.gz
> hiddenmenu
> title CentOS (2.6.18-92.1.22.el5PAE)
>          root (hd0,0)
>          kernel /vmlinuz-2.6.18-92.1.22.el5PAE ro root=/dev/sda com-
> debug com-stepmod
>          initrd /initrd_sr-2.6.18-92.1.22.el5PAE.img
>
>
> then I have the file fstab on the newroot:
>
> cat /mnt/newroot/etc/fstab
> /dev/sda		 /       		ocfs2  defaults		0 0
> #LABEL=/tmp              /tmp                    ext3
> defaults        1 2
> #LABEL=/var              /var                    ext3
> defaults        1 2
> #LABEL=/usr              /usr                    ext3
> defaults        1 2
> /dev/cciss/c0d0p1        /boot                   ext3
> defaults        1 2
> tmpfs                   /dev/shm                tmpfs
> defaults        0 0
> devpts                  /dev/pts                devpts
> gid=5,mode=620  0 0
> sysfs                   /sys                    sysfs
> defaults        0 0
> proc                    /proc                   proc
> defaults        0 0
> LABEL=SW-cciss/c0d0p2   swap                    swap
> defaults        0 0
>
>
> I have attached the log files that produced the server but that sounds
> strange to me
> is that in the Repository list, in the log files, there is the entry:
>
> newroot:/mnt/newroot
>
> should not be:
>
> newroot:/
>
> where it should be the file Repository ??
>
> Thanks



-- 
Gruss / Regards,

Marc Grimme
Phone: +49-89 452 3538-14
http://www.atix.de/               http://www.open-sharedroot.org/

ATIX Informationstechnologie und Consulting AG | Einsteinstrasse 10 |
85716 Unterschleissheim | www.atix.de | www.open-sharedroot.org

Registergericht: Amtsgericht Muenchen, Registernummer: HRB 168930, USt.-Id.: 
DE209485962 | Vorstand: Marc Grimme, Mark Hlawatschek, Thomas Merz (Vors.) |
Vorsitzender des Aufsichtsrats: Dr. Martin Buss

[OSR-users] Problem with OCFS2

[Stefano E. <ste...@so...>]

Hi Marc,

thanks for your suggestions, now the process goes forward..... but I  
have other problems.....sigh !!!
 From what I understand, it seems to me wrong mounting the new root.
My idea is to have the Grub on the local server and then switch the  
Root on OCFS2 partition.
My file grub.conf:

cat /boot/grub/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this  
file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/cciss/c0d0p3
#          initrd /initrd-version.img
#boot=/dev/cciss/c0d0
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.18-92.1.22.el5PAE)
         root (hd0,0)
         kernel /vmlinuz-2.6.18-92.1.22.el5PAE ro root=/dev/sda com- 
debug com-stepmod
         initrd /initrd_sr-2.6.18-92.1.22.el5PAE.img


then I have the file fstab on the newroot:

cat /mnt/newroot/etc/fstab
/dev/sda		 /       		ocfs2  defaults		0 0
#LABEL=/tmp              /tmp                    ext3     
defaults        1 2
#LABEL=/var              /var                    ext3     
defaults        1 2
#LABEL=/usr              /usr                    ext3     
defaults        1 2
/dev/cciss/c0d0p1        /boot                   ext3     
defaults        1 2
tmpfs                   /dev/shm                tmpfs    
defaults        0 0
devpts                  /dev/pts                devpts   
gid=5,mode=620  0 0
sysfs                   /sys                    sysfs    
defaults        0 0
proc                    /proc                   proc     
defaults        0 0
LABEL=SW-cciss/c0d0p2   swap                    swap     
defaults        0 0


I have attached the log files that produced the server but that sounds  
strange to me
is that in the Repository list, in the log files, there is the entry:

newroot:/mnt/newroot

should not be:

newroot:/

where it should be the file Repository ??

Thanks

Re: [OSR-users] Problem with OCFS2

[Marc G. <gr...@at...>]

Hi Stefano,
I found something. I think you are missing 
comoonics-bootimage-listfilles-rhel5.

I need to make them dependent from the initscripts.

Sorry Marc.
On Thursday 26 February 2009 15:16:51 Stefano Elmopi wrote:
> Hi Marc,
>
> I have attached two photos, I hope you can read.
> The boot process start and it comes to the screen that you see in foto_1
> and remains locked until I push twice the return key.
> After this the process the process goes on until the screen that you
> see in foto_2,
> where we see that the function "cc_validate" fails.
>
> I will send you also the one that I had requested:
> com-queryclusterconf convert ocfs2
>
> node:
>          ip_port = 7777
>          ip_address = 10.43.100.203
>          number = 1
>          name = clu01
>          cluster = cluOCFS2
>
> node:
>          ip_port = 7777
>          ip_address = 10.43.100.187
>          number = 2
>          name = clu02
>          cluster = cluOCFS2
>
> cluster:
>          node_count = 2
>          name = cluOCFS2
>
> start with this and if you need more info, just ask me.
>
> Bye



-- 
Gruss / Regards,

Marc Grimme
Phone: +49-89 452 3538-14
http://www.atix.de/               http://www.open-sharedroot.org/

ATIX Informationstechnologie und Consulting AG | Einsteinstrasse 10 |
85716 Unterschleissheim | www.atix.de | www.open-sharedroot.org

Registergericht: Amtsgericht Muenchen, Registernummer: HRB 168930, USt.-Id.: 
DE209485962 | Vorstand: Marc Grimme, Mark Hlawatschek, Thomas Merz (Vors.) |
Vorsitzender des Aufsichtsrats: Dr. Martin Buss

Re: [OSR-users] Problem with OCFS2

[Marc G. <gr...@at...>]

On Thursday 26 February 2009 15:16:51 Stefano Elmopi wrote:
> Hi Marc,
>
> I have attached two photos, I hope you can read.
> The boot process start and it comes to the screen that you see in foto_1
> and remains locked until I push twice the return key.
> After this the process the process goes on until the screen that you
> see in foto_2,
> where we see that the function "cc_validate" fails.
That's really strange. 
Could you just execute cc_validate on the console you were left and report 
about the errors there?
Until now I have no idea everything looks ok.
You could also do that following unpack the initrd (mkdir /tmp/initrd; 
cd /tmp/initrd; gzip -cd <initrdfile> | cpio -i) and the chroot /tmp/initrd 
and execute "com-queryclusterconf nodeids" and let me now about the result.

Marc.
>
> I will send you also the one that I had requested:
> com-queryclusterconf convert ocfs2
>
> node:
>          ip_port = 7777
>          ip_address = 10.43.100.203
>          number = 1
>          name = clu01
>          cluster = cluOCFS2
>
> node:
>          ip_port = 7777
>          ip_address = 10.43.100.187
>          number = 2
>          name = clu02
>          cluster = cluOCFS2
>
> cluster:
>          node_count = 2
>          name = cluOCFS2
>
> start with this and if you need more info, just ask me.
>
> Bye



-- 
Gruss / Regards,

Marc Grimme
http://www.atix.de/               http://www.open-sharedroot.org/

Re: [OSR-users] Problem with OCFS2

[Marc G. <gr...@at...>]

Hi Stefan,
just send all you have. Pictures are welcome ;-) .
You can just set com-debug as bootoption but nothing else. So no com-debug=xx 
but just com-debug.

Marc.
On Thursday 26 February 2009 08:24:38 Stefano Elmopi wrote:
> Hi Marc,
>
> I have CentOS, I think it is the same !!
> For the parameters, I put them in the file grub.conf in the same line
> of the kernel options ?
> For the com-debug, I do not have to put it in the form com-
> debug=<number> ??
>
> If I can, I will do some testing today and I will send you the output
> of the console.
> In case, can I send a few pictures of the console?
>
>
>
> Bye
>
>
> Ing. Stefano Elmopi
> Gruppo Darco - Area ICT Sistemi
> Via Ostiense 131/L Corpo B, 00154 Roma
>
> cell. 3466147165
> tel.  0657060500
> email:ste...@so...
>
> Il giorno 25/feb/09, alle ore 16:55, Marc Grimme ha scritto:
> > Just add the bootoptions:
> > com-debug: for more information
> > com-step: for using stepmode.
> >
> > BTW: I veryfied the current rpms against ocfs2/rhel5 and they were
> > working.
> >
> > Marc.
> >
> > On Wednesday 25 February 2009 16:44:45 Stefano Elmopi wrote:
> >> Hi Marc,
> >>
> >> How do I set the parameters com-debug and com-stepmod for have more
> >> debugging ?
> >>
> >> Thanks
> >>
> >> Best regard
> >>
> >>
> >> Ing. Stefano Elmopi
> >> Gruppo Darco - Area ICT Sistemi
> >> Via Ostiense 131/L Corpo B, 00154 Roma
> >>
> >> cell. 3466147165
> >> tel.  0657060500
> >> email:ste...@so...
> >>
> >>
> >> ------------------------------------------------------------------------
> >>--- --- Open Source Business Conference (OSBC), March 24-25, 2009, San
> >> Francisco, CA -OSBC tackles the biggest issue in open source: Open
> >> Sourcing
> >> the Enterprise -Strategies to boost innovation and cut costs with
> >> open
> >> source participation -Receive a $600 discount off the registration
> >> fee with
> >> the source code: SFAD http://p.sf.net/sfu/XcvMzF8H
> >> _______________________________________________
> >> Open-sharedroot-users mailing list
> >> Ope...@li...
> >> https://lists.sourceforge.net/lists/listinfo/open-sharedroot-users
> >
> > --
> > Gruss / Regards,
> >
> > Marc Grimme
> > http://www.atix.de/               http://www.open-sharedroot.org/



-- 
Gruss / Regards,

Marc Grimme
Phone: +49-89 452 3538-14
http://www.atix.de/               http://www.open-sharedroot.org/

ATIX Informationstechnologie und Consulting AG | Einsteinstrasse 10 |
85716 Unterschleissheim | www.atix.de | www.open-sharedroot.org

Registergericht: Amtsgericht Muenchen, Registernummer: HRB 168930, USt.-Id.: 
DE209485962 | Vorstand: Marc Grimme, Mark Hlawatschek, Thomas Merz (Vors.) |
Vorsitzender des Aufsichtsrats: Dr. Martin Buss

[OSR-users] Problem with OCFS2

[Stefano E. <ste...@so...>]

Hi Marc,

I have CentOS, I think it is the same !!
For the parameters, I put them in the file grub.conf in the same line  
of the kernel options ?
For the com-debug, I do not have to put it in the form com- 
debug=<number> ??

If I can, I will do some testing today and I will send you the output  
of the console.
In case, can I send a few pictures of the console?



Bye


Ing. Stefano Elmopi
Gruppo Darco - Area ICT Sistemi
Via Ostiense 131/L Corpo B, 00154 Roma

cell. 3466147165
tel.  0657060500
email:ste...@so...

Il giorno 25/feb/09, alle ore 16:55, Marc Grimme ha scritto:

> Just add the bootoptions:
> com-debug: for more information
> com-step: for using stepmode.
>
> BTW: I veryfied the current rpms against ocfs2/rhel5 and they were  
> working.
>
> Marc.
> On Wednesday 25 February 2009 16:44:45 Stefano Elmopi wrote:
>> Hi Marc,
>>
>> How do I set the parameters com-debug and com-stepmod for have more
>> debugging ?
>>
>> Thanks
>>
>> Best regard
>>
>>
>> Ing. Stefano Elmopi
>> Gruppo Darco - Area ICT Sistemi
>> Via Ostiense 131/L Corpo B, 00154 Roma
>>
>> cell. 3466147165
>> tel.  0657060500
>> email:ste...@so...
>>
>>
>> ---------------------------------------------------------------------------
>> --- Open Source Business Conference (OSBC), March 24-25, 2009, San
>> Francisco, CA -OSBC tackles the biggest issue in open source: Open  
>> Sourcing
>> the Enterprise -Strategies to boost innovation and cut costs with  
>> open
>> source participation -Receive a $600 discount off the registration  
>> fee with
>> the source code: SFAD http://p.sf.net/sfu/XcvMzF8H
>> _______________________________________________
>> Open-sharedroot-users mailing list
>> Ope...@li...
>> https://lists.sourceforge.net/lists/listinfo/open-sharedroot-users
>
>
>
> -- 
> Gruss / Regards,
>
> Marc Grimme
> http://www.atix.de/               http://www.open-sharedroot.org/
>
>

Re: [OSR-users] Problem with OCFS2

[Marc G. <gr...@at...>]

Just add the bootoptions: 
com-debug: for more information
com-step: for using stepmode.

BTW: I veryfied the current rpms against ocfs2/rhel5 and they were working.

Marc.
On Wednesday 25 February 2009 16:44:45 Stefano Elmopi wrote:
> Hi Marc,
>
> How do I set the parameters com-debug and com-stepmod for have more
> debugging ?
>
> Thanks
>
> Best regard
>
>
> Ing. Stefano Elmopi
> Gruppo Darco - Area ICT Sistemi
> Via Ostiense 131/L Corpo B, 00154 Roma
>
> cell. 3466147165
> tel.  0657060500
> email:ste...@so...
>
>
> ---------------------------------------------------------------------------
>--- Open Source Business Conference (OSBC), March 24-25, 2009, San
> Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing
> the Enterprise -Strategies to boost innovation and cut costs with open
> source participation -Receive a $600 discount off the registration fee with
> the source code: SFAD http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Open-sharedroot-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/open-sharedroot-users



-- 
Gruss / Regards,

Marc Grimme
http://www.atix.de/               http://www.open-sharedroot.org/

[OSR-users] Problem with OCFS2

[Stefano E. <ste...@so...>]

Hi Marc,

How do I set the parameters com-debug and com-stepmod for have more  
debugging ?

Thanks

Best regard


Ing. Stefano Elmopi
Gruppo Darco - Area ICT Sistemi
Via Ostiense 131/L Corpo B, 00154 Roma

cell. 3466147165
tel.  0657060500
email:ste...@so...

Re: [OSR-users] Problem with OCFS2

[Marc G. <gr...@at...>]

Hi Stefano,
could you be so kind and also attach the console output (if possible).
And note: I didn't (yet) validate the new bootimage with ocfs2. Hopefully I'll 
get it done tomorrow and let you know.

Everything else looks like ok.

What does com-queryclusterconf convert ocfs2 say?

Also remove the syslog and you might see more information on console.

Regards Marc.
On Monday 23 February 2009 15:17:43 Stefano Elmopi wrote:
> Hi,
>
> now I'm trying to create a cluster with OCFS2 but there are problems
> when have to mount
> the new Shared-Root. Unlike the guide, I left the original grub but I
> have changed it
> so that the new Shared-Root is the OCFS2 volume.
> The server is able to mount the image
> initrd_sr-2.6.18-92.1.22.el5PAE.img
> (created as written on the guide), but then fails to validate the
> cluster.conf,
> seems that it is unable to find information about hardware of the server
> and therefore can not validate that written in file config.conf.
> It isn't able to find the hostname, the mac-address of network card
> and so on !!!!
>
> hostname
> clu01
>
> cat /etc/sysconfig/network-scripts/ifcfg-eth0
> # Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
> DEVICE=eth0
> BOOTPROTO=static
> HWADDR=00:15:60:56:75:FD
> IPADDR=10.43.100.203
> NETMASK=255.255.0.0
> ONBOOT=yes
>
> The packeges installed:
> rpm -qa | grep comoonics
> SysVinit-comoonics-2.86-14.atix.1
> comoonics-cluster-py-0.1-16
> comoonics-bootimage-extras-ocfs2-0.1-2
> comoonics-cs-py-0.1-56
> comoonics-bootimage-1.4-1
> comoonics-bootimage-fenceacksv-0.3-2
> comoonics-pythonosfix-py-0.1-2
> comoonics-bootimage-initscripts-1.4-1.rhel5
> comoonics-bootimage-listfiles-all-0.1-4
> comoonics-cdsl-py-0.2-11
>
>
> My grub:
> default=0
> timeout=5
> splashimage=(hd0,0)/grub/splash.xpm.gz
> hiddenmenu
> title CentOS (2.6.18-92.1.22.el5PAE)
>          root (hd0,0)
>          kernel /vmlinuz-2.6.18-92.1.22.el5PAE ro root=/dev/sda
>          initrd /initrd_sr-2.6.18-92.1.22.el5PAE.img
>
>
> fstab file:
> cat /mnt/newroot/etc/fstab
> LABEL=/dev/sda          /                       ocfs2
> defaults        0 0
> LABEL=/boot             /boot                   ext3
> defaults        1 2
> tmpfs                   /dev/shm                tmpfs
> defaults        0 0
> devpts                  /dev/pts                devpts
> gid=5,mode=620  0 0
> sysfs                   /sys                    sysfs
> defaults        0 0
> proc                    /proc                   proc
> defaults        0 0
> LABEL=SW-cciss/c0d0p2   swap                    swap
> defaults        0 0
>
>
> cluser.conf file:
> cat /mnt/newroot/etc/cluster/cluster.conf
> <?xml version="1.0"?>
> <cluster config_version="1" name="cluOCFS2">
>    <cman></cman>
>      <clusternodes>
>         <clusternode name="clu01" nodeid="1">
>             <com_info>
>               <syslog name="clu01"/>
>               <rootvolume name="/dev/sda" fstype="ocfs2"/>
>               <eth name="eth0" ip="10.43.100.203"
> mac="00:15:60:56:75:FD"/>
>             </com_info>
>         </clusternode>
>         <clusternode name="clu02" nodeid="2">
>             <com_info>
>               <syslog name="clu02"/>
>               <rootvolume name="/dev/sda" fstype="ocfs2"/>
>               <eth name="eth0" ip="10.43.100.187"
> mac="00:15:60:56:77:11"/>
>             </com_info>
>          </clusternode>
>       </clusternodes>
> </cluster>
>
>
> OCSF2 cluster.conf file:
> cat /mnt/newroot/etc/ocfs2/cluster.conf
> node:
>          ip_port = 7777
>          ip_address = 10.43.100.203
>          number = 1
>          name = clu01
>          cluster = cluOCFS2
>
> node:
>          ip_port = 7777
>          ip_address = 10.43.100.187
>          number = 2
>          name = clu02
>          cluster = cluOCFS2
>
> cluster:
>          node_count = 2
>          name = cluOCFS2
>
>
> Thanks.
>
>
>
>
> Ing. Stefano Elmopi
> Gruppo Darco - Area ICT Sistemi
> Via Ostiense 131/L Corpo B, 00154 Roma
>
> cell. 3466147165
> tel.  0657060500
> email:ste...@so...
>
>
> ---------------------------------------------------------------------------
>--- Open Source Business Conference (OSBC), March 24-25, 2009, San
> Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing
> the Enterprise -Strategies to boost innovation and cut costs with open
> source participation -Receive a $600 discount off the registration fee with
> the source code: SFAD http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Open-sharedroot-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/open-sharedroot-users

-- 
Gruss / Regards,

Marc Grimme
http://www.atix.de/               http://www.open-sharedroot.org/

[OSR-users] Problem with OCFS2

[Stefano E. <ste...@so...>]

Hi,

now I'm trying to create a cluster with OCFS2 but there are problems  
when have to mount
the new Shared-Root. Unlike the guide, I left the original grub but I  
have changed it
so that the new Shared-Root is the OCFS2 volume.
The server is able to mount the image  
initrd_sr-2.6.18-92.1.22.el5PAE.img
(created as written on the guide), but then fails to validate the  
cluster.conf,
seems that it is unable to find information about hardware of the server
and therefore can not validate that written in file config.conf.
It isn't able to find the hostname, the mac-address of network card  
and so on !!!!

hostname
clu01

cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
DEVICE=eth0
BOOTPROTO=static
HWADDR=00:15:60:56:75:FD
IPADDR=10.43.100.203
NETMASK=255.255.0.0
ONBOOT=yes

The packeges installed:
rpm -qa | grep comoonics
SysVinit-comoonics-2.86-14.atix.1
comoonics-cluster-py-0.1-16
comoonics-bootimage-extras-ocfs2-0.1-2
comoonics-cs-py-0.1-56
comoonics-bootimage-1.4-1
comoonics-bootimage-fenceacksv-0.3-2
comoonics-pythonosfix-py-0.1-2
comoonics-bootimage-initscripts-1.4-1.rhel5
comoonics-bootimage-listfiles-all-0.1-4
comoonics-cdsl-py-0.2-11


My grub:
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.18-92.1.22.el5PAE)
         root (hd0,0)
         kernel /vmlinuz-2.6.18-92.1.22.el5PAE ro root=/dev/sda
         initrd /initrd_sr-2.6.18-92.1.22.el5PAE.img


fstab file:
cat /mnt/newroot/etc/fstab
LABEL=/dev/sda          /                       ocfs2    
defaults        0 0
LABEL=/boot             /boot                   ext3     
defaults        1 2
tmpfs                   /dev/shm                tmpfs    
defaults        0 0
devpts                  /dev/pts                devpts   
gid=5,mode=620  0 0
sysfs                   /sys                    sysfs    
defaults        0 0
proc                    /proc                   proc     
defaults        0 0
LABEL=SW-cciss/c0d0p2   swap                    swap     
defaults        0 0


cluser.conf file:
cat /mnt/newroot/etc/cluster/cluster.conf
<?xml version="1.0"?>
<cluster config_version="1" name="cluOCFS2">
   <cman></cman>
     <clusternodes>
        <clusternode name="clu01" nodeid="1">
            <com_info>
              <syslog name="clu01"/>
              <rootvolume name="/dev/sda" fstype="ocfs2"/>
              <eth name="eth0" ip="10.43.100.203"  
mac="00:15:60:56:75:FD"/>
            </com_info>
        </clusternode>
        <clusternode name="clu02" nodeid="2">
            <com_info>
              <syslog name="clu02"/>
              <rootvolume name="/dev/sda" fstype="ocfs2"/>
              <eth name="eth0" ip="10.43.100.187"  
mac="00:15:60:56:77:11"/>
            </com_info>
         </clusternode>
      </clusternodes>
</cluster>


OCSF2 cluster.conf file:
cat /mnt/newroot/etc/ocfs2/cluster.conf
node:
         ip_port = 7777
         ip_address = 10.43.100.203
         number = 1
         name = clu01
         cluster = cluOCFS2

node:
         ip_port = 7777
         ip_address = 10.43.100.187
         number = 2
         name = clu02
         cluster = cluOCFS2

cluster:
         node_count = 2
         name = cluOCFS2


Thanks.




Ing. Stefano Elmopi
Gruppo Darco - Area ICT Sistemi
Via Ostiense 131/L Corpo B, 00154 Roma

cell. 3466147165
tel.  0657060500
email:ste...@so...

[OSR-users] New Preview RPMs for next Release Candidate of comoonics-bootimage

[Marc G. <gr...@at...>]

Hello *,
finally we got the first stage of the new version of the osr cluster suite in 
the preview channel. This will be the first release candidate for the next 
productive channel.

NOTE: Those packages are NOT YET production ready. And they might include bugs 
as they did not undergo the Q&A. So use them at your own risc.

2nd NOTE: Those packages were only tested with OSR<RHEL5> clusters based on 
GFS or NFS. OSR<SLES10/ocfs2>,OSR<Fedora/gfs2|nfs> and OSR<RHEL5/ocfs2> will 
be tested next. This means you shouldn't use those packages with ocfs2 as 
rootfilesystem.

As this is only a preview update I will sum up the most important changes not 
automated:

- Rewritten hardwaredetection: https://bugzilla.atix.de/show_bug.cgi?id=325
- Usability review: https://bugzilla.atix.de/show_bug.cgi?id=323
- Support for breakpoints in bootprocess
- Break shell will always continue the bootprocess when exited
- Bootparameters may be overwritten in Breakshell
- Rootfs Check with bootparameter rootfsck (use with care and up to now only 
with GFS)
- NFS OSR will not start scsi detection
- Preview support for OSR on fedora (NFS)
- Preview support for OSR<NFS4> without authentication
- Preview support for OSR<RHEL5 with localfs>
- Many small bugfixes
Patches from Gordan Bobic (all preview status):
- glusterfs support
- Software RAID with md support 
- diet patch (new option to mkinitrd <-l> to make initrd smaller)

Please let me know what you think

Thanks
Marc

P.S. May the root always be shared! ;-)

-- 
Gruss / Regards,

Marc Grimme
http://www.atix.de/               http://www.open-sharedroot.org/

Re: [OSR-users] rpms for ocfs2+rhel5

[Marc G. <gr...@at...>]

On Tuesday 10 February 2009 00:35:26 Dan Magenheimer wrote:
> OK, I've finished the howto, trying to reasonably substitute
> where necessary for the fact that I am going to boot the
> osr as a xen guest (running 2.6.28 as the guest kernel).
>
> Note that I am running the howto in a Xen EL5 guest booted
> with 2.6.28 and with an ocfs2 filesystem mounted in the
> guest as a second disk "/extra"... so wherever I see
> /mnt/newroot, I am substituting /extra.
That should not be a problem. BTW. I also made the howto for nodes running in 
XEN with EL5. So that should fit.
>
> All seems to go smoothly until I get to the last step...
> the mkinitrd complains loudly and lengthy.  It can't find
> a list of rpms and skips:
> - comoonics-cs-xml
> - kmod-gfs
> - gfs-utils
> - cman
> - openais
> - lvm2-cluster
> - OpenIPMI-tools
> - xen
> - xen-libs
> - libvirt
You can ignore those. These are only warnings (I don't like them either and 
they will go away in the future) for rpms not to be found. Most are related 
to GFS and RedHat Cluster or xen Dom0. You can siltently ignore then.
>
> Then the /boot disk fills and I get cpio errors.  It appears
> that an intird...img.tmp file is created that is 78MB in size.
Yes. It might be that the boot disk is too small. A workaround would be to 
first create the initrd in /tmp. I.e mkinitrd /tmp/initrd_sr... and then 
copy/move it to boot. I've done this whenever the bootdisk was too small.
>
> Oh dear... it also looks like the grub part of the howto has
> changed /boot/grub on my running system, not on the /extra
> disk?!  And now I can't boot that guest anymore at all!
Yes, the bootdisk normally resides on a special disk and therefore must be 
handled specially. See above for a workaround.
>
> When I have a chance, I will restart with a fresh EL5u2
> guest and document every step from the beginning, but
> if you see any obvious solutions, please let me know.
If possible let the /boot be 1G.

Regards
Marc.
-- 
Gruss / Regards,

Marc Grimme
http://www.atix.de/               http://www.open-sharedroot.org/

Re: [OSR-users] rpms for ocfs2+rhel5

[Marc G. <gr...@at...>]

On Monday 09 February 2009 23:11:18 Dan Magenheimer wrote:
> > Does that help and make sense?
>
> Thanks, yes.  But I would like to test the process by
> creating and booting a one-node (or at most two-node)
> cluster and then "grow" it later to a larger cluster.
> Is this possible?  If so, what parts/scripts of the
> howto will I have to re-do when I am ready to grow
> it from one-node (or two-nodes) to many?
If ocfs2 does support it we do as well. I think you just need to add a node to 
the /etc/cluster/cluster.conf build a new initrd and then boot the new node.
Additionally you need to have the hostdependent files ready for that node as 
well. Those will be found at /cluster/cdsl/<nodeid>. Best if this directory 
is not there it to either copy /cluster/cdsl/default 
to /cluster/cdsl/<nodeid> and then adapt the hostdep. files.

Hope that helps
Regrads Marc.


-- 
Gruss / Regards,

Marc Grimme
http://www.atix.de/               http://www.open-sharedroot.org/

Re: [OSR-users] rpms for ocfs2+rhel5

[Dan M. <dan...@or...>]

OK, I've finished the howto, trying to reasonably substitute
where necessary for the fact that I am going to boot the
osr as a xen guest (running 2.6.28 as the guest kernel).

Note that I am running the howto in a Xen EL5 guest booted
with 2.6.28 and with an ocfs2 filesystem mounted in the
guest as a second disk "/extra"... so wherever I see
/mnt/newroot, I am substituting /extra.

All seems to go smoothly until I get to the last step...
the mkinitrd complains loudly and lengthy.  It can't find
a list of rpms and skips:
- comoonics-cs-xml
- kmod-gfs
- gfs-utils
- cman
- openais
- lvm2-cluster
- OpenIPMI-tools
- xen
- xen-libs
- libvirt

Then the /boot disk fills and I get cpio errors.  It appears
that an intird...img.tmp file is created that is 78MB in size.

Oh dear... it also looks like the grub part of the howto has
changed /boot/grub on my running system, not on the /extra
disk?!  And now I can't boot that guest anymore at all!

When I have a chance, I will restart with a fresh EL5u2
guest and document every step from the beginning, but
if you see any obvious solutions, please let me know.

Thanks,
Dan

> -----Original Message-----
> From: Dan Magenheimer 
> Sent: Monday, February 09, 2009 3:11 PM
> To: Marc Grimme; ope...@li...
> Subject: Re: [OSR-users] rpms for ocfs2+rhel5
> 
> 
> > Does that help and make sense?
> 
> Thanks, yes.  But I would like to test the process by
> creating and booting a one-node (or at most two-node)
> cluster and then "grow" it later to a larger cluster.
> Is this possible?  If so, what parts/scripts of the
> howto will I have to re-do when I am ready to grow
> it from one-node (or two-nodes) to many?
> 
> Thanks,
> Dan
> 
> > -----Original Message-----
> > From: Marc Grimme [mailto:gr...@at...]
> > Sent: Saturday, February 07, 2009 3:13 AM
> > To: ope...@li...
> > Cc: Dan Magenheimer
> > Subject: Re: [OSR-users] rpms for ocfs2+rhel5
> > 
> > 
> > On Saturday 07 February 2009 01:42:42 Dan Magenheimer wrote:
> > > Finally got the rpms and installed.  One other typo on
> > > the rhel5/ocfs2 webpage:
> > >
> > > comoonics-bootimage-1.3-33 (not -32)
> > >
> > > as comoonics-bootimage-extras-ocfs2-0.1-1 depends
> > > on -33.
> > Thanks. I fixed both typos. You might want to check if those 
> > are ok now.
> > >
> > > On to the next step! :-)
> > >
> > > Do I need a redhat cluster.conf file other than to
> > > have the ocfs2 cluster.conf file created from it?
> > > In other words, can I just start with my own
> > > /etc/ocfs2/cluster.conf file?  Or will the other
> > > installation steps require /etc/cluster/cluster.conf?
> > Yes, this is something I don't like either but as I had no 
> > customer willing to 
> > pay for it I took the simplest way ;-).
> > 
> > That means up to now you need a /etc/cluster/cluster.conf 
> > based on redhat 
> > cluster. And on the other side it wasn't possible to extend 
> the ocfs 
> > cluster.conf with attributes.
> > 
> > So in the current state you will have to create a 
> > cluster.conf. This will be 
> > the base for the /etc/ocfs2/cluster.conf which will be 
> automatically 
> > generated by com-queryclusterconf convert ocfs2. To validate 
> > the output you 
> > can use the command. It should return something like below:
> > 
> > [root@generix3 ~]# com-queryclusterconf convert ocfs2
> > 
> > node:
> >         ip_port = 7777
> >         ip_address = 10.10.10.83
> >         number = 3
> >         name = generix3.local
> >         cluster = clu_generix
> > 
> > node:
> >         ip_port = 7777
> >         ip_address = 10.10.10.82
> >         number = 2
> >         name = generix2.local
> >         cluster = clu_generix
> > 
> > node:
> >         ip_port = 7777
> >         ip_address = 10.10.10.84
> >         number = 4
> >         name = generix4.local
> >         cluster = clu_generix
> > 
> > cluster:
> >         node_count = 3
> >         name = clu_generix
> > 
> > Does that help and make sense?
> > 
> > Marc.
> > 
> > -- 
> > Gruss / Regards,
> > 
> > Marc Grimme
> > http://www.atix.de/               http://www.open-sharedroot.org/
> > 
> >
> 
> --------------------------------------------------------------
> ----------------
> Create and Deploy Rich Internet Apps outside the browser with 
> Adobe(R)AIR(TM)
> software. With Adobe AIR, Ajax developers can use existing 
> skills and code to
> build responsive, highly engaging applications that combine 
> the power of local
> resources and data with the reach of the web. Download the 
> Adobe AIR SDK and
> Ajax docs to start building applications 
> today-http://p.sf.net/sfu/adobe-com
> _______________________________________________
> Open-sharedroot-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/open-sharedroot-users
>

Re: [OSR-users] rpms for ocfs2+rhel5

[Dan M. <dan...@or...>]

> Does that help and make sense?

Thanks, yes.  But I would like to test the process by
creating and booting a one-node (or at most two-node)
cluster and then "grow" it later to a larger cluster.
Is this possible?  If so, what parts/scripts of the
howto will I have to re-do when I am ready to grow
it from one-node (or two-nodes) to many?

Thanks,
Dan

> -----Original Message-----
> From: Marc Grimme [mailto:gr...@at...]
> Sent: Saturday, February 07, 2009 3:13 AM
> To: ope...@li...
> Cc: Dan Magenheimer
> Subject: Re: [OSR-users] rpms for ocfs2+rhel5
> 
> 
> On Saturday 07 February 2009 01:42:42 Dan Magenheimer wrote:
> > Finally got the rpms and installed.  One other typo on
> > the rhel5/ocfs2 webpage:
> >
> > comoonics-bootimage-1.3-33 (not -32)
> >
> > as comoonics-bootimage-extras-ocfs2-0.1-1 depends
> > on -33.
> Thanks. I fixed both typos. You might want to check if those 
> are ok now.
> >
> > On to the next step! :-)
> >
> > Do I need a redhat cluster.conf file other than to
> > have the ocfs2 cluster.conf file created from it?
> > In other words, can I just start with my own
> > /etc/ocfs2/cluster.conf file?  Or will the other
> > installation steps require /etc/cluster/cluster.conf?
> Yes, this is something I don't like either but as I had no 
> customer willing to 
> pay for it I took the simplest way ;-).
> 
> That means up to now you need a /etc/cluster/cluster.conf 
> based on redhat 
> cluster. And on the other side it wasn't possible to extend the ocfs 
> cluster.conf with attributes.
> 
> So in the current state you will have to create a 
> cluster.conf. This will be 
> the base for the /etc/ocfs2/cluster.conf which will be automatically 
> generated by com-queryclusterconf convert ocfs2. To validate 
> the output you 
> can use the command. It should return something like below:
> 
> [root@generix3 ~]# com-queryclusterconf convert ocfs2
> 
> node:
>         ip_port = 7777
>         ip_address = 10.10.10.83
>         number = 3
>         name = generix3.local
>         cluster = clu_generix
> 
> node:
>         ip_port = 7777
>         ip_address = 10.10.10.82
>         number = 2
>         name = generix2.local
>         cluster = clu_generix
> 
> node:
>         ip_port = 7777
>         ip_address = 10.10.10.84
>         number = 4
>         name = generix4.local
>         cluster = clu_generix
> 
> cluster:
>         node_count = 3
>         name = clu_generix
> 
> Does that help and make sense?
> 
> Marc.
> 
> -- 
> Gruss / Regards,
> 
> Marc Grimme
> http://www.atix.de/               http://www.open-sharedroot.org/
> 
>

Re: [OSR-users] rpms for ocfs2+rhel5

[Marc G. <gr...@at...>]

On Saturday 07 February 2009 01:42:42 Dan Magenheimer wrote:
> Finally got the rpms and installed.  One other typo on
> the rhel5/ocfs2 webpage:
>
> comoonics-bootimage-1.3-33 (not -32)
>
> as comoonics-bootimage-extras-ocfs2-0.1-1 depends
> on -33.
Thanks. I fixed both typos. You might want to check if those are ok now.
>
> On to the next step! :-)
>
> Do I need a redhat cluster.conf file other than to
> have the ocfs2 cluster.conf file created from it?
> In other words, can I just start with my own
> /etc/ocfs2/cluster.conf file?  Or will the other
> installation steps require /etc/cluster/cluster.conf?
Yes, this is something I don't like either but as I had no customer willing to 
pay for it I took the simplest way ;-).

That means up to now you need a /etc/cluster/cluster.conf based on redhat 
cluster. And on the other side it wasn't possible to extend the ocfs 
cluster.conf with attributes.

So in the current state you will have to create a cluster.conf. This will be 
the base for the /etc/ocfs2/cluster.conf which will be automatically 
generated by com-queryclusterconf convert ocfs2. To validate the output you 
can use the command. It should return something like below:

[root@generix3 ~]# com-queryclusterconf convert ocfs2

node:
        ip_port = 7777
        ip_address = 10.10.10.83
        number = 3
        name = generix3.local
        cluster = clu_generix

node:
        ip_port = 7777
        ip_address = 10.10.10.82
        number = 2
        name = generix2.local
        cluster = clu_generix

node:
        ip_port = 7777
        ip_address = 10.10.10.84
        number = 4
        name = generix4.local
        cluster = clu_generix

cluster:
        node_count = 3
        name = clu_generix

Does that help and make sense?

Marc.

-- 
Gruss / Regards,

Marc Grimme
http://www.atix.de/               http://www.open-sharedroot.org/