Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
got the part about the status report..
still a bit confused about the filesystem access
i would be replicating the entire /dev/md0 .. as per the tutorials i read, i
am not supposed to mount this device, and let drbd handle it. thats fine..
but why do i need to create a file system on /dev/drbd0, and how will I
access the files on /dev/md0, since i can't mount it or anything..
other than that.. I formatted /dev/drbd0 on one system using mkreiserfs, ,
completed successfully and i rebooted server, and the /dev/drbd0 has
dissappeared..
On the other system it won't let me format the dev/drbd0 saying "could not
open /dev/drbd0
Read only filesystem"
On 11/30/06, Milind Dumbare <milind at linsyssoft.com> wrote:
>
> On Wednesday 29 November 2006 22:26, Kamran Nisar wrote:
> > okie i got it to compile against the source of the kernel installed...
> >
> > drbd is finally up :D
> >
> > okie now, i have a couple of other concerns..
> > firstly after setting on as primary, the cat /proc/drbd on both machine
> is
> > reflected as..
> > test 1 is the primary
> >
> > test1:~ # cat /proc/drbd
> > version: 0.7.14 (api:77/proto:74)
> > SVN Revision: 1989 build by root at test1, 2005-11-11 14:50:53
> > 0: cs:Connected st:Primary/Secondary ld:Consistent
> > ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0
> > 1: cs:Unconfigured
> st:Primary/Secondary means this node is primary and peer is secondary same
> for
> entry at other node in /proc/drbd
> >
> >
> > test2:~ # cat /proc/drbd
> > version: 0.7.18 (api:78/proto:74)
> > SVN Revision: 2186 build by lmb at chip, 2006-05-04 17:08:27
> > 0: cs:Connected st:Secondary/Primary ld:Consistent
> > ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0
> > 1: cs:Unconfigured
> >
> >
> > is the above correct ? should the st:/primary/Secondary should be same
> on
> > both the machines ?
> >
> > secondly i'm using the folling snip in my conf file
> >
> > on test1 {
> > device /dev/drbd0;
> > disk /dev/md0;
> > address 192.168.2.61:7788;
> > meta-disk internal;
> > }
> >
> > on test2 {
> > device /dev/drbd0;
> > disk /dev/md0;
> > address 192.168.2.62:7788;
> > meta-disk internal;
> > }
> >
> >
> >
> > I have linux RAID0 on both the server under /dev/md0
> >
> > now the thing i can't figure out, is where does the data actually goes
> on
> > the server1 is how to mount /dev/md0 to store some data on it.. because
> > when i try to mount it, it says drive is busy, probably becuase of
> sumthing
> > drbd is doing ..
> You have now set up /dev/drbd0 on existing /dev/md0. Now when you create
> filesystem on /dev/drbd0 every block of /dev/md0 from test1 node will be
> replicated to /dev/md0 of test2.
>
> >
> >
> >
> > Thanks
> >
> > On 11/29/06, Milind Dumbare <milind at linsyssoft.com> wrote:
> > > On Wednesday 29 November 2006 19:41, Kamran Nisar wrote:
> > > > right, so how do i get the exact 13-4 source code ? coz i blv these
> > > > extension aren't supported for long and disappear quickly.. i can
> > > > either find a 16.13 or 16.14
> > >
> > > Thats SUSE's kernel I guess. Because kernel.org doesn't give such
> > > extensions.
> > >
> > >
> www.rpmfind.net/linux/RPM/opensuse/10.1/i586/kernel-bigsmp-2.6.16.13-4.i5
> > >86.html see here for the source RPM. Or google for it.
> > >
> > > > On 11/29/06, Milind Dumbare <milind at linsyssoft.com> wrote:
> > > > > On Wednesday 29 November 2006 19:24, Kamran Nisar wrote:
> > > > > > here's the drbd module path
> > > > > >
> > > > > > test2:~ # find /lib/modules -name "drbd*"
> > > > > > /lib/modules/2.6.16.13-smp/block/drbd.ko
> > > > > > /lib/modules/2.6.16.13-4-smp/block/drbd.ko
> > > > > > /lib/modules/2.6.16.21-0.25-smp/block/drbd.ko
> > > > > >
> > > > > > test2:~ # find /lib/modules/`uname -r` -name "drbd*"
> > > > > > /lib/modules/2.6.16.13-4-smp/block/drbd.ko
> > > > > >
> > > > > >
> > > > > > 2.6.16.13-4-smp was the standard kernel with the installation..
> i
> > > > >
> > > > > couldn't
> > > > >
> > > > > > find 2.16.13-4-smp source, so i compiled drbd against 2.6.16.13
> 's
> > > > >
> > > > > source.
> > > > > Ohh, you mean you compile drbd with 2.6.16.13 and put it
> > > > > in /lib/modules/2.6.16.13-4-smp/block ? And trying to insert
> that
> > > > > module?
> > > > > That wont work. You can't mismatch the kernel version and module
> > >
> > > version.
> > >
> > > > > You can load module in kernel only when that module is compiled
> with
> > >
> > > that
> > >
> > > > > kernel version source.
> > > > >
> > > > > > and yepsh.. still doesn't seem to be loaded :(
> > > > > >
> > > > > > On 11/29/06, Milind Dumbare <milind at linsyssoft.com> wrote:
> > > > > > > On Wednesday 29 November 2006 18:49, Kamran Nisar wrote:
> > > > > > > > they are as below
> > > > > > > >
> > > > > > > >
> > > > > > > > test2:~# uname -a
> > > > > > > > Linux test2 2.6.16.13-4-smp #1 SMP Wed May 3 04:53:23 UTC
> 2006
> > >
> > > i686
> > >
> > > > > > > > i686 i386 GNU/Linux
> > > > > > >
> > > > > > > So you are booting through 2.6.16.13-4-smp kernel.
> > > > > > >
> > > > > > > > test2:~# lsmod
> > > > > > > > Module Size Used by
> > > > > > > > vfat 16000 0
> > > > > > > > fat 51356 1 vfat
> > > > > > > > ext3 123528 0
> > > > > > > > jbd 63264 1 ext3
> > > > > > > > parport_pc 39524 0
> > > > > > > > parport 37192 1 parport_pc
> > > > > > > > nls_utf8 6016 0
> > > > > > > > edd 12484 0
> > > > > > > > af_packet 28296 0
> > > > > > > > iptable_filter 6912 0
> > > > > > > > ip_tables 16196 1 iptable_filter
> > > > > > > > x_tables 16388 1 ip_tables
> > > > > > > > ipv6 242272 20
> > > > > > > > joydev 12992 0
> > > > > > > > sg 35996 0
> > > > > > > > st 38684 0
> > > > > > > > sd_mod 20352 0
> > > > > > > > sr_mod 18596 0
> > > > > > > > scsi_mod 128008 4 sg,st,sd_mod,sr_mod
> > > > > > > > button 10640 0
> > > > > > > > battery 13444 0
> > > > > > > > ac 8964 0
> > > > > > > > apparmor 53144 0
> > > > > > > > aamatch_pcre 17408 1 apparmor
> > > > > > > > loop 19080 0
> > > > > > > > dm_mod 57936 0
> > > > > > > > i2c_viapro 11924 0
> > > > > > > > via686a 19208 0
> > > > > > > > via_agp 13440 1
> > > > > > > > hwmon 6916 1 via686a
> > > > > > > > i2c_isa 8576 1 via686a
> > > > > > > > i2c_core 24064 3 i2c_viapro,via686a,i2c_isa
> > > > > > > > agpgart 33352 1 via_agp
> > > > > > > > e100 37256 0
> > > > > > > > mii 9088 1 e100
> > > > > > > > shpchp 44000 0
> > > > > > > > pci_hotplug 28860 1 shpchp
> > > > > > > > ide_cd 39840 0
> > > > > > > > cdrom 36512 2 sr_mod,ide_cd
> > > > > > > > reiserfs 217856 2
> > > > > > > > raid0 11648 1
> > > > > > > > fan 8580 0
> > > > > > > > thermal 17416 0
> > > > > > > > processor 31208 1 thermal
> > > > > > > > via82cxxx 12164 0 [permanent]
> > > > > > > > ide_disk 19200 8
> > > > > > > > ide_core 123340 3 ide_cd,via82cxxx,ide_disk
> > > > > > >
> > > > > > > Where is drbd module? its not in yet?
> > > > > > >
> > > > > > > > test2:~ # ls /lib/modules/
> > > > > > > > 2.6.16.13-4-smp 2.6.16.13-smp 2.6.16.21-0.25-smp
> > > > > > >
> > > > > > > does /lib/modules/2.6.16.13-4-smp have drbd.ko anywhere?
> > > > > > >
> > > > > > > > test2:~/new # pwd
> > > > > > > > /root/new
> > > > > > > > test2:~/new # ls
> > > > > > > > drbd-0.7.22 drbd-0.7.22.tar.gz
> > > > > > >
> > > > > > > Have you compiled drbd-0.7.22/drbd/ with 2.6.16.13-4-smpsources?
> > > > > > >
> > > > > > > > On 11/29/06, Milind Dumbare <milind at linsyssoft.com> wrote:
> > > > > > > > > ok post following things here
> > > > > > > > > 1. uname -a
> > > > > > > > > 2. lsmod
> > > > > > > > > 3. ls /lib/modules
> > > > > > > > > 4. your drbd tarball's path.
> > > > > > > > >
> > > > > > > > > On Wednesday 29 November 2006 18:30, Kamran Nisar wrote:
> > > > > > > > > > alrite, thank you all for you support :)
> > > > > > > > > >
> > > > > > > > > > done with that.. now i'm getting this when trying to
> start
> > >
> > > drbd
> > >
> > > > > > > > > > test2:~/new/drbd-0.7.22/scripts # drbdadm up all
> > > > > > > > > > can not open /dev/drbd0: No such device or address
> > > > > > > > > >
> > > > > > > > > > i created the device using mknod.. is there any speical
> > > > > > > > > > that
> > > > >
> > > > > needs
> > > > >
> > > > > > > to
> > > > > > >
> > > > > > > > > > be done to these devices ?
> > > > > > > > > >
> > > > > > > > > > On 11/29/06, Milind Dumbare <milind at linsyssoft.com>
> wrote:
> > > > > > > > > > > On Wednesday 29 November 2006 16:44, Kamran Nisar
> wrote:
> > > > > > > > > > > > nopes. nuthing worked...same error..
> > > > > > > > > > > >
> > > > > > > > > > > > there are a few things, pls take a moment and let me
> > >
> > > know
> > >
> > > > > > > > > > > > if
> > > > > > >
> > > > > > > that
> > > > > > >
> > > > > > > > > could
> > > > > > > > >
> > > > > > > > > > > be
> > > > > > > > > > >
> > > > > > > > > > > > cause of the problem
> > > > > > > > > > > >
> > > > > > > > > > > > my uname -r output shows version 2.6.16.13-4 , there
> > > > > > > > > > > > was
> > >
> > > no
> > >
> > > > > > > source
> > > > > > >
> > > > > > > > > code
> > > > > > > > >
> > > > > > > > > > > > avaiblae so i compiled aginst the source od
> 2.6.16.13..
> > > > >
> > > > > would
> > > > >
> > > > > > > that
> > > > > > >
> > > > > > > > > be
> > > > > > > > >
> > > > > > > > > > > > screwing up things ?
> > > > > > > > > > >
> > > > > > > > > > > Definitel, it will screw up If you insert 2.6.16.13's
> > >
> > > module
> > >
> > > > > into
> > > > >
> > > > > > > > > > > 2.6.16.13-4.
> > > > > > > > > > > Compile DRBD with 2.6.16.13-4 source or build bzImage
> for
> > > > > > > > > > > 2.6.16.13boot into
> > > > > > > > > > > it and then compile and install the drbd module for it
> > > > > > > > > > >
> > > > > > > > > > > > On 11/29/06, Leroy van Logchem
> > > > > > > > > > > > <leroy.vanlogchem at wldelft.nl>
> > > > > > >
> > > > > > > wrote:
> > > > > > > > > > > > > Kamran Nisar wrote:
> > > > > > > > > > > > > > test2:~ # insmod drbd.ko
> > > > > > > > > > > > >
> > > > > > > > > > > > > Try modprobe. Did you depmod?
>
--
Regards
M Kamran Nisar,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20061130/c0016163/attachment.htm>