Re: Distributed RAID

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I use last source from git stable RHEL5
but, when i try compile cmirror kernel mudule i get syntax error


[root@node1 cmirror-kernel]# make
cd src && make all
make[1]: Entering directory `/home/test2/cluster/cmirror-kernel/src'
make -C /lib/modules/2.6.27.5-117.storage.x86_64/source
M=/home/test2/cluster/cmirror-kernel/src   modules USING_KBUILD=yes
make[2]: Entering directory
`/usr/src/kernels/2.6.27.5-117.storage.x86_64'
  CC [M]  /home/test2/cluster/cmirror-kernel/src/dm-clog.o
/home/test2/cluster/cmirror-kernel/src/dm-clog.c: In function
‘cluster_ctr’:
/home/test2/cluster/cmirror-kernel/src/dm-clog.c:148: warning: format ‘%
llu’ expects type ‘long long unsigned int’, but argument 3 has type
‘sector_t’
/home/test2/cluster/cmirror-kernel/src/dm-clog.c: In function
‘cluster_flush’:
/home/test2/cluster/cmirror-kernel/src/dm-clog.c:417: warning:
comparison of distinct pointer types lacks a cast
/home/test2/cluster/cmirror-kernel/src/dm-clog.c:419: warning:
comparison of distinct pointer types lacks a cast
/home/test2/cluster/cmirror-kernel/src/dm-clog.c: In function
‘cluster_mark_region’:
/home/test2/cluster/cmirror-kernel/src/dm-clog.c:478: warning:
comparison of distinct pointer types lacks a cast
/home/test2/cluster/cmirror-kernel/src/dm-clog.c:482: warning:
comparison of distinct pointer types lacks a cast
/home/test2/cluster/cmirror-kernel/src/dm-clog.c: In function
‘cluster_clear_region’:
/home/test2/cluster/cmirror-kernel/src/dm-clog.c:517: warning:
comparison of distinct pointer types lacks a cast
/home/test2/cluster/cmirror-kernel/src/dm-clog.c:521: warning:
comparison of distinct pointer types lacks a cast
/home/test2/cluster/cmirror-kernel/src/dm-clog.c: At top level:
/home/test2/cluster/cmirror-kernel/src/dm-clog.c:709: error: unknown
field ‘get_failure_response’ specified in initializer
/home/test2/cluster/cmirror-kernel/src/dm-clog.c:709: warning: excess
elements in struct initializer
/home/test2/cluster/cmirror-kernel/src/dm-clog.c:709: warning: (near
initialization for ‘_clustered_core_type’)
/home/test2/cluster/cmirror-kernel/src/dm-clog.c:710: error: unknown
field ‘is_remote_recovering’ specified in initializer
/home/test2/cluster/cmirror-kernel/src/dm-clog.c:710: warning: excess
elements in struct initializer
/home/test2/cluster/cmirror-kernel/src/dm-clog.c:710: warning: (near
initialization for ‘_clustered_core_type’)
/home/test2/cluster/cmirror-kernel/src/dm-clog.c:731: error: unknown
field ‘get_failure_response’ specified in initializer
/home/test2/cluster/cmirror-kernel/src/dm-clog.c:731: warning: excess
elements in struct initializer
/home/test2/cluster/cmirror-kernel/src/dm-clog.c:731: warning: (near
initialization for ‘_clustered_disk_type’)
/home/test2/cluster/cmirror-kernel/src/dm-clog.c:732: error: unknown
field ‘is_remote_recovering’ specified in initializer
/home/test2/cluster/cmirror-kernel/src/dm-clog.c:732: warning: excess
elements in struct initializer
/home/test2/cluster/cmirror-kernel/src/dm-clog.c:732: warning: (near
initialization for ‘_clustered_disk_type’)
make[3]: *** [/home/test2/cluster/cmirror-kernel/src/dm-clog.o] Error 1
make[2]: *** [_module_/home/test2/cluster/cmirror-kernel/src] Error 2
make[2]: Leaving directory
`/usr/src/kernels/2.6.27.5-117.storage.x86_64'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/test2/cluster/cmirror-kernel/src'
make: *** [all] Error 2

Thank you

В Втр, 25/11/2008 в 14:23 -0600, Jonathan Brassow пишет:
> You do not have the module installed (or in the right place?).
> 
> You need the cmirror and cmirror-kmod packages.  If you don't have  
> access to them, and would like to compile them for yourself, then you  
> will need to check-out the cluster tree on the RHEL5 or RHEL53 branch.
> 
>   brassow
> 
> On Nov 24, 2008, at 2:46 AM, Василец Дмитрий wrote:
> 
> > Hello
> > This is /var/log/messages
> > "Nov 20 07:57:14 recipient1 kernel: device-mapper: dirty region log:
> > Module for logging type "clustered-core" not found.
> > Nov 20 07:57:14 recipient1 kernel: device-mapper: table: 253:2:  
> > mirror:
> > Error creating mirror dirty log
> > Nov 20 07:57:14 recipient1 kernel: device-mapper: ioctl: error adding
> > target to table
> > Nov 20 08:43:37 recipient1 kernel: device-mapper: dirty region log:
> > Module for logging type "clustered-core" not found.
> > Nov 20 08:43:37 recipient1 kernel: device-mapper: table: 253:2:  
> > mirror:
> > Error creating mirror dirty log
> > Nov 20 08:43:37 recipient1 kernel: device-mapper: ioctl: error adding
> > target to table
> > Nov 20 08:47:05 recipient1 kernel: device-mapper: dirty region log:
> > Module for logging type "clustered-core" not found.
> > Nov 20 08:47:05 recipient1 kernel: device-mapper: table: 253:2:  
> > mirror:
> > Error creating mirror dirty log
> > Nov 20 08:47:05 recipient1 kernel: device-mapper: ioctl: error adding
> > target to table
> > "
> >
> > В Птн, 21/11/2008 в 11:51 -0600, Jonathan Brassow пишет:
> >> What does /var/log/messages say?
> >>
> >>  brassow
> >>
> >> On Nov 20, 2008, at 3:33 AM, Василец Дмитрий wrote:
> >>
> >>> hello
> >>> i use lvm2  2.02.39
> >>> when i write  "lvcreate  -L 60G -m1 --corelog  -n mirror1 volg1"
> >>> i get error
> >>> "Error locking on node recipient1: device-mapper: reload ioctl  
> >>> failed:
> >>> Invalid argument
> >>> Error locking on node recipient2: device-mapper: reload ioctl
> >>> failed:Invalid argument
> >>> Aborting. Failed to activate new LV to wipe the start of it."
> >>>
> >>> i must update lvm2 or other ?
> >>>
> >>> В Втр, 11/11/2008 в 20:01 -0600, Jonathan Brassow пишет:
> >>>> Sure.  In fact, if you have access to the red hat 5.3 beta, it is
> >>>> ready there.
> >>>>
> >>>>
> >>>> brassow
> >>>>
> >>>> On Nov 7, 2008, at 6:59 AM, pronix pronix wrote:
> >>>>
> >>>>> can i use cluster raid1 if i get development release from
> >>>>> sources.redhat.com/cluster ?
> >>>>>
> >>>>>
> >>>>> 2008/11/7 Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
> >>>>> <mad@xxxxxx>
> >>>>>       Hello,
> >>>>>
> >>>>>
> >>>>>       will the changes to mirroring get merged into stable2 and
> >>>>>       head after
> >>>>>       RHEL-5.3 release?
> >>>>>
> >>>>>
> >>>>>       Marc
> >>>>>
> >>>>>       Am Donnerstag, den 06.11.2008, 16:34 -0600 schrieb Jonathan
> >>>>>       Brassow:
> >>>>>
> >>>>>> that works already.
> >>>>>>
> >>>>>> single machine: linear, stripe, mirror, snapshot
> >>>>>> cluster-aware: linear, stripe, mirror (5.3)
> >>>>>>
> >>>>>> brassow
> >>>>>>
> >>>>>> On Nov 6, 2008, at 2:40 PM, Gordan Bobic wrote:
> >>>>>>
> >>>>>>> What about CLVM based striping (RAID0)? Does that work
> >>>>>       already or is
> >>>>>>> it planned for the near future?
> >>>>>>>
> >>>>>>> Gordan
> >>>>>>>
> >>>>>>> Jonathan Brassow wrote:
> >>>>>>>> Cluster mirror (RAID1) will be available in rhel5.3 for
> >>>>>       LVM.
> >>>>>>>> brassow
> >>>>>>>> On Nov 6, 2008, at 9:40 AM, Federico Simoncelli wrote:
> >>>>>>>>> On Thu, Nov 6, 2008 at 10:38 AM, Gordan Bobic
> >>>>>       <gordan@xxxxxxxxxx>
> >>>>>>>>> wrote:
> >>>>>>>>>> I rather doubt md will become cluster aware any time
> >>>>>       soon. CLVM
> >>>>>>>>>> doesn't yet
> >>>>>>>>>> support even more important features like
> >>>>>       snapshotting, so I
> >>>>>>>>>> wouldn't count
> >>>>>>>>>> on it supporting anything more advanced.
> >>>>>>>>>
> >>>>>>>>> I worked a little on clvm snapshots:
> >>>>>>>>>
> >>>>>       https://www.redhat.com/archives/linux-lvm/2008-October/msg00027.html
> >>>>>>>>>
> >>>>>>>>> Review and testing is required.
> >>>>>>>>> --
> >>>>>>>>> Federico.
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>> Linux-cluster mailing list
> >>>>>>>>> Linux-cluster@xxxxxxxxxx
> >>>>>>>>> https://www.redhat.com/mailman/listinfo/linux-cluster
> >>>>>>>> --
> >>>>>>>> Linux-cluster mailing list
> >>>>>>>> Linux-cluster@xxxxxxxxxx
> >>>>>>>> https://www.redhat.com/mailman/listinfo/linux-cluster
> >>>>>>>
> >>>>>>> --
> >>>>>>> Linux-cluster mailing list
> >>>>>>> Linux-cluster@xxxxxxxxxx
> >>>>>>> https://www.redhat.com/mailman/listinfo/linux-cluster
> >>>>>>
> >>>>>> --
> >>>>>> Linux-cluster mailing list
> >>>>>> Linux-cluster@xxxxxxxxxx
> >>>>>> https://www.redhat.com/mailman/listinfo/linux-cluster
> >>>>>
> >>>>>
> >>>>>       --
> >>>>>
> >>>>>       Linux-cluster mailing list
> >>>>>       Linux-cluster@xxxxxxxxxx
> >>>>>       https://www.redhat.com/mailman/listinfo/linux-cluster
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Linux-cluster mailing list
> >>>>> Linux-cluster@xxxxxxxxxx
> >>>>> https://www.redhat.com/mailman/listinfo/linux-cluster
> >>>>
> >>>>
> >>>> --
> >>>> Linux-cluster mailing list
> >>>> Linux-cluster@xxxxxxxxxx
> >>>> https://www.redhat.com/mailman/listinfo/linux-cluster
> >>>
> >>> --
> >>> Linux-cluster mailing list
> >>> Linux-cluster@xxxxxxxxxx
> >>> https://www.redhat.com/mailman/listinfo/linux-cluster
> >>
> >>
> >> --
> >> Linux-cluster mailing list
> >> Linux-cluster@xxxxxxxxxx
> >> https://www.redhat.com/mailman/listinfo/linux-cluster
> >>
> >
> > --
> > Linux-cluster mailing list
> > Linux-cluster@xxxxxxxxxx
> > https://www.redhat.com/mailman/listinfo/linux-cluster
> 
> 
> --
> Linux-cluster mailing list
> Linux-cluster@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/linux-cluster
> 

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux