i get many errors when i try compile dm-clog.c dm-clog-tfr.c from cluster 2.03.09 ../cluster/cmirror-kernel/src/dm-clog.c:583: error: unknown field 'clear_region' specified in initializer ../cluster/cmirror-kernel/src/dm-clog.c:583: warning: excess elements in struct initializer ../cluster/cmirror-kernel/src/dm-clog.c:583: warning: (near initialization for '_clustered_disk_type') ../cluster/cmirror-kernel/src/dm-clog.c:584: error: unknown field 'get_resync_work' specified in initializer ../cluster/cmirror-kernel/src/dm-clog.c:584: warning: excess elements in struct initializer ../cluster/cmirror-kernel/src/dm-clog.c:584: warning: (near initialization for '_clustered_disk_type') ../cluster/cmirror-kernel/src/dm-clog.c:585: error: unknown field 'set_region_sync' specified in initializer ../cluster/cmirror-kernel/src/dm-clog.c:585: warning: excess elements in struct initializer ../cluster/cmirror-kernel/src/dm-clog.c:585: warning: (near initialization for '_clustered_disk_type') ../cluster/cmirror-kernel/src/dm-clog.c:586: error: unknown field 'get_sync_count' specified in initializer ../cluster/cmirror-kernel/src/dm-clog.c:586: warning: excess elements in struct initializer ../cluster/cmirror-kernel/src/dm-clog.c:586: warning: (near initialization for '_clustered_disk_type') ../cluster/cmirror-kernel/src/dm-clog.c:587: error: unknown field 'status' specified in initializer ../cluster/cmirror-kernel/src/dm-clog.c:587: warning: excess elements in struct initializer ../cluster/cmirror-kernel/src/dm-clog.c:587: warning: (near initialization for '_clustered_disk_type') ../cluster/cmirror-kernel/src/dm-clog.c:588: error: unknown field 'get_failure_response' specified in initializer ../cluster/cmirror-kernel/src/dm-clog.c:588: warning: excess elements in struct initializer ../cluster/cmirror-kernel/src/dm-clog.c:588: warning: (near initialization for '_clustered_disk_type') ../cluster/cmirror-kernel/src/dm-clog.c:591: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'cluster_dirty_log_init' ../cluster/cmirror-kernel/src/dm-clog.c:619: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'cluster_dirty_log_exit В Пнд, 24/11/2008 в 11:46 +0300, Василец Дмитрий пишет: > 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
